MeetGeek to Slack, meeting briefs with action items
You leave a meeting, then the real mess starts. Notes live in one place, action items live in someone’s memory, and the recap shows up late (if it shows up at all).
This MeetGeek Slack briefs automation hits project managers hardest, but ops leads and agency owners feel it too. Instead of chasing people for “what did we decide?”, you get a clean daily brief in Slack with owners and next steps.
Below you’ll see exactly what this workflow does, what you need to run it, and how to tailor the summary format so your team actually reads it.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: MeetGeek to Slack, meeting briefs with action items
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n1["<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/aitransform.svg' width='40' height='40' /></div><br/>AI Transform"]
n2@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
n3["<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/>Send a message"]
n4@{ icon: "mdi:web", form: "rounded", label: "summary", pos: "b", h: 48 }
n5@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-vertical", form: "rounded", label: "Add custom name for meeting id", pos: "b", h: 48 }
n7@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split meetings", pos: "b", h: 48 }
n8["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Get meetings list"]
n9@{ icon: "mdi:cog", form: "rounded", label: "Format date", pos: "b", h: 48 }
n10["<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/code.svg' width='40' height='40' /></div><br/>Restructure to slack block"]
n4 -.-> n5
n5 --> n10
n9 --> n1
n1 --> n5
n7 --> n6
n0 --> n8
n8 --> n7
n2 -.-> n5
n10 --> n3
n6 --> n9
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 n5 ai
class n2 aiModel
class n4,n8 api
class n10 code
classDef customIcon fill:none,stroke:none
class n1,n3,n8,n10 customIcon
Why This Matters: Meeting Recaps Get Lost in the Gaps
Meeting notes are only useful if they turn into decisions and follow-through. But in most teams, the recap is a manual task that competes with everything else, so it becomes inconsistent. One person shares a long transcript, another shares three bullets, and half the time the “real” action items never make it into Slack where work actually happens. Then you get the classic Friday scramble: “Wait, who owned that?” and “Did we agree to ship it?” It’s not just time. It’s trust and momentum leaking out of your week.
The friction compounds. Here’s where it breaks down.
- Someone has to open MeetGeek, find the right meeting, and copy-paste the important parts into Slack.
- Action items get buried in paragraphs, so owners miss them and the same tasks get re-discussed next meeting.
- Different recap styles across managers make it hard to scan quickly, which means people stop reading recaps altogether.
- When you have multiple meetings per day, the backlog of “I’ll send the notes later” turns into hours by the end of the week.
What You’ll Build: Daily MeetGeek Summaries Posted to Slack
This workflow runs on a schedule and pulls your most recent meetings from MeetGeek through an HTTP request. It then filters down to the meetings you actually care about (for example, “since yesterday” or “only meetings tagged for a project”), and sends each meeting summary through an AI step to create a tight brief plus action items. After that, it reshapes the content into Slack’s Block Kit format so the message is readable, skimmable, and consistent. Finally, it posts the brief to a Slack channel so the whole team sees what was decided and what needs to happen next. Set it once, and the daily “recap chore” mostly disappears.
The workflow starts with a Cron schedule. It pulls a meeting catalog, splits it into individual meetings, and fetches the full summary for each one. AI turns that raw content into clean decisions and action items, then a formatting step builds Slack blocks and sends the message.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say your team runs 5 meetings in a day and you post recaps to Slack. Manually, you might spend about 10 minutes per meeting to open MeetGeek, skim, pull action items, then format a message, which is close to an hour daily. With this workflow, you spend maybe 5 minutes upfront getting the schedule and Slack channel right, then it runs on its own. The AI and formatting do the heavy lifting, and Slack gets one clean brief automatically.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- MeetGeek for access to meeting notes via API.
- Slack to deliver summaries and action items to a channel.
- MeetGeek API key (get it from your MeetGeek account settings).
Skill level: Intermediate. You’ll connect credentials, adjust a prompt, and verify a couple of API responses.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A daily schedule kicks things off. The Cron node runs at the time you choose, so you can deliver a morning brief, an end-of-day recap, or both if you duplicate the workflow.
Meetings are pulled and narrowed down. n8n retrieves a catalog of meetings from MeetGeek, splits the list into individual items, and formats the meeting start date so the filter can reliably pick “recent” meetings.
AI turns long notes into decisions and tasks. The workflow fetches each meeting’s summary, then an AI Agent (backed by a chat model) generates a concise brief and clear action items that read like a human wrote them, not like raw transcripts.
Slack receives a message people will actually scan. A Code step builds Slack Block Kit blocks (headings, sections, bullet-like items), then the Slack node posts it to your selected channel.
You can easily modify the filter logic to include only certain meetings, or change the Slack layout to match your team’s preferred recap style. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set the workflow to run on a schedule so it can periodically check for new meeting summaries.
- Add or open Scheduled Automation Start.
- Configure the Rule to your preferred interval (e.g., daily or hourly) to control when the workflow runs.
- Keep Flowpast Branding as a static note for documentation (no configuration required).
Step 2: Connect MeetGeek and prepare meeting records
Pull the meeting catalog, split it into individual records, and prepare identifiers and dates for filtering.
- Open Retrieve Meeting Catalog and set URL to
https://api.meetgeek.ai/v1/meetings/. - Credential Required: Connect your httpBearerAuth credentials in Retrieve Meeting Catalog.
- In Split Meeting Records, set Field to Split Out to
=meetingsso each meeting becomes its own item. - In Map Meeting Identifier, add the assignment extract_meeting_id with value
={{ $json.meeting_id }}, and keep Exclude Fields asmeeting_id. - In Format Start Date, set Date to
={{ $json.timestamp_start_utc }}and Format toyyyy-MM-dd.
⚠️ Common Pitfall: If timestamp_start_utc is missing from the API response, Format Start Date will output invalid dates and Filter Recent Meetings may drop all records.
Step 3: Filter recent meetings and set up AI summarization
Filter meetings from the last 7 days, then use the AI agent and tool to fetch and summarize meeting notes.
- In Filter Recent Meetings, keep the provided JS Code and confirm the instruction
Filter the formatted Date in the past week upto today. - Open Meeting Summary Agent and verify the prompt includes
{{ $json.extract_meeting_id }}and{{ $json.title }}so each summary includes the meeting title. - Ensure Gemini Chat Model is connected as the language model for Meeting Summary Agent.
- Credential Required: Connect your googlePalmApi credentials in Gemini Chat Model.
- Fetch Meeting Summary is an AI tool connected to Meeting Summary Agent—ensure the tool is available to the agent and uses the URL
=https://api.meetgeek.ai/v1/meetings/{{ $json.extract_meeting_id }}/summary/. - Credential Required: Connect your httpBearerAuth credentials for the AI tool used by Meeting Summary Agent (the tool is Fetch Meeting Summary).
Step 4: Build and send the Slack message
Convert AI output to Slack Block Kit format and post the notification to your channel.
- Open Build Slack Blocks and keep the provided JS Code that parses the agent output and constructs a
blocksarray. - In Post Slack Notification, set Message Type to
blockand Blocks UI to={{ '{ "blocks": ' + JSON.stringify($json.blocks) + ' }' }}. - Set Channel to your target Slack channel ID (replace
[YOUR_ID]). - Credential Required: Connect your slackOAuth2Api credentials in Post Slack Notification.
⚠️ Common Pitfall: If you see empty Slack messages, confirm Build Slack Blocks outputs a valid blocks array and that blocksUi uses the exact expression above.
Step 5: Test and Activate Your Workflow
Run a manual test to verify the MeetGeek API, AI summary generation, and Slack delivery.
- Click Execute Workflow from the editor to trigger Scheduled Automation Start manually.
- Confirm that Retrieve Meeting Catalog returns a list of meetings and Split Meeting Records creates individual items.
- Verify Meeting Summary Agent produces a JSON output with
summaryandaction_items. - Check your Slack channel to ensure Post Slack Notification posts a block-formatted message with summaries and action items.
- When satisfied, toggle the workflow Active to enable scheduled production runs.
Troubleshooting Tips
- MeetGeek API credentials can expire or need specific permissions. If things break, check your MeetGeek API key and account access settings 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.
Quick Answers
About 30 minutes if your MeetGeek and Slack access are ready.
No. You will connect accounts and adjust a few fields. The included Code node is already written and usually only needs light edits for formatting.
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 AI model costs for summarization, which are usually only a few cents per day for most teams.
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 probably should. You can change the schedule in “Scheduled Automation Start,” tighten or loosen the criteria in “Filter Recent Meetings,” and adjust the tone in the “Meeting Summary Agent” prompt (for example, “strict bullet points” vs “narrative + bullets”). If you want a different destination, you can also swap “Post Slack Notification” for email or a doc workflow and keep the rest the same.
Usually it’s expired OAuth authorization or the bot isn’t allowed to post in that channel. Reconnect Slack in n8n, then confirm the channel exists and the app has permission to post there. If you recently changed workspace settings, you may need an admin to approve the app again.
If you self-host, there’s no execution limit (it mainly depends on your server and API rate limits). On n8n Cloud, the limit depends on your plan, but most teams can run a daily MeetGeek Slack briefs automation comfortably. Practically, you can usually process dozens of meetings per run as long as your AI and MeetGeek quotas allow it.
Often, yes, because this workflow needs a few “heavier” steps: splitting meeting lists, filtering by dates, generating structured summaries, then formatting Slack Block Kit. n8n handles branching and custom logic without forcing you into expensive task pricing for every little operation, which is honestly where Zapier can get painful. Make can also do it, but you may spend more time building the formatting and edge-case handling. If you already live in Zapier for simple two-step zaps, it can still work, but the output is usually less polished. Talk to an automation expert if you want a quick recommendation based on your meeting volume.
Once this is running, meeting notes stop being a private artifact and start becoming shared clarity. The workflow handles the repetitive recap work so your team can focus on shipping.
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.
