Notion Task Daily Digest

Start the day with a clear, prioritized list of open Notion tasks — without opening Notion to go hunting for it. This workflow reads your tasks database, has the AI assistant turn the raw API response into a readable digest, and notifies your subscribers on whatever channels they have configured.

Use case

You keep a tasks/projects database in Notion. Each morning you want a single digest of everything that is still open (not Done), summarized in plain language, delivered to email/Slack/Discord/Telegram, etc.

What it does each run

1. fetch-due-tasks (notion tool) — calls the Notion query_database operation against your tasks database, filtering out pages whose Status is Done. The connector returns its raw API response in {{fetch-due-tasks.result}} (a JSON string) and the HTTP status in {{fetch-due-tasks.status}}. Those are the only two outputs a connector publishes.
2. summarize (anthropic tool) — feeds {{fetch-due-tasks.result}} to Claude with instructions to parse the Notion results array and emit a short markdown bulleted digest ordered by due date, plus an open-task count. The generated text is published as {{summarize.response}}.
3. notify-digest (message tool) — sends {{summarize.response}} to the workflow's subscribed publishers (default: intouch) on their configured channels.

If the Notion query or the AI step fails, the alertOnError notification fires so you know the digest did not go out.

Required credentials

• Notion API key — create an internal integration at https://www.notion.so/my-integrations, copy its secret, and supply it to the fetch-due-tasks task's apiKey property via an InTouch credential (or a runtime environment variable). The task ships with the placeholder <set via credential> — never hardcode the key. Share your tasks database with the integration (Notion → database → ••• → Connections → add the integration), otherwise the query returns no results.
• Anthropic API key — store an Anthropic credential in InTouch and reference it from the summarize task's credentialName property (placeholder <set via credential>). The credential holds the API key; the password field is the Anthropic key. Swap to a different AI provider tool (e.g. ollama) if you prefer a local model — the flow is the same.

Required runtime environment

• NOTION_TASKS_DB_ID — the ID of your Notion tasks database (the 32-char hash in the database URL). Supply it to the databaseId property; the workflow ships with the placeholder <set via runtime env: NOTION_TASKS_DB_ID>.

Database property expectations

The default filter assumes your tasks database has a Status property of type status with a Done option. Adjust the JSON filter in workflow.yaml if your database uses a different property name or type (e.g. a select or a checkbox done flag, or to add a due-date constraint).

Scheduling

Attach a daily schedule (e.g. a day schedule firing each morning at 7:00) so the digest lands before the workday begins.

Subscribers

By default the digest goes to the intouch user. Change the workflow's subscriptions to route it to a team channel or distribution list.