Turn a week of MeetGeek recordings into one AI-written Slack digest
Pull the last week of meetings from MeetGeek, have an AI Agent fetch and summarise each one with action items, then post a single formatted digest to Slack instead of scrolling through recordings.
What this looks like
One step on screen at a time. Read it, do it, tap Next.
Turn a week of MeetGeek recordings into one AI-written Slack digest
Step 1 of 13
Run on a schedule with the Schedule Trigger
Create a workflow and add a Schedule Trigger node. This kicks off the digest run — once a week is enough since the workflow itself filters down to the last seven days of meetings.
Checkpoint
A Schedule Trigger sits on the canvas as the workflow's starting node.
Before you begin
Tick these off as you sort them. Stopping halfway to create an account is how a fifteen-minute build becomes an hour.
0 of 8 ready
Ticks are saved on this device, so you can come back to them.
- API key
MeetGeek needs to have already recorded and transcribed your meetings. The workflow reads its meeting list and per-meeting summary endpoints with a bearer token.
- API key
Powers the AI Agent that reads each meeting's notes and writes the actual summary and action items.
- Credential
Used to send the finished digest as a formatted block message into a channel your team actually reads.
- Permission
The template posts into a channel named meeting-notes. Create one, or repoint the Slack node at whichever channel you use.
- Time
Most of the setup is wiring the AI Agent's tool correctly so it actually calls the summary endpoint per meeting.
The basics — ticked once, remembered everywhere
- Account
Either the hosted version or a self-hosted install. Everything here works the same on both — the only visible difference is the shape of your webhook URLs.
Create a workspace - Know-how
Adding a node, connecting two of them, and pressing Execute. If any of that is new, the free primer covers it in about ten minutes.
- Credential
You will paste at least one secret during setup. A password manager beats a notes app, and it stops you pasting a live key into a chat window by accident.
The shape of the workflow
The nodes you will end up with, left to right, in the order you add them.
4 things to set here- 1Schedule Trigger — the trigger — everything starts here
- 2HTTP Request — Get meetings list
- 3Split Out — Split meetings
- 4Edit Fields (Set) — Add custom name for meeting id
Skip the node hunting
Import a starter file with every node for this build already on the canvas, named after its step and wired in order, each one carrying a sticky note with the values to enter. You still connect your own accounts and fill the fields — that is what the walkthrough takes you through — but you never start at a blank canvas.
In n8n: Workflows → Import from file.
What you will build
Jump straight to any step, or print the list and tick it off beside your n8n tab.
- 1Run on a schedule with the Schedule Trigger
- 2Get meetings list
- 3Split meetings
- 4Add custom name for meeting id
- 5Format date
- 6Keep only the last week with AI Transform
- 7Summarise each meeting with the AI Agent
- 8Restructure to slack block
- 9Send a message
- 10Activate the workflow
- 11Run manually with a handful of recent meetings
- 12Check the AI Agent's tool call actually fires
- 13Read the final Slack message against the source recordings
If something goes wrong
Everything ready?
Start walkthrough