Gmail API Credentials
Configured with Chain LLM, Gmail, Google Calendar, HTTP Request, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Transform
- Code
- Web / API
- Messaging
- Integration
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking 'Test workflow' | Trigger | Manual Trigger | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Structured Output Parser | Transform | Output Parser Structured | See node parameters |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Change filename | Code | Code | See node parameters |
| Generate Voice Reminder | Web / API | HTTP Request | POST |
| Send Voice Reminder | Messaging | Gmail | See node parameters |
| create message | AI & models | Chain LLM | See node parameters |
| Get Appointments | Integration | Google Calendar | getAll |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
ElevenlabsAPI key
ElevenlabsAPI key
Click to get your Elevenlabs API key. Elevenlabs
Gmail API Credentials
Gmail API Credentials
Click here to view the documentation and configure your access permissions for the Google Gmail API.
Calendar API Credentials
Calendar API Credentials
Click here to view the documentation and configure your access permissions for the Google Calendar API.
Gmail API Credentials
Gmail API Credentials
Purpose and structure
This folder contains the Gmail API Credentials workflow. Its executable nodes use chainLlm, code, gmail, googleCalendar, httpRequest, lmChatOpenAi, manualTrigger, outputParserStructured, scheduleTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking 'Test workflow', Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0787_Code_GoogleCalendar_Create_Webhook.json MIT; preserve source notices.