---
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
