Rotate on-call schedules around leave and holidays with Google Calendar, Slack and Nager.Date

by Melbin Francis ✓ · 0 views · created 2026-09-29 · DevOps

What this workflow does

This workflow has 23 nodes and runs on a schedule (every week at 10:00) (plus 1 other trigger). Along the way it connects Google Calendar and Slack.

How it runs

Trigger: On a schedule (every week at 10:00) (plus 1 other trigger).

1. Rota Rules (Edit Fields (Set)): sets 8 fields: team, holiday_country, lead_slack_id…
2. Read Past On-Call Weeks (Google Calendar): get many (event)
3. Read The Leave Calendar (Google Calendar): get many (event)
4. Read Public Holidays (HTTP Request): calls an HTTP API
5. Combine History, Leave And Holidays (Merge): merges the data from its input branches
6. Decide The On-Call Week (Code): runs custom JavaScript code
7. What Now For The Week? (Switch): routes items into 4 branches
8. Book The On-Call Week (Google Calendar): create (event)
9. Escalate: Nobody Available (Slack): post (message)
10. Put The Week Back (Google Calendar): update (event)

…plus 11 more steps. See the full node list below.

Services it uses

Google CalendarSlack

Before you upgrade to n8n 3.0

Nodes used (11)

• Schedule Triggern8n-nodes-base.scheduleTrigger
• Google Calendar Triggern8n-nodes-base.googleCalendarTrigger
• Edit Fields (Set)n8n-nodes-base.set
• Google Calendarn8n-nodes-base.googleCalendar
• HTTP Requestn8n-nodes-base.httpRequest
• Mergen8n-nodes-base.merge
• Coden8n-nodes-base.code
• Switchn8n-nodes-base.switch
• Slackn8n-nodes-base.slack
• Waitn8n-nodes-base.wait
• Loop Over Items (Split in Batches)n8n-nodes-base.splitInBatches

From the author

Quick overview This workflow rotates weekly on-call duty using Google Calendar events, factoring in team history, leave, and public holidays from the Nager.Date API, then announces the assignment and swap outcomes in Slack and updates a channel topic at…

View the original on n8n.io → Check your own copy