Free for 30 days on Scale.Start free
Run5 steps45 min setup, ongoing zero touch (transcripts flow in)

Meeting follow-up and action item extraction

A workspace where every meeting becomes a follow-up email or Slack post + a sectioned meeting log in Dock + one Action items row per task. Nothing said in a meeting falls through the cracks.

Open in DockSee every step →

A workspace where every meeting becomes a follow-up email or Slack post + a sectioned meeting log in Dock + one Action items row per task

A workspace where every meeting becomes a follow-up email or Slack post + a sectioned meeting log in Dock + one Action items row per task. Nothing said in a meeting falls through the cracks.

Spin up an agent for the heavy lifting

Scans for new transcripts 3x per weekday, extracts decisions + action items via Claude (owner, due date, priority), sends follow-up email or Slack post to attendees, appends a meeting section to Meetings doc, writes one Action items row per task. Never marks a row as Done; the owner does that.

5 steps, 0 official links, 2 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

4Surfaces
5Steps
2Agent prompts
6Tools mapped
Surfaces
  • tableAction items
  • docSetup guide
  • docMeetings
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/meeting-followup-action-items and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

Does this work without Fireflies?
Yes. Set TRANSCRIPT_DIR to a local folder and drop .txt or .md transcripts in there. The script picks them up on the next scan. Useful for teams that record on Zoom or Otter but don't have a Fireflies account.
What if the transcript doesn't include attendee emails?
Populate participants.json with name-to-email mappings. The keys must match the names exactly as they appear in the transcript. The Meetings doc section shows the extracted names after the first run; copy those strings into participants.json.
Does the agent ever mark action items as done?
No. The owner does that. The agent writes new rows with Status=Open. Owners flip to Done as they complete. This is intentional, owners object to a bot closing things out from under them.
Can I add a Day 14 reminder for overdue action items?
Yes. The Extending section in Setup guide shows the pattern: a second script (overdue_reminder.py) runs daily, reads the Action items table, filters Status=Open + Due Date in the past, sends a Slack DM to each owner with their overdue rows.
What if Claude extracts action items that aren't real commitments?
Edit the extract_meeting_data() prompt to be stricter: 'Extract only explicit action items where someone said I will or NAME will. Do not infer.' Default already biases toward explicit assignments. If you need implicit + explicit, swap the language the other way.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.