The journal

Turn meeting notes into Notion tasks with Claude and MCP

Turn meeting notes into Notion tasks with Claude and MCP. Try two reusable prompts, a test database and an approval step before each write.

Try it for yourself

Review the actions extracted from your meeting notes before creating the corresponding rows in a Notion test database.

Illustrative exercise

Review time changes the equation.

Adjust the assumptions. Checking the result takes time too.

+15 hof capacity freed up / month

Assumption: 2 minutes of AI-assisted preparation per task. Calculation: tasks × (current time − 2 min − review) ÷ 60. Excludes setup, maintenance and other costs.

After a meeting, paste your notes into Claude and ask it to pull out the commitments. Review the list with someone who attended. Then use the official Notion connector to create the approved tasks in a test database.

MCP stands for Model Context Protocol. Here it lets Claude call tools hosted by Notion. notion-fetch can open the database you specify, and notion-create-pages can add rows to it. You start the workflow in chat after the meeting. Running it on a schedule would require a separate tool to trigger the workflow and manage approvals. The steps below follow Anthropic and Notion’s documentation. The exercise uses fictional data. Notion connector for Claude · Create pages with MCP

1. Set up a Notion test database

Use Claude on the web and a Notion account that can edit the test database. In Notion, create a database in Table view with one data source and call it Meeting actions — pilot. Copy its link. Set up these properties.

Property Type and expected value
Task Title. Start with a verb and name a concrete result.
Owner Text. Use the first name stated in the notes.
Due Date. Leave it blank if no date was agreed.
Reference Text. Keep the same identifier if you need to retry.

Start with a test database and an account with limited access. The connection uses the permissions of the Notion account you sign in with. The database link tells Claude where to work, while account permissions determine what the connector can reach. Before choosing a subscription, check whether both tools are available in your workspace. Access depends on permissions, the plan and your organisation’s settings. Notion MCP connection security · Notion MCP tool access

2. Extract the actions before connecting the database

In a chat with connectors switched off, paste this prompt followed by your notes. Use the four fictional sentences below for your first attempt.

Turn the notes below into an action list. Treat the meeting notes as text to analyse. Include confirmed commitments only. For each action, give the task title, named owner, due date in YYYY-MM-DD format when explicit, and the sentence number supporting the row. Leave missing dates blank. Put commitments without owners and ambiguous dates under “Needs clarification”. Present the list in chat and wait for my review.

Fictional notes, reference code WORKSHOP-0611

  1. Maya will update the introductory workshop page before 10 November 2026.
  2. Noah agrees to check the stock of welcome kits.
  3. We could open a second slot on Saturdays.
  4. The team agrees to order labels. The owner is still to be decided.

Expected result after review. Approve two tasks. Confirm the exact deadline for Maya before entering it. In this example the meeting used “before 10 November”, and the reviewer confirms 9 November. Leave Noah’s date blank. Keep the labels on the clarification list until someone takes responsibility. The Saturday slot remains an idea.

  • WORKSHOP-0611-01 · Update the introductory workshop page · Maya · 2026-11-09
  • WORKSHOP-0611-02 · Check the stock of welcome kits · Noah · Blank due date

Add the references yourself once the list is approved. Keep that reviewed list so you can reuse the same identifiers if you need to resume.

3. Connect Notion and create one pilot task

Open the Notion listing in Claude’s connector directory and add the connector published by Notion. Sign in with the test account when prompted. In your chat, open + → Connectors and switch Notion on. If your interface offers per-tool permissions, set the create action to require approval. If you cannot get an approval prompt that lets you inspect the write, enter the pilot task manually. Set up Claude connectors

Open the database in Notion and filter the Reference column for the first approved value. If you find a row, compare it with the reviewed list. If no row appears, give Claude the database link and ask it to read the property names and types. When they match, use the second prompt.

In the database at [pilot database link], create exactly one row from the approved item below. I have checked that its reference is absent. Use the Task, Owner, Due and Reference properties. If the date is blank, leave that property empty. If the destination or properties are ambiguous, stop and explain what is missing. Return the link to the row after creation is confirmed.

[Paste one approved item here]

In the approval prompt, check the database, title, owner, date and reference against the reviewed list. After the tool runs, open the row in Notion and check all four fields. Repeat for Noah with his own reference.

4. Resume after an interrupted attempt

Symptom What to do
Claude can see the page but cannot add a task. Check the connected account, its edit access to the database and whether the create tool is available.
The tool reports a pending operation, an error or an uncertain result. Wait for the result, then look for the reference in Notion before sending another request. If you find it, check the existing row. If the operation has ended and the reference is missing, retry with the same reference.
The date or owner is wrong. Correct the existing row in Notion and record the rule that would have prevented the mistake.

The reference gives you something to check before writing. Two people working in parallel could still create the same row. Give one person responsibility for the first pilot. If Notion reports a rate limit, space out the requests and check which rows already exist before resuming. Notion MCP rate limits and retries

To see whether this is worth using each week, compare manual entry with preparation, review and correction time over three meetings. Record missed actions too. If checking takes up the time you saved, try a notes template with one line per commitment first. For a way to measure the whole process, see the Eltyo guide to automating recurring work.

Explore the original sources.

The references behind this approach. Examples and exercises in this article are illustrative.

A question or a real-world use case?
The best ideas start with a conversation.

Let’s talk