Calendar_scheduling
Configured with Agent, Chain LLM, Execute Workflow Trigger, Filter, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Subworkflow
- Integration
- Transform
- Routing
- Messaging
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 |
|---|---|---|---|
| Gmail Trigger | Trigger | Gmail Trigger | See node parameters |
| Chat OpenAI | AI & models | OpenAI Chat Model | See node parameters |
| Workflow Tool | Subworkflow | Tool Workflow | See node parameters |
| Chat OpenAI1 | AI & models | OpenAI Chat Model | See node parameters |
| Google Calendar | Integration | Google Calendar | getAll |
| Execute Workflow Trigger | Trigger | Execute Workflow Trigger | See node parameters |
| Format response | Transform | Item Lists | concatenateItems |
| Stringify Response | Transform | Edit Fields | See node parameters |
| Extract start, end and name | Transform | Edit Fields | See node parameters |
| Filter only confirmed and with set time | Routing | Filter | See node parameters |
| Is appointment request | Routing | If | See node parameters |
| Classify appointment | AI & models | Chain LLM | See node parameters |
| Structured Output Parser | Transform | Output Parser Structured | See node parameters |
| Sort | Transform | Item Lists | sort |
| Mark as read | Messaging | Gmail | markAsRead |
| Send Reply | Messaging | Gmail | reply |
| Agent | AI & models | Agent | See node parameters |
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
gmailOAuth2googleCalendarOAuth2ApiopenAiApi
Workflow notes
Check if incoming email is about appointment
Check if incoming email is about appointment
We use LLM to check subject and body of the email and determine if it's an appointment request.
Get calendar availability and compose a response
Get calendar availability and compose a response
Make sure to update the Workflow ID if you are running this as 2 workflows
Calendar_scheduling
Calendar_scheduling
Purpose and structure
This folder contains the Calendar_scheduling workflow. Its executable nodes use agent, chainLlm, executeWorkflowTrigger, filter, gmail, gmailTrigger, googleCalendar, if, itemLists, lmChatOpenAi, outputParserStructured, set, toolWorkflow. 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
Gmail Trigger, Execute Workflow 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/Googlecalendar/1668_GoogleCalendar_Filter_Automation_Triggered.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Get all query google events for the next month and extract relevant data
- Wrap the result in `response` object and return