Google Calendar to Slack Status and Philips Hue
Needs changesWhat this workflow does
This workflow has 9 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Google Calendar and Slack.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Google Calendar: get
- Set CalColor (Function): runs custom JavaScript (legacy Function node)
- Slack: update (user profile)
- Switch: routes items into 4 branches
- Light - Busy (HTTP Request): calls an HTTP API
- Light - Personal (HTTP Request): calls an HTTP API
- Light - Available (HTTP Request): calls an HTTP API
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Set CalColor: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Set CalColor | Code node, mode 'Run Once for All Items' |
Nodes used (7)
- Manual Trigger
n8n-nodes-base.manualTrigger - Google Calendar
n8n-nodes-base.googleCalendar - HTTP Request
n8n-nodes-base.httpRequest - Switch
n8n-nodes-base.switch - Google Calendar Trigger
n8n-nodes-base.googleCalendarTrigger - Slack
n8n-nodes-base.slack - Function
n8n-nodes-base.function
From the author
I'm currently trialing a 4 day work week for all staff at my company, and one of the major impacts on productivity is interruptions. As such, I opted to use N8N to create a workflow to monitor my Google Calendar and when an event starts, to update my Slack…