The flow
Starts it 1Logic 7Service 10
The steps in the order they run, from what starts it.
- 1When App MentionedSlack triggerStarts it
- 2Route by Event TypeIfLogic
- 3Prepare Request ConfigSetLogic
- 4If Reaction AddedIfLogic
- 5Extract Dates with GeminiHttp RequestService
- 6Fetch Thread RepliesSlackService
- 7Parse Date OutputSetLogic
- 8Prepare Reaction ConfigSetLogic
- 9Check Calendar ConflictsGoogle CalendarService
- 10Check Reaction CriteriaIfLogic
- 11If Calendar ConflictIfLogic
- 12Lookup Request in SheetsGoogle SheetsService
- 13Warn Requester of ConflictSlackService
- 14Post Request to HR ChannelSlackService
- 15Block Time in CalendarGoogle CalendarService
- 16Log Pending Request in SheetsGoogle SheetsService
- 17Update Status in SheetsGoogle SheetsService
- 18Notify Employee of ApprovalSlackService
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, with 4 branches
- Size
- Medium: a working afternoon
- Connects to
- Google Calendar, Google Sheets, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Calendar, Google Sheets and Slack accounts. 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. 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.