The flow
Starts it 1Logic 7Service 3
The steps in the order they run, from what starts it.
- 1Daily CheckSchedule triggerStarts it
- 2Workflow ConfigurationSetLogic
- 3Loop Over ItemsSplit In BatchesLogic
- 4Get Next Week Calendar EventsGoogle CalendarService
- 5Merge and Filter Next Week HolidaysCodeLogic
- 6Fetch Public HolidaysHttp RequestService
- 7Detect Holiday ConflictsCodeLogic
- 8Check If Conflicts FoundIfLogic
- 9Generate Reschedule SuggestionsCodeLogic
- 10Format Slack DigestCodeLogic
- 11Post Slack DigestSlackService
How it's built
- Starts on
- A clock
- Steps
- 11, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Calendar, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Calendar and Slack accounts. 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. 11 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 11 steps before you point it at anything that matters.