Meetings -> notes -> action

The flagship pipeline

This is the build the whole module points at: a meeting happens, and within minutes the structured note is filed in the client folder, the action items exist as tasks with the right assignees, the CRM has the activity logged, and Slack has a confirmation listing exactly what was done.

• Stage 1 - capture: pull the transcript from your meeting recorder.
• Stage 2 - structure: run meeting-capture (module one) to produce the decisions/actions/risks note, filed with an ISO-dated name.
• Stage 3 - route: create tasks in your project tool, log the activity in the CRM, draft the client follow-up email.
• Stage 4 - confirm: post a summary to Slack ending with a "review this" list, so a human sees every external write the pipeline made.

You already built stage 2. This lesson wires stages 1, 3, and 4 around it. Notice the ladder at work: what you once did by chatting became the meeting-capture skill, and in this lesson the skill becomes a pipeline - module three will hand pipelines like it a schedule.

Transcript sources: Granola and Fireflies

Two recorders have first-party MCP servers worth teaching. Granola's lives at mcp.granola.ai/mcp (browser OAuth) with tools like query_granola_meetings, list_meetings, and get_meeting_transcript - note transcripts and folders need a paid plan; the free tier covers the last 30 days. Fireflies ships an official MCP too, plus a mature GraphQL API and webhooks carrying transcripts, summaries, action items, and speaker data.

Connect one of them now: claude mcp add --transport http granola mcp.granola.ai/mcp, then /mcp to OAuth. Test with "list my meetings from this week" before building anything on top.

Routing to tasks: Linear, Asana, ClickUp

Project tools all run official servers now. Linear is the most polished: mcp.linear.app/mcp, OAuth, scoped to your existing Linear permissions. Asana is at mcp.asana.com/v2/mcp - pin to /v2; the V1 server has been retired, and V2 ships a smaller tool set, so check via /mcp that the tools you need are there. ClickUp runs a public beta at mcp.clickup.com/mcp.

The routing logic is the part you own: assignees come from company/org-chart.md, not from guessing. "Action item mentions billing - org chart says Maria owns billing - task assigned to Maria." When the chart is ambiguous, the skill asks instead of guessing. That one rule prevents most of the cleanup that gives automation a bad name.

Build the meeting-followup skill

1. Create .claude/skills/meeting-followup/SKILL.md. It chains meeting-capture: first produce the filed note, then act on it.
2. Add the routing steps: for each action item, create a task in your project tool with the owner resolved from org-chart.md and a link back to the note file.
3. Add the CRM step: log the meeting as an activity on the right account, with the decisions list as the body.
4. Add the follow-up step: draft (never send) the client recap email from the note, using your tone rules.
5. End with the confirmation: post to your ops channel a list of every task created, the CRM update, and the draft location - phrased as "review this," not "done."
6. Run it end to end on one real meeting. Check each system: are the tasks right, is the CRM activity on the correct account, does the draft read like you?

Do this now

Sources and further reading

• Granola MCP docs
• Linear MCP docs
• Asana MCP server docs
• ClickUp MCP docs