Your Meeting Notes Should Run Themselves

Picture the last meeting you got out of.

It went well. Decisions got made. 3 people committed to things. You took notes, real ones, the kind your old boss would have been proud of.

You close the laptop, take a breath, and feel that brief flash of "good meeting."

Then the 45 minutes start.

Turn the notes into tasks. Assign each one to someone. Write the recap email. Update the project in Asana, Notion, or whatever you are using this quarter.

Follow up with the one person who asked you a side question. Send the calendar invite for the follow-up that got committed to in minute 47.

By the time all that is done, the next meeting starts. And you have not actually moved anything forward. You have just transcribed.

That part should not exist.

The notes are not the problem. The translation is.

Good notes are not hard to take. AI takes them better than you do, actually. Granola, Fathom, Read.ai, Otter, take your pick. All 4 have been good enough to replace human notetaking for at least a year now.

The reason you are still doing the 45-minute slog is not the capture. It is everything that has to happen AFTER the capture.

The notes have to become tasks. The tasks have to find the right people. The recap email has to sound like you wrote it, not like a robot did. The project tracker has to get updated. The follow-up has to get scheduled.

That whole chain is what should run by itself. Not the notes. The translation.

What the workflow actually does.

You hop off a call. 4 minutes later, here is what is sitting in front of you without you doing anything.

A clean recap email draft. Subject line, attendees, key decisions, action items by owner, next meeting if there is one. Drafted in your tone, ready to send or edit. Addressed to the right people based on who was in the meeting.

Tasks created. Anything that sounded like "I will do X" or "Brittany is going to send Y" is now a task in your project management tool, assigned to the right person, with the meeting link attached for context.

A project update. If the meeting was about a project, the project status got a one-paragraph update with what was decided and what is next.

A follow-up question batch. The 2 or 3 things you said "let me check on that and get back to you" about are now sitting as personal tasks for you with the question and the asker attached.

You did not log into anything. You closed your laptop after the call and walked to grab water.

How to actually build this in Claude.

You do not need Zapier. You do not need Make. You do not need a 17-step automation chain held together with duct tape.

Claude already has built-in connectors for Granola, Asana, Notion, Linear, Gmail, Google Calendar, HubSpot, and most of what you use.

Flip Claude over to Cowork mode (it lives in the desktop app), connect the tools, and Claude can pull the transcript and write to your project tool and draft the email in one move.

Here is the setup.

1. Use whatever meeting capture tool you already like. Granola has the cleanest integration if you are starting from scratch, but Otter, Fathom, and Read.ai all work.

2. Open Claude in the desktop app and switch on Cowork mode. (Settings, Cowork, on.)

3. Save the prompt below as a Claude project so you can fire it post-meeting in 1 click, or set it as a scheduled task that checks for new transcripts every hour.

4. The first time you run the prompt, Claude will ask permission to connect to your meeting tool, your project tool, and your email. If any of them are not connected yet, Claude will walk you through the 2-click OAuth flow right there. Save first. Let it tell you what is missing.

5. After your next meeting, run the prompt. Read what Claude proposes. Approve. Tweak the prompt for next time.

That is the whole build. No Zapier subscription. No connector hunting. No glue code.

Copy this. Paste it into a Claude project or scheduled task. Adjust the tool names to match your stack.

Process my most recent Granola meeting (or the meeting transcript I paste below if none in Granola).

Pull the transcript and produce 4 things.

**1. A recap email draft.** Subject line includes the meeting title and date. Body has: attendees, 2 to 4 key decisions, action items grouped by owner with deadlines if stated, and the next meeting if one was scheduled. Match my tone (warm, direct, no corporate sludge). Show me the draft in chat. Do not send.

**2. Tasks in Asana.** For every action item I committed to, create a task in my Asana inbox with the meeting title in the description and the deadline if stated. For action items assigned to other people who are in my Asana workspace, create tasks assigned to them in the relevant project. Show me what you are about to create before you create it.

**3. A project update.** If the meeting was tied to an active Asana project, add a one-paragraph status update with what was decided and what is next.

**4. My follow-up list.** Anything I said "let me check on that" or "I will get back to you" about becomes a personal task in my Asana inbox with the question and the person who asked.

Show me everything in one summary. Wait for my approval before sending the email or creating tasks.

That is the version I sent a client last month who was losing 30 to 45 minutes after every meeting to admin. Now he reviews the summary, hits approve, and the next thing on his calendar starts on time.

If writing your own prompt feels like too much.

Open Claude in Cowork mode, hit Schedule, then New Task with Claude. Claude will walk you through it.

First, it asks what kind of task this is. The options are: a recurring deliverable, a watch and alert, or a reminder.

Then it walks you through how often you want it to run, which tools to pull from, and what kind of update you actually want.

You can use the guided flow to set this workflow up as a recurring deliverable that checks for new transcripts every hour, or as a watcher that triggers when a new Granola recording lands. Either works.

What to tune.

Either path gets you 80 percent of the way. The other 20 percent is the part that makes it yours.

Your tone. The first 2 or 3 recap emails will sound a little generic. Paste 2 examples of recaps you have actually sent in the past and tell Claude to match that tone going forward. The drafts will land much closer after that.

Your project structure. If your action items always belong in a specific project or section, tell the prompt that. Otherwise Claude will pick the most relevant project and you will have to move them.

Your approval threshold. If you trust the output, you can drop the "wait for my approval" line and let Claude send the email and create the tasks automatically. I would not do that for the first 2 weeks. After that, your call.

Your meeting types. Sales calls, internal team meetings, and client check-ins each want a slightly different recap style. You can either fork the prompt into 3 versions or add a one-line "what kind of meeting is this" instruction at the top.

You will spend 1 to 2 weeks tweaking. After that, the 45 minutes goes away.

If you want help dialing it in.

This is exactly the kind of thing I do inside an AI Power Hour. 60 minutes together, I pick the 3 AI workflows that will save you the most time (meeting-to-tasks is almost always in the top 3), and you walk away with the prompts, the connector setup, and a written build plan, plus 30 days of email support while you actually do it. $197.

If you would rather hand it off entirely, the AI Setup Sprint is the 2-week done-for-you version, $3,500 for 3 to 5 working workflows.

Book your AI Power Hour →

Or wait for next Monday. Week 4 is the one about 5 AI features hiding inside tools you already pay for, that you have not opened in 9 months. That one is going to make you feel both seen and slightly annoyed.