

How to Send Google Calendar Event Notifications to Slack with Make
Automatically notify a Slack channel whenever a new meeting is added to your shared 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 using shared Google Calendars who want automatic Slack notifications without coding.
Not ideal for
Teams needing instant notifications (polling has 15-minute delays) or managing 20+ high-traffic calendars.
Sync type
pollingUse case type
notificationReal-World Example
A 12-person marketing agency uses this to notify #team-schedule whenever someone books client calls or internal meetings on their shared calendar. Before automation, team members missed scheduling conflicts and double-booked conference rooms twice weekly. Now everyone sees new meetings within 15 minutes of booking.
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 | |
| Start Time | start.dateTime | |
4 optional fields▸ show
| Attendees | attendees.email |
| Location | location |
| Event Creator | creator.email |
| Description | description |
Step-by-Step Setup
Scenarios > Create new scenario
Create New Make Scenario
Start by setting up a new automation scenario in Make. This creates the foundation for connecting Google Calendar to Slack.
- 1Log into your Make account and click 'Create a new scenario'
- 2Click the gray '+' circle in the center of the canvas
- 3Search for 'Google Calendar' and select it from the results
Google Calendar Module > Watch Events
Configure Google Calendar Trigger
Set up the trigger to watch for new events in your shared calendar. This module fires whenever someone adds a meeting.
- 1Select 'Watch Events' from the Google Calendar trigger options
- 2Click 'Add' next to Connection and authenticate with your Google account
- 3Choose your shared team calendar from the Calendar ID dropdown
- 4Set 'Limit' to 10 to avoid overwhelming Slack during initial sync
Google Calendar Module > Run once
Test Calendar Connection
Run a test to verify Make can read events from your calendar. This confirms the authentication and permissions are working.
- 1Click 'Run once' at the bottom of the Google Calendar module
- 2Wait for the test to complete (usually 10-15 seconds)
- 3Review the sample event data in the output panel
Add Module > Slack > Create a Message
Add Slack Module
Connect Slack as the destination for your notifications. This module will send the formatted message to your chosen channel.
- 1Click the '+' icon to the right of the Google Calendar module
- 2Search for 'Slack' and select it from the app list
- 3Choose 'Create a Message' as the action type
Slack Module > Connection > Add
Connect Slack Workspace
Authenticate Make with your Slack workspace to enable message posting. You'll need admin permissions or pre-approval for the Make app.
- 1Click 'Add' next to Connection in the Slack module
- 2Select 'Slack' (not Slack Legacy) from the connection types
- 3Click 'Continue' to open Slack's authorization window
- 4Grant Make permission to post messages in your workspace
Slack Module > Channel
Select Target Channel
Choose which Slack channel receives the calendar notifications. Pick a channel where your team discusses scheduling or general updates.
- 1Click the Channel dropdown in the Slack module
- 2Select your target channel from the list (e.g., #general or #calendar)
- 3If the channel doesn't appear, type the channel name manually with the # prefix
start.dateTime: {{start.dateTime}}
end.dateTime: {{end.dateTime}}
Slack Module > Text > Data Mapping
Map Event Title and Time
Build the notification message using calendar event data. Start with the event title and start time for basic context.
- 1Click in the Text field of the Slack module
- 2Type 'New meeting: ' then click the data picker icon
- 3Select 'Summary' from the Google Calendar data (this is the event title)
- 4Add a new line and type 'Time: ' followed by the 'Start' field from calendar data
Slack Module > Text > Data Mapping
Add Attendees and Location
Include attendee information and meeting location to make notifications more useful for team coordination.
- 1Add another line in the Text field and type 'Attendees: '
- 2Click the data picker and select 'Attendees > Email' from calendar data
- 3Add a final line with 'Location: ' and map the 'Location' field
- 4If location is often empty, add fallback text like 'TBD'
Scenario > Run once
Test Complete Workflow
Run the full scenario to verify Google Calendar data flows correctly to Slack. This catches any mapping or formatting issues.
- 1Click 'Run once' at the bottom left of the scenario
- 2Wait for both modules to execute (Google Calendar → Slack)
- 3Check your Slack channel for the test notification message
- 4Verify all mapped fields display correctly in the message
Module > Right-click > Add error handler
Configure Error Handling
Set up proper error handling so the scenario doesn't break if Google Calendar or Slack has issues. This prevents silent failures.
- 1Right-click the Slack module and select 'Add error handler'
- 2Choose 'Ignore' as the error handler type
- 3Click the settings gear on the Google Calendar module
- 4Set 'Processing error' to 'Break' to stop execution on API failures
Scenario > Schedule > Every 15 minutes
Set Scenario Schedule
Configure how often Make checks for new calendar events. More frequent polling catches events faster but uses more operations.
- 1Click the clock icon at the bottom left of the scenario
- 2Select 'Every 15 minutes' for good responsiveness without burning operations
- 3For high-traffic calendars, consider 'Every 5 minutes'
- 4Click 'OK' to save the schedule
Scenario > Toggle ON > Save
Activate and Monitor
Turn on the scenario and monitor initial performance. Watch for any unexpected behavior or high operation usage.
- 1Click the 'ON' toggle switch in the bottom left
- 2Save the scenario with a descriptive name like 'Calendar → Slack Notifications'
- 3Monitor the execution history for the first few runs
- 4Check operation usage in your Make dashboard after 24 hours
Drop this into a Make custom function.
JavaScript — Custom Function{{formatDate(start.dateTime; "MMM D, YYYY at h:mm A"; "America/New_York")}}▸ Show code
{{formatDate(start.dateTime; "MMM D, YYYY at h:mm A"; "America/New_York")}}... expand to see full code
{{formatDate(start.dateTime; "MMM D, YYYY at h:mm A"; "America/New_York")}}Scaling Beyond 5+ calendars or 20+ events/day+ Records
If your volume exceeds 5+ calendars or 20+ events/day records, apply these adjustments.
Switch to webhook triggers
Google Workspace Enterprise supports push notifications that eliminate polling operations. Configure domain-wide delegation and webhook endpoints in Make to get instant event notifications without 15-minute delays.
Add calendar filtering
Use Make's filter module to process only specific event types or calendars. Filter by keywords in titles, specific attendee domains, or location fields to reduce unnecessary Slack messages and operation usage.
Batch notifications
Instead of one message per event, use Make's aggregator to collect multiple events and send a daily digest to Slack. This works well for high-frequency calendars where individual notifications become noise.
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 reliable polling and complex message formatting. Make checks Google Calendar every 15 minutes consistently, and its data mapping interface handles attendee arrays and date formatting better than basic webhook tools. The visual builder makes it easy to add filters for specific calendars or event types. Skip Make for N8n if you're self-hosting and want to avoid monthly fees — the functionality is nearly identical.
This workflow costs about 150-200 operations monthly for a team calendar with 2-3 events per day. That includes 96 operations for polling checks plus 1 operation per notification sent. Make's Free plan covers 1,000 operations, so you're well within limits. The Core plan at $9/month handles 10,000 operations if you add more calendars. Zapier's Starter plan costs $20/month for the same volume, making Make 55% cheaper.
Zapier triggers faster with webhook support for Google Calendar, catching new events within 30 seconds instead of Make's 15-minute polling delay. N8n offers the same visual workflow builder as Make but with unlimited operations if you self-host. However, Make's Google Calendar integration includes better error handling for API rate limits and automatically formats complex fields like recurring event patterns that trip up other platforms.
Google Calendar's API has quirks that surface after a few weeks. All-day events return dates in YYYY-MM-DD format while timed events use full ISO timestamps — your Slack messages will look inconsistent unless you add date formatting. The API also rate-limits at 100 requests per 100 seconds per user, so teams with multiple active calendars might hit throttling during busy periods. Make handles this automatically, but you'll see delayed notifications when it happens.
Ideas for what to build next
- →Add meeting reminders — Create a second scenario that watches for events starting in 1 hour and sends reminder messages to the same Slack channel with @channel mentions.
- →Log events to Google Sheets — Branch your workflow to also save meeting details to a Google Sheets log for attendance tracking and meeting analytics.
- →Create Slack threads for updates — Store the Slack message ID and create threaded replies when the same calendar event gets updated or cancelled.
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