--- title: "Daily calendar meeting summary posted to Slack by Gemini" kind: "Kit" category: "Productivity" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/5d086eb6-c94b-41b0-9d51-72c649fbb558" updated: "2026-11-12" --- # Daily calendar meeting summary posted to Slack by Gemini > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow that runs every morning at 9:00. A Gemini-powered AI Agent reads today’s events from Google Calendar, writes a short summary that names every attendee, and posts it to a Slack channel. Daily calendar meeting summary posted to Slack by Gemini is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-12. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n. ## About ### What it is This n8n workflow posts a summary of your day’s meetings to Slack each morning. A schedule starts it at 9:00. An AI Agent, thinking with a Google Gemini chat model, asks a Google Calendar tool for today’s events and writes the summary, naming every attendee. The workflow strips the markdown and posts the text to a Slack channel. Five nodes do the work, beside four sticky notes. ### Who it suits Managers, assistants and small teams who live in Slack and want the day’s meetings in front of them before work starts. Skip it if you need several calendars, or if someone should read the summary first. As imported, it posts at once. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Startups | Founders | See the day’s calls and who is on them without opening the calendar | A founder gets a post listing three investor calls and the people invited to each. | | Agencies | Account leads | Share the day’s client meetings with the whole team | A lead posts the summary in the team channel before the 10:00 stand-up. | | Support | Team managers | Plan coverage around the day’s internal meetings | A manager sees that two people share a training slot and plans the queue around it. | | Operations | Executive assistants | Send an executive a morning rundown | An assistant points the post at a private channel that only the executive reads. | You need a little n8n: import a file, add three credentials, and pick a calendar and a Slack channel. ### Where to use it Any n8n that can reach Google and Slack will run it. The summary lands in the Slack channel you choose. - n8n Cloud: import the file into a new workflow there - Your own n8n server: the same file and steps - A team channel: everyone sees the day’s meetings - A private channel: a rundown for one person ### How to set it up Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Three accounts are involved, one for each service. What you need first | Need | Detail | | --- | --- | | n8n | On n8n Cloud or on a server of your own | | Google Gemini | An API key, for a Google Gemini(PaLM) credential | | Google Calendar | A Google account with the calendar to read, signed in through a Google Calendar credential | | Slack | A Slack credential and the channel that gets the post | 1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`. 2. Open `Google Gemini Chat Model` and add a Google Gemini(PaLM) credential with your key. 3. Open `Google Calendar Get Events`, add a Google Calendar credential and choose your calendar in Calendar. 4. Open `Send response back to slack channel`, add a Slack credential and choose the channel in Channel. 5. Save, press Execute workflow once and check that the summary reaches Slack. 6. Press Publish so the 9:00 schedule runs. ### How to use it Nothing to press after that. Each morning the agent reads that day’s events, from 00:00:00 to 23:59:59, and the summary appears in Slack with the word Gemini in front. What to change for a different result | To change | Where | | --- | --- | | The model | Model in \`Google Gemini Chat Model\` | | The time | Trigger at Hour in \`Schedule Trigger\` | | What the summary covers | The prompt and the System Message option in \`Calendar AI Agent\` | | The calendar | Calendar in \`Google Calendar Get Events\` | | The channel and the lead-in word | Channel and the text in \`Send response back to slack channel\` | ### Example A team lead has a 10:00 stand-up with five people, a 13:00 client call and a 16:00 review. At 9:00 the agent asks the calendar for that day’s events. The agent lists the three meetings in order and names who is invited to each, since its instructions ask for every attendee. Slack shows the text as a post that begins with Gemini. ### For newcomers and experts **If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. Here the agent sits in the middle, with its model and its calendar tool plugged in underneath. Press Execute workflow, then open the run to see what the agent asked the calendar for. **For experts.** The prompt carries today’s start and end from `$now`, and the agent fills the tool’s two date fields with `$fromAI`. Where to look closer | Node | What it does | What to know | | --- | --- | --- | | \`Schedule Trigger\` | Version 1.2 with the hour set to 9 | The interval is one day and the minute is 0, in the workflow’s time zone | | \`Calendar AI Agent\` | AI Agent 1.7 with a defined prompt and a system message | It has no memory, and its system message asks for every attendee | | \`Google Calendar Get Events\` | Google Calendar tool 1.2, set to get many events | It returns up to 50, since Return All is off and the limit starts at 50 | | \`Send response back to slack channel\` | Slack 2.1, posting a message | Its text is \`Gemini : \` plus the answer with \`removeMarkdown()\` applied | ### Good to know The summary goes to Slack at once, and a recurring meeting may be missed. - Models: Google’s deprecations page, read on 12 November 2026, no longer lists any Gemini 1.5 model, and its models page lists none. Mindket’s copy asks for \`models/gemini-3.6-flash\`, which that models page badges Stable - Recurring meetings: Expand Events is off in this tool version, so a recurring meeting comes back as its original entry, not as today’s date. Turn it on under Options in \`Google Calendar Get Events\` to list each instance - Empty pickers: the author’s own calendar and Slack channel are gone. Choose yours before the first run - Billing: each run is one agent call, and the agent can call the model more than once - No review: the summary is posted without anyone reading it first - Your data: event titles and attendees go to Google’s Gemini API, and the summary goes to Slack - Credentials: the JSON holds none ## README ```markdown # Daily calendar meeting summary posted to Slack by Gemini An n8n workflow that runs every morning at 9:00. An AI Agent run by a Google Gemini chat model asks a Google Calendar tool for today's events, writes a short summary that names every attendee, and posts it to a Slack channel. ## What is inside - `workflow.json`: the workflow as n8n exports it, five working nodes (the schedule, the agent, its model, its calendar tool and the Slack post) and four sticky notes. It holds no credential. - `README.md`: these notes. ## What we changed from the original copy - The Gemini model was `models/gemini-1.5-flash-latest`. Google's deprecations page, read on 12 November 2026, no longer lists any Gemini 1.5 model, and neither does its models page. The node now asks for `models/gemini-3.6-flash`, which that models page badges Stable. - The Slack channel and the calendar were the author's own, picked from a list. Both pickers are now empty, so choose yours. - The calendar tool node was named with a spaced hyphen. It is now `Google Calendar Get Events`. - The credential links and the Slack node's webhook ID are gone. - Nothing else. The file has no Code node. ## Before you start - An n8n instance, on n8n Cloud or your own server. - A Google Gemini API key, for the Google Gemini(PaLM) credential. - A Google account whose calendar the agent may read, signed in to n8n through the Google Calendar credential. - A Slack workspace, a Slack API credential and the channel that should get the summary. ## Set it up 1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`. 2. Open `Google Gemini Chat Model` and add a Google Gemini(PaLM) credential with your key. 3. Open `Google Calendar Get Events`, add a Google Calendar credential and choose your calendar in Calendar. 4. Open `Send response back to slack channel`, add a Slack credential and choose the channel in Channel. 5. Save, press Execute workflow once and check that the summary reaches Slack. 6. Publish the workflow so the 9:00 schedule runs. ## How a run goes 1. `Schedule Trigger` (version 1.2) starts the run at 9:00 every day. Its rule sets only the hour, so the interval is one day and the minute is 0. The time zone is the workflow's, or the n8n instance's when the workflow sets none. 2. `Calendar AI Agent` (AI Agent 1.7) gets a prompt that asks it to summarize today's meetings, with a start of 00:00:00 and an end of 23:59:59 for today's date. Its system message tells it to base answers on the current date, to format the dates as `YYYY-MM-DD HH:mm:ss` and to mention every attendee. It has no memory. 3. `Google Gemini Chat Model` is the model the agent thinks with. 4. `Google Calendar Get Events` is the agent's tool. It lists events between the two dates the agent fills in. 5. `Send response back to slack channel` (Slack 2.1) posts the agent's answer, with the markdown stripped and `Gemini : ` in front, to the channel. ## Change the look - The model: Model in `Google Gemini Chat Model`. - The time: Trigger at Hour in `Schedule Trigger`. - What the summary covers: the prompt in `Calendar AI Agent` and its System Message option. - The calendar: Calendar in `Google Calendar Get Events`. - The channel and the lead-in word: Channel and the text in `Send response back to slack channel`. ## Good to know - Each run is one agent call. The agent can call the model more than once, so Gemini may bill more than one request. - The tool returns up to 50 events, since its Return All switch is off and its limit starts at 50. - In this tool version Expand Events is off, so a recurring meeting comes back as its original entry, not as today's date. The summary can then miss it or show its first start time. Turn on Expand Events under Options in the tool to list each instance. - The summary goes to Slack at once. Nobody reads it first. - The calendar's event titles and attendees go to Google's Gemini API, and the summary goes to Slack. ``` ## What is in it 3 files, 10 KB, downloaded as a zip. ```text NOTICE.md 614 B README.md 4 KB workflow.json 6 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 3 steps, starting on a schedule - AI: 1 step calls an AI model: Calendar AI Agent - Sign-ins: Signs in to: Google Calendar, Slack and Google Gemini - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 3 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/5d086eb6-c94b-41b0-9d51-72c649fbb558) - [Its page on Mindket](https://mindket.com/p/5d086eb6-c94b-41b0-9d51-72c649fbb558)