The flow
Starts it 5Service 6
The steps in the order they run, from what starts it.
- 1Hit this URL from Streamdeck http request buttonWebhookStarts it
- 2Hit this URL from Streamdeck http request button 60WebhookStarts it
- 3Hit this URL from Streamdeck http request button 15WebhookStarts it
- 4Get the Events for the Rest of the DayGoogle CalendarService
- 5Get the Events for the Rest of the Day 60Google CalendarService
- 6Get the Events for the Rest of the Day 15Google CalendarService
- 7Push All Meetings 30 Minutes LaterGoogle CalendarService
- 8Respond with 500Respond To WebhookStarts it
- 9Push All Meetings 60 Minutes LaterGoogle CalendarService
- 10Push All Meetings 15 Minutes LaterGoogle CalendarService
- 11Respond with 200Respond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 11
- 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 another system calling it.
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.