5 projects changed status this week, 2 overdue
5 status changes, 2 projects past their due date and 4 due in the next two weeks. Mobile onboarding moved to Blocked.
Every Friday: which Notion projects changed status this week, who owns them, what is due in the next two weeks and what is overdue.
Reads
You get
The card on the right is a sample. Yours shows your own numbers and updates in place every run.
What lands on your board
5 status changes, 2 projects past their due date and 4 due in the next two weeks. Mobile onboarding moved to Blocked.
Plenty of teams that run projects in Notion have a status meeting whose first fifteen minutes are someone reading the database out loud. Status changed, owner changed, due date moved: it is all in the table, just not in a form anyone reads on a phone.
On Fridays the agent turns the projects database into a digest. It queries the projects edited this week, compares each status with last Friday's snapshot, and lists what moved, what is due in the next two weeks and what is already late. Stakeholders read the digest instead of opening the board.
POST /v1/data_sources/{data_source_id}/query with the Notion-Version: 2025-09-03 header and {"filter": {"timestamp": "last_edited_time", "last_edited_time": {"past_week": {}}}}, paging with start_cursor while has_more is true. The data source ID comes from GET /v1/databases/{database_id}; on API version 2022-06-28, POST /v1/databases/{database_id}/query still works while the database has one data source.
A second query with {"and": [{"property": "Due", "date": {"on_or_before": "<today + 14 days>"}}, {"property": "Status", "status": {"does_not_equal": "Done"}}]} returns both overdue projects and those due soon. Use select in place of status if your Status column is a select.
The API returns only current values, so save {page_id: {status, owner, due}} to a JSON file each run and diff it against last week's file. On the first run, report current status only.
Take the name from the title property, owners from the people property, and the page url for the link. Skip archived pages.
Status changes first (old and new status, owner), then overdue projects, then those due in the next 14 days, soonest first. Link every project name to its page.
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.
Pick your agent, where the data comes from and how to schedule it; the commands below follow.
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-weekly-project-digest/install | shAsk Claude Code:
promptRun the notion-weekly-project-digest skillOr paste the prompt instead of installing:
promptRead my Notion projects database [database ID] with the Notion API. List the projects whose status changed since last week (compare with what you saved last time; if you have nothing saved, just report current status), with owner and old and new status. Then list open projects past their due date, and projects due in the next 14 days, soonest first. Link each project to its Notion page. Save the current status, owner and due date of every project for next week's comparison.Fridays at 12:00, from cron on any machine where Claude Code is signed in:
crontab0 12 * * 5 claude -p "Run the notion-weekly-project-digest 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.
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
SKILL.md---
name: notion-weekly-project-digest
description: "Every Friday: which Notion projects changed status this week, who owns them, what is due in the next two weeks and what is overdue. Use when the user asks for this, or when it runs on a schedule."
---
# Notion weekly project digest
Every Friday: which Notion projects changed status this week, who owns them, what is due in the next two weeks and what is overdue.
Plenty of teams that run projects in Notion have a status meeting whose first fifteen minutes are someone reading the database out loud. Status changed, owner changed, due date moved: it is all in the table, just not in a form anyone reads on a phone.
On Fridays the agent turns the projects database into a digest. It queries the projects edited this week, compares each status with last Friday's snapshot, and lists what moved, what is due in the next two weeks and what is already late. Stakeholders read the digest instead of opening the board.
## 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 read content access, shared with the projects database, its token in `NOTION_TOKEN`; or a Notion MCP server or connector.
- The database ID and the names of its Status, Owner and Due properties.
If something is missing, say what and stop; do not invent numbers.
### Steps
1. **Query the projects edited this week** (Notion): `POST /v1/data_sources/{data_source_id}/query` with the `Notion-Version: 2025-09-03` header and `{"filter": {"timestamp": "last_edited_time", "last_edited_time": {"past_week": {}}}}`, paging with `start_cursor` while `has_more` is true. The data source ID comes from `GET /v1/databases/{database_id}`; on API version `2022-06-28`, `POST /v1/databases/{database_id}/query` still works while the database has one data source.
2. **Pull what is due and late** (Notion): A second query with `{"and": [{"property": "Due", "date": {"on_or_before": "<today + 14 days>"}}, {"property": "Status", "status": {"does_not_equal": "Done"}}]}` returns both overdue projects and those due soon. Use `select` in place of `status` if your Status column is a select.
3. **Compare with last Friday**: The API returns only current values, so save `{page_id: {status, owner, due}}` to a JSON file each run and diff it against last week's file. On the first run, report current status only.
4. **Read the details**: Take the name from the `title` property, owners from the `people` property, and the page `url` for the link. Skip archived pages.
5. **Write the digest**: Status changes first (old and new status, owner), then overdue projects, then those due in the next 14 days, soonest first. Link every project name to its page.
## Route B: the browser
### What you need
- Signed in to Notion as a workspace member who can view the projects database; adding filters to a view needs edit access, or use a personal view.
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. **Open the projects database**: Pick the workspace and open the projects database as a full page (not an inline view inside another page).
2. **Filter to this week's edits**: Add a filter on **Last edited time** with **Is within** the **past week**. Read each project's name, Status, Owner and Due. Compare the status with the list from last Friday that you kept; on the first run, report current status only.
3. **Pull what is due and late**: Change the filter to **Due** **Is on or before** the date 14 days from today, and **Status** **Is not** Done. Sort by Due ascending. Everything before today is overdue; the rest is due soon.
4. **Copy the links**: Open each project page and use **Copy link** from the page menu, or read the URL, so every name in the digest links to its page. Skip pages in Trash.
5. **Write the digest**: Status changes first, with owner and old and new status, then overdue projects, then those due in the next 14 days, soonest first.
Note: Notion keeps page history, but only per page, so status changes are only visible by comparing with a saved list. Database views load 50 rows at a time; scroll to the end or use Export (CSV) from the view menu for a large database.
## The report
- **Status changes** this week, with owner and the old and new status.
- **Overdue**: open projects past their due date.
- **Due in the next 14 days**, soonest first.
- A link to each project page.
## 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-weekly-project-digest/<date of this run, e.g. 2026-10-16>",
"item_key": "notion-weekly-project-digest",
"project": "Acme",
"source": "Notion weekly project digest skill",
"kind": "update",
"title": "5 projects changed status this week, 2 overdue",
"summary": "**5** status changes, **2** projects past their due date and **4** due in the next two weeks. Mobile onboarding moved to Blocked.",
"widget": [
{
"type": "Table",
"props": {
"columns": [
"Project",
"Owner",
"Status change",
"Due"
],
"rows": [
[
"Billing page redesign",
"Lena",
"In progress → In review",
"Oct 23"
],
[
"Mobile onboarding",
"Theo",
"In progress → Blocked",
"Oct 30"
],
[
"SSO for the teams plan",
"Jonas",
"Planned → In progress",
"Nov 20"
],
[
"Help center migration",
"Aisha",
"In review → Done",
"Oct 15"
],
[
"Q4 pricing test",
"Priya",
"Planned → In progress",
"Nov 6"
]
]
}
},
{
"type": "Table",
"props": {
"columns": [
"Overdue",
"Owner",
"Was due",
"Status"
],
"rows": [
[
"Usage-based invoices",
"Marco",
"Oct 9",
"In progress"
],
[
"Partner API docs",
"Dana",
"Oct 13",
"In review"
]
]
}
},
{
"type": "KeyValue",
"props": {
"items": [
{
"key": "Search filters v2",
"value": "Due Oct 21, Sam"
},
{
"key": "Billing page redesign",
"value": "Due Oct 23, Lena"
},
{
"key": "Admin audit log",
"value": "Due Oct 27, Jonas"
},
{
"key": "Mobile onboarding",
"value": "Due Oct 30, Theo (blocked)"
}
]
}
}
]
}
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 12:00 (`0 12 * * 5`). From cron, with the agent signed in on that machine:
```bash
0 12 * * 5 claude -p "Run the notion-weekly-project-digest 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-weekly-project-digest#schedule
Source: https://briefkin.dev/skills/notion-weekly-project-digest
A Notion integration with read content access, shared with the projects database, its token in NOTION_TOKEN; or a Notion MCP server or connector.
The database ID and the names of its Status, Owner and Due properties.
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.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.
Notion's API returns a page's current properties but not their history. The skill saves each project's status every Friday and compares; the last_edited_time filter only narrows down which pages to look at.
Not until someone adds a second data source to the database. From API version 2025-09-03 a database can hold several data sources and queries go to POST /v1/data_sources/{data_source_id}/query; older versions keep working against single-source databases, with the same filters. Moving over is a header change and one GET /v1/databases/{database_id} call for the data source ID.
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.
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.
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.
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.