What happens if the meeting organizer isn't in our Slack workspace?

The Slack module will fail with 'user_not_found' error. Add a filter before the Slack step to check if the organizer email contains your company domain, or use a fallback to DM a default person like the meeting room admin.

Can I customize the reminder message based on meeting type?

Yes, use Make's conditional text formulas to check the meeting title or description for keywords like 'client', 'standup', or 'all-hands' and modify the message accordingly. Add these conditions in the Slack message field.

Why don't reminders work for recurring meetings?

Recurring meetings often use the 'date' field instead of 'dateTime' for all-day events, which breaks the end-time filter. Add a parallel branch to handle recurring events with different field mapping.

How do I prevent reminders for meetings that already have notes shared?

Make can't automatically detect if notes were shared unless they're posted in a specific Slack channel. You could monitor a #meeting-notes channel and cross-reference, but that requires a more complex scenario with data storage.

Beginner~12 min setupProductivity & CommunicationVerified April 2026

How to Send Meeting Notes Reminders to Slack with Make

Automatically DM the meeting organizer in Slack 15 minutes after a Google Calendar event ends to remind them to share meeting notes.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Make

Also on:Zapier N8n Power-automate Pipedream

Best for

Teams that want consistent follow-up on meeting notes without manual tracking.

Not ideal for

Companies where meeting organizers and note-takers are different people.

Sync type

scheduled

Use case type

notification

Real-World Example

💡

A 25-person marketing agency uses this to ensure client meeting notes get shared within an hour of each call ending. Before automation, account managers would forget to distribute notes 30% of the time, leaving team members confused about next steps and deliverables. Now every client call gets automatic follow-up, improving project coordination.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

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

Skip the setup

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.

Google Calendar with meeting events that have clear start/end times

Slack workspace where you can install apps or admin approval

Meeting organizers use the same email for Google and Slack accounts

Make account with available operations (free tier includes 1,000/month)

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Meeting Title	`summary`	Event title from Google Calendar to include in the reminder message
Organizer Email	`organizer.email`	Email address of meeting creator, used to find their Slack user ID
End Time	`end.dateTime`	Meeting end timestamp to calculate when 15-minute delay should start
Event Status	`status`	Meeting status (confirmed/cancelled/tentative) to filter out cancelled meetings

1 optional field▸ show

Calendar ID calendar.id Which calendar the meeting belongs to, useful for filtering work vs personal events

Step-by-Step Setup

Dashboard > Create scenario > Google Calendar > Watch Events

Create new scenario in Make

Start a new workflow that will monitor calendar events and send Slack DMs. This scenario will need two main modules connected in sequence.

1Click the blue 'Create a new scenario' button on your Make dashboard
2Click the large gray '?' circle to add your first module
3Search for 'Google Calendar' in the app list
4Select 'Watch Events' from the Google Calendar triggers

✓ What you should see: You should see a Google Calendar module with 'Watch Events' selected as your first step in the scenario builder.

Google Calendar module > Connection > Add

Connect Google Calendar account

Authenticate your Google account so Make can read calendar events. This creates the connection for monitoring meeting end times.

1Click 'Add' next to the Connection field
2Enter a connection name like 'Work Calendar'
3Click 'Save' then 'Continue' to open Google's auth window
4Select your Google account and grant calendar permissions

✓ What you should see: The connection dropdown shows your new connection name with a green checkmark icon.

⚠

Common mistake — Make sure you're logged into the correct Google account before clicking Continue — switching accounts mid-auth causes connection errors.

Make settings

Connection

Choose a connection…Add

click Add

Google Calendar

Authorize Make

popup window

✓

Connected

green checkmark

Google Calendar module > Settings

Configure calendar event monitoring

Set which calendar to watch and what types of events to monitor. Focus on events that typically need follow-up notes.

1Select your primary calendar from the 'Calendar ID' dropdown
2Set 'Watch Events' to 'Updated Events'
3Leave 'Max Results' at 10
4Set the scenario to run every 5 minutes

✓ What you should see: The module shows your calendar name selected and 'Updated Events' as the watch type.

⚠

Common mistake — Don't choose 'New Events' — you need 'Updated Events' to detect when meetings actually end.

Between modules > Filter > Add conditions

Add event status filter

Filter for events that have ended, not started or been updated during the meeting. This prevents sending reminders for cancelled or rescheduled meetings.

1Click the wrench icon between modules to add a filter
2Name the filter 'Event Ended'
3Set condition: 'status' equals 'confirmed'
4Add second condition: 'end.dateTime' is before 'now'

✓ What you should see: A filter module appears between your trigger and the next step, showing your two conditions.

⚠

Common mistake — Use 'end.dateTime' not 'end.date' — all-day events use a different field format and won't trigger properly.

Google Calendar

trigger

filter

Status

matches criteria?

yes — passes through

no — skipped

Slack

notified

Add module > Tools > Sleep

Add 15-minute delay

Wait exactly 15 minutes after the meeting ends before sending the reminder. This gives attendees time to wrap up and the organizer time to collect their thoughts.

1Click the '+' button to add a new module
2Search for 'Tools' in the app list
3Select 'Sleep' from the Tools options
4Set delay to 900 seconds (15 minutes)

✓ What you should see: A Sleep module shows with '900' in the delay field and displays '15 minutes' as confirmation.

Add module > Slack > Send a Direct Message

Add Slack connection

Connect your Slack workspace to enable sending direct messages to meeting organizers. This requires admin permissions in most workspaces.

1Click '+' to add another module
2Search for 'Slack' and select it
3Choose 'Send a Direct Message' action
4Click 'Add' to create a new Slack connection

✓ What you should see: The Slack module appears with 'Send a Direct Message' selected and a connection field ready for setup.

⚠

Common mistake — Your Slack admin may need to approve the Make app first — check with them if the auth window shows 'pending approval'.

Slack module > Connection > Add

Authenticate Slack workspace

Complete the OAuth flow to connect Make with your Slack workspace. This grants permission to send DMs and lookup user information.

1Name the connection after your workspace (e.g., 'Acme Corp Slack')
2Click 'Save' then 'Continue' to open Slack auth
3Select your workspace from the dropdown
4Click 'Allow' to grant Make the necessary permissions

✓ What you should see: The connection dropdown shows your workspace name with a green connected status.

⚠

Common mistake — If you're in multiple Slack workspaces, double-check you're authorizing the correct one — Make can't switch workspaces after connection.

Slack module > User field > Map data

Map organizer email to Slack user

Find the meeting organizer's Slack user ID using their email from Google Calendar. This ensures the DM goes to the right person.

1In the 'User' field, click the mapping icon
2Select 'organizer.email' from the Google Calendar data
3Make will automatically convert email to Slack user ID
4Verify the mapping shows the email field selected

✓ What you should see: The User field displays '{{1.organizer.email}}' showing it will use the calendar organizer's email.

⚠

Common mistake — This only works if the organizer's Google email matches their Slack email — mismatches will cause 'user not found' errors.

Google Calendar fields

summary

description

start.dateTime

end.dateTime

location

available as variables:

1.props.summary

1.props.description

1.props.start.dateTime

1.props.end.dateTime

1.props.location

Slack module > Text field

Write the reminder message

Create a helpful DM that includes the meeting title and a clear call-to-action. Keep it friendly but direct.

1Click in the 'Text' field
2Type: 'Hi! Friendly reminder to share notes from '
3Map the 'summary' field from Google Calendar
4Add: '. The team would appreciate having them in the next hour. Thanks!'

✓ What you should see: The message field shows your text with '{{1.summary}}' inserted for the meeting title.

⚠

Common mistake — Don't make the message too long — Slack DMs over 3 lines often get ignored as spam.

Message template

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Bottom toolbar > Run once

Test the scenario

Run a test with sample data to verify the flow works before going live. This catches mapping errors and permission issues.

1Click 'Run once' button at the bottom left
2Wait for the scenario to check your calendar
3Review any events it found in the execution log
4Check if test messages were sent (if recent meetings exist)

✓ What you should see: The execution log shows green checkmarks for each module and displays any calendar events processed.

⚠

Common mistake — If you have recent meetings, this test will send real DMs — warn your team or test with a personal calendar first.

Make

▶ Run once

executed

✓

Google Calendar

✓

Slack

🔔 notification

received

Top bar > ON/OFF toggle

Schedule the scenario

Turn on automatic execution so Make continuously monitors for ended meetings. The 5-minute interval balances responsiveness with operation usage.

1Click the toggle switch labeled 'OFF' near the scenario name
2Confirm the schedule is set to 'Every 5 minutes'
3Click 'OK' to activate the scenario
4Verify the toggle now shows 'ON' in blue

✓ What you should see: The scenario status shows 'ON' with a blue toggle and displays 'Every 5 minutes' as the schedule.

⚠

Common mistake — Confirm your workflow timezone matches your business timezone — n8n uses the instance timezone by default. Also verify the workflow is saved and set to Active, since Schedule Triggers won't fire on inactive workflows.

Drop this into a Make custom function.

JavaScript — Custom Function{{if(contains(1.summary; "standup") or contains(1.summary; "1:1") or contains(1.summary; "coffee"); "skip"; 1.summary)}}

▸ Show code

{{if(contains(1.summary; "standup") or contains(1.summary; "1:1") or contains(1.summary; "coffee"); "skip"; 1.summary)}}

... expand to see full code

{{if(contains(1.summary; "standup") or contains(1.summary; "1:1") or contains(1.summary; "coffee"); "skip"; 1.summary)}}

Scaling Beyond 100+ meetings/week+ Records

If your volume exceeds 100+ meetings/week records, apply these adjustments.

Batch process calendar checks

Change the trigger schedule from every 5 minutes to every 15 minutes to reduce API calls. The slight delay won't matter for a 15-minute reminder window.

Add meeting type filters

Filter out recurring daily standups, 1:1s, and other meetings that rarely need formal notes. This cuts operation usage by 40-60% in most organizations.

Use data store for deduplication

Google Calendar triggers fire multiple times as attendees join/leave. Store processed meeting IDs to prevent sending 3-4 reminders for the same event.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test with a meeting that has the same attendees as your typical team calls

Applies when: Always

Add error handling to continue scenario even if one Slack DM fails

Applies when: Always

Set up email notifications for scenario failures in Make settings

Applies when: Always

Verify the Sleep module delay accounts for timezone differences if your team spans multiple zones

Applies when: Enterprise

Add a data store to prevent duplicate reminders for meetings updated multiple times

Applies when: High volume

Create a filter to exclude recurring daily standups or other meetings that don't need notes

Applies when: Always

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Make for this workflow

Use Make for this if you need reliable timing control and your team already uses Google Calendar + Slack daily. Make's Sleep module gives you exact 15-minute delays, while the visual builder makes it easy to add filters for meeting types or specific calendars. Pick Zapier instead if you need this running in under 10 minutes — their setup wizard is faster than Make's module-by-module approach.

Cost

This workflow uses 3 operations per meeting (trigger + sleep + Slack DM). At 40 meetings per month, that's 120 operations total. Make's free tier covers 1,000 operations, so you won't hit limits until 300+ monthly meetings. The $9 Core plan handles up to 10,000 operations. Zapier's equivalent would need their $20 Starter plan since free only includes 100 tasks. Make wins on cost here.

Tradeoffs

Zapier handles the Google-to-Slack email matching more reliably — their built-in user lookup works even when emails don't match exactly. N8n lets you customize the reminder message with more complex logic, like different messages for all-hands vs team meetings. But Make's Sleep module timing is more precise than either competitor, and the visual debugger makes troubleshooting much easier when calendar webhooks act up.

You'll discover that Google Calendar's "updated" trigger fires multiple times per meeting as attendees join/leave calls that run over. Add a data store to prevent duplicate reminders. Also, all-day events use a different date format (date vs dateTime) that breaks the end-time filter. Your scenario will skip those entirely unless you add a separate branch to handle the different field structure.

Ideas for what to build next

→
Add meeting notes template — Create a follow-up automation that posts a notes template to the relevant Slack channel when the organizer responds to the reminder DM.
→
Track notes completion rate — Build a dashboard in Google Sheets that logs which meetings got reminders and whether notes were actually shared within 2 hours.
→
Escalate overdue notes — Set up a second reminder that pings the organizer's manager if notes aren't shared within 24 hours of the original reminder.