---
ref: workflow:meeting-notes-and-action-items
title: Turn recent meetings into notes and tracked action items
author: Shahzaib0217
tools: [tool:bridge/search-meetings, tool:bridge/get-meeting-details, tool:bridge/create-action-item, tool:notion/create-page]
tags: [capability:manage-docs, capability:manage-tasks, capability:review-recordings, has:mcp, motion:retention]
updated: 2026-10-28
---

# Turn recent meetings into notes and tracked action items

Writes notes for each new meeting, adds missed action items in Bridge, and saves the notes to Notion.

Set up the tools below, then run the steps in order for the user, carrying each step's results into the next. The run is done when the user has the outcome below.

## Outcome

- Notes for every meeting since the last run: summary, decisions, key takeaways and action items with owners.
- Any action item said in the meeting but missing from Bridge, added to that meeting once you approve it.
- One Notion page per meeting with its notes.

## Inputs

Ask the user for these before you start.

- `since`: when the last run happened, so only newer meetings are read, e.g. 2026-10-16
- `participant`: optionally, only meetings with this person or company, e.g. acme.com
- `notes_parent`: the Notion page or database the notes go in, e.g. Meeting notes

## Set up

### Bridge (tool:bridge/search-meetings, tool:bridge/get-meeting-details, tool:bridge/create-action-item)

Use the MCP server. Add it to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "bridge": { "url": "https://api.meetonbridge.com/mcp" } } }
```

- Search meetings: call the MCP tool `search_meetings`
- Get meeting details: call the MCP tool `get_meeting_details`
- Create an action item: call the MCP tool `create_action_item`

Note: Needs a paid Bridge plan (Professional or above); not on the free Starter plan or a trial. At sign-in the user grants read, or read and write, access. Call get_bridge_context first for the tools the plan and connection allow.

Notes:

- Search meetings: Omit `query` to browse by date or participant. Pass a returned `recapId` to `get_meeting_details` for the full meeting.
- Create an action item: Needs edit access to the meeting. Takes the meeting's `recapId` from `search_meetings` as `recap_id`.

### Create a page (Notion, tool:notion/create-page)

Use the first option your agent supports.

Note: To add a row to a database, set the parent to its data source and match that data source's property schema.

#### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "notion": { "url": "https://mcp.notion.com/mcp" } } }
```

Call the MCP tool `notion-create-pages`.

#### CLI (official)

Install the command, then confirm it runs.

```sh
npm install --global ntn
ntn --version
```

Run `ntn api v1/pages`.

Set `$NOTION_API_TOKEN` in your environment first (get a key: https://www.notion.so/developers/tokens).

Before step 1, confirm access to each service with its cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Steps

1. **List the meetings** with Search meetings (Bridge). Browse meetings from `since` to now, without a query, filtered on `participant` when given. Keep each `recapId`, title and date.
2. **Read each meeting** with Get meeting details (Bridge). For each `recapId`, keep the summary, takeaways, topics, action items and transcript. Skip meetings with no transcript, such as booked calls that never took place.
3. **Write the notes** yourself. For each meeting, write a summary, the decisions made, three to five takeaways and every commitment heard in the transcript, with its owner and due date when said. Compare the commitments with the meeting's action items from step 2, and show the user the ones Bridge did not capture.
4. **Add what is missing** with Create an action item (Bridge). Add each approved commitment to its meeting by `recapId`, with its owner.
5. **Save the notes** with Create a page (Notion). Create one page per meeting under `notes_parent`, titled with the meeting title and date.

## Notes

Run it daily or weekly with `since` set to the previous run. Any docs tool can stand in for Notion in step 5, or skip it and keep the notes in Bridge.

## Rules

- Use only the services set up above. The read-only calls they need, like listing ids or polling for results, are fine.
- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.