---
name: notion-overdue-tasks
description: "Each weekday morning: open tasks in your Notion database whose due date has passed, counted by assignee, with the oldest ones named. Use when the user asks for this, or when it runs on a schedule."
---

# Notion overdue tasks

Each weekday morning: open tasks in your Notion database whose due date has passed, counted by assignee, with the oldest ones named.

A Notion tasks database is easy to fill and easy to ignore. Due dates pass without anyone noticing, because nothing in Notion turns red unless someone built a formula and a filtered view, and the view only helps the people who open it.

The agent runs one filtered query each weekday morning: due date before today, status not done. It posts the overdue count as a tile, broken down by assignee, so a founder or PM can see at a glance whether late work is piling up and on whose plate it sits.

## 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 shared with the tasks database, its token in `NOTION_TOKEN`, or a Notion connector your agent already uses.
- The database ID, the exact names of the Due, Status and Assignee properties, and which status options mean finished.

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

### Steps

1. **Query overdue tasks** (Notion): `POST /v1/data_sources/{data_source_id}/query` (API version `2025-09-03`; `POST /v1/databases/{database_id}/query` on `2022-06-28`) with `{"filter": {"and": [{"property": "Due", "date": {"before": "<today, YYYY-MM-DD>"}}, {"property": "Status", "status": {"does_not_equal": "Done"}}]}, "sorts": [{"property": "Due", "direction": "ascending"}]}`.
2. **Cover every finished state**: If the Status property has several complete options (Done, Won't do, Archived), add one `does_not_equal` per option inside the `and`. The API filters on option names, not on status groups.
3. **Group by assignee**: Count tasks per person from the `Assignee` people property. Tasks with no assignee get their own row; a task with two assignees counts for both.
4. **Measure lateness**: Days late is today minus the `start` of the Due date. Name the five oldest with assignee, due date and the page `url`.
5. **Post the overdue count**: Headline: overdue tasks against yesterday's count. Glance: tasks more than 7 days late, unassigned tasks and how many people have overdue work. Widget: tasks per assignee and the oldest five.

## Route B: the browser

### What you need

- Signed in to Notion as a workspace member with access to the tasks database; filtering and grouping a view needs edit access to the view, or 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 tasks database**: Pick the workspace and open the tasks database as a full page, in a **Table** view.
2. **Filter to overdue, open tasks**: Add two filters: **Due** **Is before** **Today**, and **Status** **Is not** `Done`. Add one more **Is not** filter for every other finished option (Won't do, Archived). Sort by Due, oldest first.
3. **Group by assignee**: Use **Group** by **Assignee** in the view options, which shows a count next to each person's name and an **Empty** group for unassigned tasks. Note the counts; a task with two assignees appears under both.
4. **Measure lateness**: Take the five oldest rows: name, assignee, due date and days late (today minus the due date). Open each and copy its link from the page menu. Count how many rows are more than **7 days** late.
5. **Write the count up**: Total overdue tasks against yesterday's count if you have it, the per-person counts including unassigned, how many are over a week late, and the five oldest with links.

Note: The Group option counts rows, so the per-person counts are visible without opening anything. Relative dates such as Today in a filter follow the time zone of the browser, which can shift a task by a day near midnight.

## The report

- **Overdue tasks** (due before today and not done) and the change since yesterday.
- **By assignee**, including unassigned.
- **The five oldest**, with days late and a link.
- How many are more than a week late.

## 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-overdue-tasks/<date of this run, e.g. 2026-10-16>",
  "item_key": "notion-overdue-tasks",
  "project": "Acme",
  "source": "Notion overdue tasks skill",
  "kind": "metric",
  "title": "23 overdue tasks, 9 of them Theo's",
  "metric": {
    "label": "Overdue tasks",
    "value": 23,
    "better": "lower",
    "period_start": "<start of the period, ISO 8601>",
    "period_end": "<end of the period, ISO 8601>"
  },
  "glance": {
    "type": "Grid",
    "props": {
      "columns": 3
    },
    "children": [
      {
        "type": "Stat",
        "props": {
          "label": "Over 7 days late",
          "value": 8,
          "tone": "warn"
        }
      },
      {
        "type": "Stat",
        "props": {
          "label": "Unassigned",
          "value": 2
        }
      },
      {
        "type": "Stat",
        "props": {
          "label": "People with overdue work",
          "value": 5
        }
      }
    ]
  },
  "widget": [
    {
      "type": "Bars",
      "props": {
        "items": [
          {
            "label": "Theo",
            "value": 9
          },
          {
            "label": "Priya",
            "value": 5
          },
          {
            "label": "Lena",
            "value": 4
          },
          {
            "label": "Jonas",
            "value": 2
          },
          {
            "label": "Sam",
            "value": 1
          },
          {
            "label": "Unassigned",
            "value": 2
          }
        ],
        "unit": "tasks",
        "tone": "warn"
      }
    },
    {
      "type": "Table",
      "props": {
        "columns": [
          "Oldest overdue",
          "Assignee",
          "Due",
          "Late"
        ],
        "align": [
          "left",
          "left",
          "left",
          "right"
        ],
        "rows": [
          [
            "Answer the SOC 2 vendor questionnaire",
            "Theo",
            "Sep 18",
            "28 days"
          ],
          [
            "Update churn survey wording",
            "Priya",
            "Sep 26",
            "20 days"
          ],
          [
            "Clean up unused Stripe products",
            "Unassigned",
            "Sep 30",
            "16 days"
          ],
          [
            "Record onboarding video v2",
            "Lena",
            "Oct 2",
            "14 days"
          ],
          [
            "Review partner contract redlines",
            "Theo",
            "Oct 5",
            "11 days"
          ]
        ]
      }
    },
    {
      "type": "Callout",
      "props": {
        "text": "Two overdue tasks have no assignee, and one of them is 16 days late.",
        "tone": "warn"
      }
    }
  ],
  "size": "md"
}
JSON
```

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

Set `period_start` and `period_end` to the window the number covers: the tile names it from them ("Last 7 days", "Today", "This month"). For a count right now (open items, a balance), send `"period_label": ""` so no period shows; for another name, send it as `period_label` (at most 24 characters).

## Run it on a schedule

Suggested: Weekdays at 8:30 (`30 8 * * 1-5`). From cron, with the agent signed in on that machine:

```bash
30 8 * * 1-5 claude -p "Run the notion-overdue-tasks 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-overdue-tasks#schedule

Source: https://briefkin.dev/skills/notion-overdue-tasks
