The flow
Starts it 2Model 5Logic 6Service 6
The steps in the order they run, from what starts it.
- 1When Executed by Another WorkflowExecute Workflow triggerStarts it
- 2validate_busy_timeTool WorkflowModel
- 3create_new_eventTool WorkflowModel
- 4delete_eventTool WorkflowModel
- 5update_eventTool WorkflowModel
- 6get_events_in_gap_timeTool WorkflowModel
- 7map_dataSetLogic
- 8MCP Server TriggerMcp triggerStarts it
- 9OperationSwitchLogic
- 10validate_availability_eventGoogle CalendarService
- 11delete_event1Google CalendarService
- 12check_availability_to_createGoogle CalendarService
- 13update_calendarGoogle CalendarService
- 14get_event_in_time_gapGoogle CalendarService
- 15Edit FieldsSetLogic
- 16IfIfLogic
- 17response_data_get_dataSetLogic
- 18create_eventGoogle CalendarService
- 19Stop and ErrorStop And ErrorLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 19, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Google Calendar
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Calendar account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 19 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 19 steps before you point it at anything that matters.