The flow
Starts it 1Logic 12Service 9
The steps in the order they run, from what starts it.
- 1Clockify TriggerClockify triggerStarts it
- 2ConfigSetLogic
- 3Translations for created Calendar EventSetLogic
- 4Rename to ClockifyFunction ItemService
- 5Get Events with IDGoogle CalendarService
- 6Merge Clockify and Calendar dataMergeLogic
- 7Rename to CalendarFunction ItemService
- 8Does the calendar event already exist?IfLogic
- 9Has the event been deleted?IfLogic
- 10Create EventGoogle CalendarService
- 11Increment loop_idFunction ItemService
- 12Do the times match?IfLogic
- 13Event createdNo OpLogic
- 14Get Events with ID + loop_idGoogle CalendarService
- 15Merge Clockify and Calendar data1MergeLogic
- 16SuccessNo OpLogic
- 17Update EventGoogle CalendarService
- 18Rename to Calendar1Function ItemService
- 19Event exists alreadyIfLogic
- 20Event updatedNo OpLogic
- 21Create Event1Google CalendarService
- 22Event created againNo OpLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 22, with 4 branches
- Size
- Large: read it before trusting it with anything live
- 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?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
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 22 steps before you point it at anything that matters.