The flow
Starts it 1Logic 10Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Everhour - Fetch Time OffHttp RequestService
- 3ConfigSetLogic
- 4Filter Approved Time-OffIfLogic
- 5Prepare Time-Off ItemsCodeLogic
- 6Build Calendar PayloadSetLogic
- 7Find Existing Event by External KeyHttp RequestService
- 8Build Assignment GroupsCodeLogic
- 9Build Global Key SetCodeLogic
- 10Attach Found Event IDCodeLogic
- 11List Assignment EventsHttp RequestService
- 12List All Everhour EventsHttp RequestService
- 13Check if Event ExistsIfLogic
- 14Find Obsolete Events (per assignment)CodeLogic
- 15Find Obsolete Events (global)CodeLogic
- 16Update All-Day EventGoogle CalendarService
- 17Create All-Day EventGoogle CalendarService
- 18Delete Calendar EventGoogle CalendarService
How it's built
- Starts on
- A clock
- Steps
- 18, 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 a clock.
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. 18 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 18 steps before you point it at anything that matters.