

How to Send Out-of-Office Alerts from Google Calendar to Slack with Make
Automatically post to Slack when someone creates an all-day 'OOO' or 'Vacation' event in Google Calendar.
Steps and UI details are based on platform versions at time of writing β check each platform for the latest interface.
Best for
Teams that need fast OOO notifications with custom filtering for specific event types or titles.
Not ideal for
Simple setups with under 10 OOO events per month where Zapier's built-in templates work fine.
Sync type
real-timeUse case type
notificationReal-World Example
A 25-person marketing agency uses this to notify #team-updates whenever someone blocks PTO in their shared Google Calendar. Before automation, project managers manually checked calendars each Monday and often scheduled meetings with people who were out. Now they get instant Slack alerts when anyone adds 'OOO', 'Vacation', or 'PTO' events, preventing double-booked resources and client delays.
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently β Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.





Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
Implementation
Import this workflow directly into Make
Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured β you just need to connect your accounts.
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Event Title | summary | |
| Person Name | organizer.displayName | |
| Start Date | start.date | |
3 optional fieldsβΈ show
| End Date | end.date |
| Event Creator | creator.displayName |
| Event Description | description |
Step-by-Step Setup
Dashboard > Create scenario > + > Google Calendar
Create New Scenario
Start building your scenario in Make. You'll connect Google Calendar as the trigger and Slack as the action module.
- 1Click the blue 'Create a new scenario' button from your Make dashboard
- 2Click the + icon in the center of the canvas
- 3Search for 'Google Calendar' in the app list
- 4Select 'Watch Events' from the trigger options
Google Calendar module > Connection > Add
Connect Google Calendar Account
Link your Google Calendar account to Make. This creates the authenticated connection needed to monitor calendar events.
- 1Click 'Add' next to the Connection field
- 2Select 'Google' as the connection type
- 3Click 'Continue' to open Google's OAuth window
- 4Authorize Make to access your Google Calendar
- 5Name your connection something like 'Work Calendar'
Google Calendar module > Settings
Configure Calendar Watch Settings
Set up the trigger to monitor the right calendar and watch for new events. This determines which calendar events will start your automation.
- 1Select your target calendar from the 'Calendar ID' dropdown
- 2Set 'Watch Events' to 'Events Created'
- 3Leave 'Show Deleted Events' unchecked
- 4Set 'Max Results' to 100
- 5Click 'OK' to save the module settings
Module connection line > Set up filter
Add Filter for OOO Events
Create a filter between modules to only process events with OOO-related titles. This prevents the automation from running on every calendar event.
- 1Click the gear icon on the line between modules
- 2Click 'Set up a filter'
- 3Name the filter 'OOO Events Only'
- 4Set condition: 'summary' contains 'OOO' OR 'summary' contains 'Vacation'
- 5Add another condition: 'start.date' exists (for all-day events)
Canvas > + > Slack > Create a Message
Add Slack Module
Connect Slack as the action that will post your OOO notification. This module sends the actual message to your team channel.
- 1Click the + icon after your filter
- 2Search for 'Slack' in the apps list
- 3Select 'Create a Message' from the actions
- 4Click 'Add' next to Connection to link your Slack workspace
Slack module > Connection > Create connection
Connect Slack Workspace
Authenticate your Slack workspace so Make can post messages. You'll need admin permissions or approval to install the Make app.
- 1Click 'Create a connection' in the connection dropdown
- 2Select your Slack workspace from the list
- 3Click 'Allow' to grant Make posting permissions
- 4Name your connection after your workspace name
Slack module > Channel settings
Configure Slack Channel
Select the target channel for OOO notifications. This is where team members will see the automated alerts.
- 1Select 'Channel' as the target type
- 2Choose '#team-updates' from the Channel dropdown
- 3Leave 'As User' unchecked to post as the Make bot
- 4Set 'Parse' to 'None' for now
Slack module > Text field
Build Message Template
Create the message format that will post to Slack. Map calendar data into a readable notification format.
- 1Click in the 'Text' field to open the message composer
- 2Type: 'ποΈ *' then click to add the 'organizer.displayName' field
- 3Add: '* is out of office\nπ ' then add the 'summary' field
- 4Add: '\nβ° Starting ' then add the 'start.date' field
π¬ New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}start.dateTime: {{start.dateTime}}
end.dateTime: {{end.dateTime}}
Scenario controls > Run once
Test the Scenario
Run a test to verify your automation works correctly. This processes a real calendar event through your complete workflow.
- 1Click 'Run once' at the bottom left of the screen
- 2Create a test event in your Google Calendar titled 'OOO - Testing'
- 3Make it an all-day event for tomorrow
- 4Wait 2-3 minutes then check the Make execution log
Scenario controls > ON/OFF toggle
Enable Auto-Scheduling
Turn on automatic execution so your scenario runs continuously. This switches from manual testing to production mode.
- 1Click the toggle switch in the bottom left to turn 'ON'
- 2Set scheduling to 'Immediately' for real-time processing
- 3Click 'OK' to confirm the scheduling settings
- 4Verify the scenario shows 'ON' status in green
Drop this into a Make custom function.
JavaScript β Custom FunctionformatDate(start.date; "MMMM D") + if(end.date != null; " - " + formatDate(end.date; "MMMM D"); "")βΈ Show code
formatDate(start.date; "MMMM D") + if(end.date != null; " - " + formatDate(end.date; "MMMM D"); "")
... expand to see full code
formatDate(start.date; "MMMM D") + if(end.date != null; " - " + formatDate(end.date; "MMMM D"); "")
Scaling Beyond 100+ calendar events/day+ Records
If your volume exceeds 100+ calendar events/day records, apply these adjustments.
Switch to Polling
Change from 'Immediately' to 'Every 15 minutes' scheduling to avoid Google Calendar API rate limits. Instant notifications aren't worth API failures.
Add Batch Processing
Use Make's iterator module to process multiple OOO events in a single Slack message rather than individual posts flooding your channel.
Going live
Production Checklist
Before you turn this on for real, confirm each item.
Troubleshooting
Common errors and how to fix them.
Frequently Asked Questions
Common questions about this workflow.
Analysis
Use Make for this if you need precise filtering control and your team creates 50+ calendar events per month. Make's visual filter builder lets you target exact event types without coding, and its Google Calendar connector updates faster than Zapier's 15-minute polling. Skip Make if you only need basic OOO alerts β Zapier's simpler interface handles low-volume notifications just fine.
This workflow uses 2 operations per OOO event: one to watch the calendar, one to post to Slack. At 20 OOO events monthly, that's 40 operations total. Make's Core plan ($9/month) includes 10,000 operations, so you're well covered. Zapier charges $20/month for the same volume on their Starter plan. N8n is free but requires hosting β factor in $15/month for a VPS.
Zapier's Google Calendar trigger includes built-in OOO detection that recognizes vacation events automatically without custom filters. N8n's Slack node supports rich message formatting with blocks and attachments that Make's basic text field can't match. But Make wins on execution speed β its Google Calendar webhook fires within 2-3 minutes while Zapier polls every 15 minutes, meaning your team gets OOO notifications faster.
Google Calendar's API sometimes delays new events by 5-10 minutes, especially for recurring series or imported events. All-day events use the 'date' field format while timed events use 'dateTime' β your filter logic needs both. Make's error handling stops the entire scenario on Slack API failures, so add a backup webhook to catch missed notifications during Slack outages.
Ideas for what to build next
- βAdd Return Notifications β Create a second scenario that posts when OOO events end, welcoming team members back and clearing their unavailable status.
- βCreate OOO Calendar Dashboard β Send OOO events to Google Sheets or Notion to build a team availability calendar that managers can reference for project planning.
- βIntegrate with Project Tools β Extend the workflow to automatically reassign tasks in Asana or Monday.com when key team members log OOO time.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup