Daily calendar meeting summary posted to Slack by Gemini

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.