Google Calendar to Slack, daily meeting digests
Your day shouldn’t start with five calendar tabs, two time zones, and one big question: “What am I actually doing today?” But that’s the reality in a lot of teams. Meetings live in different Google Calendars, invites get missed, and the “join link” hunt starts five minutes before every call.
Ops leads feel it when the whole team is late. Team managers feel it when priorities get fuzzy. And if you run a small agency, you feel it when client calls sneak up on you. This calendar Slack digest automation turns scattered schedules into one clear daily message, which means fewer surprises and fewer pings asking for links.
Below you’ll see how the workflow runs, what it sends, and what you can tweak so it matches how your team communicates.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Calendar to Slack, daily meeting digests
flowchart LR
subgraph sg0["Scheduled Automation Start Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Automation Start", pos: "b", h: 48 }
n1@{ icon: "mdi:robot", form: "rounded", label: "Intelligent Agent Core", pos: "b", h: 48 }
n2@{ icon: "mdi:brain", form: "rounded", label: "Gemini Chat Engine", pos: "b", h: 48 }
n3@{ icon: "mdi:location-exit", form: "rounded", label: "Calendar Tool B", pos: "b", h: 48 }
n4@{ icon: "mdi:location-exit", form: "rounded", label: "Calendar Tool A", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/discord.svg' width='40' height='40' /></div><br/>Dispatch Discord Update"]
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/whatsapp.svg' width='40' height='40' /></div><br/>Send WhatsApp Alert"]
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Post Slack Notification"]
n1 --> n7
n1 --> n5
n1 --> n6
n0 --> n1
n4 -.-> n1
n3 -.-> n1
n2 -.-> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n1 ai
class n2 aiModel
classDef customIcon fill:none,stroke:none
class n5,n6,n7 customIcon
The Problem: Daily meetings are scattered (and easy to miss)
When meetings are spread across multiple Google Calendars, the day becomes a constant “check and re-check” loop. Someone has a personal calendar. Someone else has a shared team calendar. Client calls sit in a separate account. You can technically find everything, but it’s slow and it’s distracting. Worse, the important details aren’t obvious. Start time, duration, location, join link, and which meetings actually matter today all get buried in invite clutter.
It adds up fast. Not in one dramatic failure, but in dozens of tiny interruptions.
- You waste about 15 minutes each morning scanning calendars, then repeating the scan after a reschedule.
- Join links get lost in invite text, so people ask in Slack right before the call.
- Time zone confusion turns “10 AM” into a mini investigation.
- Important meetings don’t stand out, so prep time disappears and calls feel reactive.
The Solution: One daily digest, posted where your team already works
This n8n workflow pulls today’s events from multiple connected Google Calendars, asks an AI agent to turn that raw list into a clean summary, then posts it to your chosen channels. It runs automatically on a schedule (commonly 9 AM), so nobody has to remember to “send the agenda” or paste links manually. The AI formatting matters here. Instead of a messy export, you get a readable list with meeting title, time, duration, and a link to join. Then the workflow distributes that same digest to Slack, Discord, and WhatsApp, so your team sees it in the tool they actually open first.
The workflow starts with a daily schedule trigger. From there, the agent fetches meetings from your connected calendars using Google Calendar tools, then formats a structured digest with Google Gemini. Finally, n8n posts the digest into Slack (and optionally Discord and WhatsApp) so the whole day is visible at a glance.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you have 3 calendars to check (personal, team, and client calls). A quick scan is maybe 5 minutes each, plus another 10 minutes during the day as things shift, so you’re at about 25 minutes daily. With this workflow, you spend about 5 minutes once to connect calendars and pick a Slack channel, then the 9 AM digest just shows up. Even if the AI takes a minute to format, it’s still “done” without you thinking about it.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Calendar to pull events from your calendars
- Slack to post the daily digest to a channel
- Google Gemini account (enable it in Google AI Studio/Cloud)
Skill level: Beginner. You’ll connect accounts, pick channels, and tweak the prompt text if you want a different format.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A daily schedule kicks things off. The workflow runs at a set time (often 9 AM) so the digest hits before the day gets noisy.
Your calendars are pulled in one pass. The AI agent uses connected Google Calendar tools to fetch today’s meetings from each calendar you’ve authorized.
AI turns “raw events” into something readable. Google Gemini formats the list into a structured digest with the details people actually need, including join links.
The digest gets dispatched where you work. n8n posts to Slack by default, and it can send the same message to Discord and WhatsApp for teams that live outside Slack.
You can easily modify the schedule time to match your team’s start and adjust the message format to match your tone based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
This workflow begins on a scheduled cadence using the built-in trigger node.
- Add and open Scheduled Automation Start.
- Define the schedule that should initiate the workflow (e.g., hourly, daily) inside Scheduled Automation Start.
- Confirm the trigger connects directly to Intelligent Agent Core.
Step 2: Set Up the AI Agent and Language Model
The agent coordinates logic and uses a Gemini chat model to generate responses before sending notifications.
- Open Intelligent Agent Core and review its agent settings for your intended behavior.
- Attach Gemini Chat Engine as the language model for Intelligent Agent Core.
- Credential Required: Connect your Google Gemini credentials in Gemini Chat Engine.
⚠️ Common Pitfall: If Gemini Chat Engine is not connected as the language model, Intelligent Agent Core will not generate any AI output.
Step 3: Connect Calendar Tools to the Agent
The agent can call Google Calendar tools for context or event lookups. These tools are connected as AI tools.
- Open Calendar Tool A and Calendar Tool B and confirm they are connected to Intelligent Agent Core via the AI tool connection.
- Credential Required: Connect your Google Calendar credentials in Calendar Tool A.
- Credential Required: Connect your Google Calendar credentials in Calendar Tool B.
Calendar Tool A and Calendar Tool B are AI tools for Intelligent Agent Core, so ensure the agent references them in its instructions as needed.
Step 4: Configure the Notification Outputs
The agent sends updates to multiple channels simultaneously. Intelligent Agent Core outputs to both Post Slack Notification and Dispatch Discord Update and Send WhatsApp Alert in parallel.
- Open Post Slack Notification and set the destination channel and message format.
- Credential Required: Connect your Slack credentials in Post Slack Notification.
- Open Dispatch Discord Update and set the target channel and message content.
- Credential Required: Connect your Discord credentials in Dispatch Discord Update.
- Open Send WhatsApp Alert and configure the recipient and message template.
- Credential Required: Connect your WhatsApp credentials in Send WhatsApp Alert.
⚠️ Common Pitfall: If any of the three output nodes lack credentials, the parallel branch will partially fail and you may miss notifications in those channels.
Step 5: Test and Activate Your Workflow
Run a manual test to verify the agent, tools, and notifications are working before turning on the schedule.
- Click Execute Workflow and verify Scheduled Automation Start triggers Intelligent Agent Core.
- Confirm successful parallel execution by checking results in Post Slack Notification, Dispatch Discord Update, and Send WhatsApp Alert.
- Review logs to ensure Gemini Chat Engine and both calendar tools were accessible by Intelligent Agent Core.
- When satisfied, toggle the workflow to Active to enable scheduled production runs.
Common Gotchas
- Google Calendar credentials can expire or need specific permissions. If things break, check the Google connection status in your n8n credentials list first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 20 minutes if your accounts are ready.
No. You’ll connect Google Calendar and Slack, then edit a few fields like the channel name and schedule time.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Google Gemini usage costs, which depend on your model and volume.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. You can change the schedule time in the “Scheduled Automation Start” node, then adjust the AI agent prompt so the digest matches your team (bullets, grouped by owner, “top 3 critical meetings,” whatever you want). If Slack isn’t the only destination, keep Slack and also enable the Discord and WhatsApp dispatch nodes. Many teams also add a second Slack message for a leadership-only channel that only includes the “important” meetings.
Usually it’s expired or revoked Slack permissions, especially if the app was reinstalled or the channel was changed. Reconnect Slack in n8n Credentials, then confirm the workflow is posting to a channel the bot is actually a member of. If you’re posting to a private channel, you must invite the bot to it. Also check Slack rate limits if you’re sending digests to multiple channels at once.
For most small teams, “a full day of meetings” is fine. On n8n Cloud, your ceiling is mainly your monthly execution limit and the AI model usage; if you self-host, the practical limit is your server and how big you let the digest get. If you regularly have 50+ events in a day across calendars, consider filtering to business hours or excluding low-signal calendars.
Often, yes, because the “AI formatting + multi-calendar pulling + multi-channel posting” is more natural in n8n. You can branch logic without paying extra per path, and self-hosting avoids the feeling that every extra step costs more. Zapier and Make are still great for quick two-app automations, frankly. If all you need is “post today’s events,” they might be faster to launch. If you want a polished digest with rules and custom formatting, n8n is the better long-term home. Talk to an automation expert if you want help choosing.
Once this is running, your team starts the day with clarity instead of calendar archaeology. Set it up once, then let the digest do its quiet, useful job.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
