Collect the action items from this week's Notion meeting notes

Friday afternoon: every unchecked to-do from this week's meeting notes in Notion, grouped by owner, with a link back to the meeting.

Runs
Fridays at 16:30
Uses
Notion
Posts
Report card

From your apps to your board

How the skill works: your agent reads this week's meetings from Notion; notion database id from What you tell it, fridays at 16:30, and gives you report card and the report in the chat.

Reads

  • NotionThis week's meetings
  • What you tell itNotion database ID
reads
Your agentClaude Code, Codex, Cursor or GeminiFridays at 16:30
posts

You get

  • Report cardOn your board, updated in place every run
  • The report in the chatEvery run, with or without Briefkin

What you get

  • Open action items from the week's meetings, grouped by owner.
  • Each item with the meeting it came from, linked.
  • No owner: items nobody was named on.
  • Counts by person, so an overloaded owner stands out.

The card on the right is a sample. Yours shows your own numbers and updates in place every run.

What lands on your board

AcmeNotion meeting action items · Claude Code

17 open action items from 6 meetings

17 unchecked to-dos across 6 meetings this week. 3 have no owner, including the Contoso follow-up from the pricing review.

Priya5 items
Lena4 items
Marco3 items
Jonas2 items
No owner3 items
OwnerAction itemMeeting
PriyaSend the revised Q4 pricing deck to salesPricing review, Oct 13
PriyaBook usability sessions for the export flowDesign review, Oct 14
LenaShare mobile onboarding metricsWeekly product sync, Oct 12
LenaDraft release notes for 4.2Release planning, Oct 15
MarcoConfirm SSO pricing with financePricing review, Oct 13
MarcoSend the advisory board the roadmap draftCustomer advisory call, Oct 16
JonasWrite the follow-up for the Oct 11 outageIncident review, Oct 14
No ownerFollow up with Contoso on the annual planPricing review, Oct 13
No ownerDecide the beta waitlist cutoffWeekly product sync, Oct 12
Done
An example with made-up numbers. Your agent posts your real ones.

What it does

Meeting notes in Notion are good at capturing action items and bad at bringing them back. A to-do written in Tuesday's design review lives on that page, and the person it belongs to has to remember which of six meetings it came from.

This skill reads every meeting notes page from the past week, collects the unchecked to-dos, works out the owner from the @mention in each one, and posts the list grouped by person with a link to the meeting. Items with no owner are listed separately, since those are the ones that quietly never happen.

How it works

  1. 1Find this week's meetings

    POST /v1/data_sources/{data_source_id}/query on the meeting notes database (API version 2025-09-03; the databases query endpoint on 2022-06-28) with {"filter": {"property": "Date", "date": {"past_week": {}}}}, or a created_time timestamp filter if the pages have no date property.

  2. 2Read each page's blocks

    GET /v1/blocks/{page_id}/children?page_size=100, following next_cursor, and recurse into any block with has_children: true, because action items often sit under a toggle or a heading.

  3. 3

    3Pick out the action items

    Keep to_do blocks where to_do.checked is false. For notes written without checkboxes, also keep bullets under a heading called Action items or Next steps.

  4. 4Work out the owner

    The owner is the first user mention in the item's rich_text (type: "mention" with mention.type: "user"). A plain name such as "Lena to send" counts if it matches a member from GET /v1/users; anything else is unowned.

  5. 5

    5Write the list

    Group by owner, oldest meeting first, each item with the meeting title and date linked to its page. Put the unowned items last, under their own heading.

  6. Post it to the board

    With BRIEFKIN_TOKEN set, the agent sends the result as one card that updates in place every run. Without it, you get the report in the chat.

Install and run it

Pick your agent, where the data comes from and how to schedule it; the commands below follow.

Agent
Data
Schedule
  1. Install the skill

    One command. It puts the SKILL.md in ~/.claude/skills and in ~/.agents/skills, which Codex, Cursor, Gemini CLI, Copilot CLI and OpenCode read too.

    shellcurl -fsSL https://briefkin.dev/skills/notion-meeting-action-items/install | sh
  2. Run it

    Ask Claude Code:

    promptRun the notion-meeting-action-items skill

    Or paste the prompt instead of installing:

    promptUsing the Notion API, find the pages in my meeting notes database [database ID] dated in the past week. Read each page's blocks, including nested ones, and collect the unchecked to-do items, plus bullets under an Action items or Next steps heading. For each item, work out the owner from the first @mention, or from a name that matches a workspace member. Group the items by owner with the meeting title, date and page link, and list items with no owner separately. Start with the total count and the number of meetings.
  3. Put it on a schedule

    Fridays at 16:30, from cron on any machine where Claude Code is signed in:

    crontab30 16 * * 5 claude -p "Run the notion-meeting-action-items skill"

    Add it with crontab -e. A laptop asleep at that time runs it when it wakes if you use launchd or Task Scheduler instead; GitHub Actions works for the API route.

  4. Send it to your board

    Connect Briefkin once with curl -fsSL https://briefkin.dev/install | sh and every run lands on your board as a report card. How setup works

View the SKILL.mdRaw file
SKILL.md---
name: notion-meeting-action-items
description: "Friday afternoon: every unchecked to-do from this week's meeting notes in Notion, grouped by owner, with a link back to the meeting. Use when the user asks for this, or when it runs on a schedule."
---

# Notion meeting action items

Friday afternoon: every unchecked to-do from this week's meeting notes in Notion, grouped by owner, with a link back to the meeting.

Meeting notes in Notion are good at capturing action items and bad at bringing them back. A to-do written in Tuesday's design review lives on that page, and the person it belongs to has to remember which of six meetings it came from.

This skill reads every meeting notes page from the past week, collects the unchecked to-dos, works out the owner from the @mention in each one, and posts the list grouped by person with a link to the meeting. Items with no owner are listed separately, since those are the ones that quietly never happen.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- A Notion integration with the read content and read user information capabilities, shared with the meeting notes database; its token in `NOTION_TOKEN`. A Notion MCP server or connector works too.
- The meeting notes database ID and the name of its date property.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Find this week's meetings** (Notion): `POST /v1/data_sources/{data_source_id}/query` on the meeting notes database (API version `2025-09-03`; the databases query endpoint on `2022-06-28`) with `{"filter": {"property": "Date", "date": {"past_week": {}}}}`, or a `created_time` timestamp filter if the pages have no date property.
2. **Read each page's blocks** (Notion): `GET /v1/blocks/{page_id}/children?page_size=100`, following `next_cursor`, and recurse into any block with `has_children: true`, because action items often sit under a toggle or a heading.
3. **Pick out the action items**: Keep `to_do` blocks where `to_do.checked` is false. For notes written without checkboxes, also keep bullets under a heading called Action items or Next steps.
4. **Work out the owner** (Notion): The owner is the first user mention in the item's `rich_text` (`type: "mention"` with `mention.type: "user"`). A plain name such as "Lena to send" counts if it matches a member from `GET /v1/users`; anything else is unowned.
5. **Write the list**: Group by owner, oldest meeting first, each item with the meeting title and date linked to its page. Put the unowned items last, under their own heading.

## Route B: the browser

### What you need

- Signed in to Notion as a workspace member with access to the meeting notes database and its pages; the member list needs a workspace that lets members see it.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://www.notion.so/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **List this week's meetings**: Open the meeting notes database as a full page and filter **Date** with **Is within** the **past week** (or **Created time** when the pages have no date property). Note each meeting's title, date and link.
2. **Read each page**: Open each meeting page and read it top to bottom, expanding every toggle, since action items often sit under a collapsed heading.
3. **Collect the action items**: Keep unchecked to-do boxes. For notes written without checkboxes, also keep bullets under a heading called Action items or Next steps.
4. **Work out the owner**: The owner is the first @mention in the item; hovering over it shows the person. A plain first name counts when it matches a workspace member (the **Members** list in Settings); anything else is unowned.
5. **Write the list**: Group by owner, oldest meeting first, each item with the meeting title and date linked to its page. Unowned items go last under their own heading, with the counts per person at the top.

Note: Synced blocks and embedded sub-pages do not expand in the page view, so an item inside one is easy to miss. Standalone meeting pages outside the database only turn up through Search, which matches titles loosely.

## The report

- **Open action items** from the week's meetings, grouped by owner.
- **Each item** with the meeting it came from, linked.
- **No owner**: items nobody was named on.
- Counts by person, so an overloaded owner stands out.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "notion-meeting-action-items/<date of this run, e.g. 2026-10-16>",
  "item_key": "notion-meeting-action-items",
  "project": "Acme",
  "source": "Notion meeting action items skill",
  "kind": "update",
  "title": "17 open action items from 6 meetings",
  "summary": "**17** unchecked to-dos across **6** meetings this week. **3** have no owner, including the Contoso follow-up from the pricing review.",
  "widget": [
    {
      "type": "Bars",
      "props": {
        "items": [
          {
            "label": "Priya",
            "value": 5
          },
          {
            "label": "Lena",
            "value": 4
          },
          {
            "label": "Marco",
            "value": 3
          },
          {
            "label": "Jonas",
            "value": 2
          },
          {
            "label": "No owner",
            "value": 3
          }
        ],
        "unit": "items"
      }
    },
    {
      "type": "Table",
      "props": {
        "columns": [
          "Owner",
          "Action item",
          "Meeting"
        ],
        "rows": [
          [
            "Priya",
            "Send the revised Q4 pricing deck to sales",
            "Pricing review, Oct 13"
          ],
          [
            "Priya",
            "Book usability sessions for the export flow",
            "Design review, Oct 14"
          ],
          [
            "Lena",
            "Share mobile onboarding metrics",
            "Weekly product sync, Oct 12"
          ],
          [
            "Lena",
            "Draft release notes for 4.2",
            "Release planning, Oct 15"
          ],
          [
            "Marco",
            "Confirm SSO pricing with finance",
            "Pricing review, Oct 13"
          ],
          [
            "Marco",
            "Send the advisory board the roadmap draft",
            "Customer advisory call, Oct 16"
          ],
          [
            "Jonas",
            "Write the follow-up for the Oct 11 outage",
            "Incident review, Oct 14"
          ],
          [
            "No owner",
            "Follow up with Contoso on the annual plan",
            "Pricing review, Oct 13"
          ],
          [
            "No owner",
            "Decide the beta waitlist cutoff",
            "Weekly product sync, Oct 12"
          ]
        ]
      }
    }
  ]
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Fridays at 16:30 (`30 16 * * 5`). From cron, with the agent signed in on that machine:

```bash
30 16 * * 5 claude -p "Run the notion-meeting-action-items skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/notion-meeting-action-items#schedule

Source: https://briefkin.dev/skills/notion-meeting-action-items

What your agent needs

  • A Notion integration with the read content and read user information capabilities, shared with the meeting notes database; its token in NOTION_TOKEN. A Notion MCP server or connector works too.

  • The meeting notes database ID and the name of its date property.

Connecting Notion

  1. Notion MCP, Notion's hosted server at https://mcp.notion.com/mcp. Add Notion from Claude's connector directory, or run claude mcp add --transport http notion https://mcp.notion.com/mcp, and approve access with OAuth; it sees the pages your Notion account can see.
  2. API with an internal integration. Create an internal integration in Notion's integration settings, store its secret (it starts with ntn_) in NOTION_TOKEN, send Notion-Version: 2025-09-03, and share each page or database with the integration from its ••• menu under Connections.

Give the integration only the Read content capability and share just the databases the report uses; Notion MCP acts as you and can edit, so it fits interactive work better than unattended runs.

Questions

Some of our notes are standalone pages, not in a database. Can it find those?

Use POST /v1/search with {"query": "meeting", "filter": {"property": "object", "value": "page"}} and keep pages whose last_edited_time falls in the past week. A database is more reliable, because search matches titles loosely.

Will it tick items off when they are done?

No. It only reads. People check the to-do in Notion as usual, and the next run leaves checked items out.

Do I need Briefkin to use the Notion meeting action items skill?

No. The skill runs with your own agent and gives you the report in the chat. With a Briefkin token set, each run also posts it to your board as a report card, so you can glance at it instead of asking again.

Which agents can run it?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp all read SKILL.md files. The install command puts it in ~/.claude/skills and ~/.agents/skills, where they look. ChatGPT, the Claude app and Grok take the prompt instead. Pick your agent under "Install and run it" and the commands change to match.

Can it work without an API or MCP server, from my browser?

Yes. Switch the data source to "Your browser" and the steps change to the Notion pages themselves: the agent opens www.notion.so in a browser you are signed in to and reads the numbers off the page. Claude Code, Codex, Cursor, Claude app and ChatGPT can drive a browser out of the box; Gemini CLI, Copilot CLI and OpenCode need a Playwright or Chrome DevTools MCP server first. It is slower than the API and needs you signed in, so it suits a report you run by hand or from a scheduler on your own computer.

Read this report on your board, not in a chat log

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Free during the open beta. No card.