Overdue Task Chaser

What it does

Each weekday morning, posts who has overdue or at-risk tasks in your Notion tasks database to Slack.

• Every weekday morning, reads up to 50 open tasks from your Notion tasks database that are overdue or due within the week.
• Dates are worked out in code, never by the AI: days until or since each date, the window and business days are computed in your workflow's time zone, and records outside the window are skipped before the AI sees them.
• Only the overdue tasks and those due in the next 2 days reach the AI, which groups them by owner and writes a short list per person: task, how late or how soon, status and Notion link. Tasks without an owner are listed as Unassigned.
• Posts one summary line (with the count from code) to your Slack channel and each person's list as a reply in its thread (one reply per owner, up to 30).
• Posts nothing on days when everything is on track.

What it needs

• A paid plan (agents run live on paid plans).
• An AI provider key (Settings → AI Providers).
• Notion and Slack, connected in Settings → Integrations.
• A Notion tasks database with a “Due” date, a “Status” (Status type, finished = Done) and a people property for owners.

What it doesn't do

• It works with Notion only (not Asana, ClickUp, monday.com or Trello).
• It doesn't change tasks, reassign them or move due dates.
• It doesn't @-mention or DM people; lists use the names from Notion.
• It reads at most 50 open tasks per run (oldest due date first).

Availability and plans

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

• A paid plan: agents run live, and the Free plan only runs Dry Runs.
• An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
• These apps, connected in Settings → Integrations: Notion and Slack.
• Nothing to send: the agent runs on a schedule.
• About 10 minutes.

• Bring your own AI key
• Notion (live)
• Slack (live)

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

• Connect your AI provider

2. Connect Notion

Connect Notion (Settings → Integrations → Notion) and share your tasks database with it.

• Connecting Notion

3. Connect Slack

Connect your Slack workspace (Settings → Integrations → Slack).

• Connecting Slack

4. Pick your tasks database

Open “Read open tasks from Notion” and pick your account and tasks database (it needs a “Due” date and a “Status” property).

5. Pick the Slack channel

Open “Post the summary in Slack” and pick your account and channel, then pick the account in “Reply with their list”. Invite the app to private channels first (/invite @Fluxo Flow).

6. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

• Dry Run vs Run

7. Switch the trigger on

Open the trigger, check the time (8:00, Monday to Friday) and set your time zone, then switch the schedule on.

How it works

The agent is a normal workflow with 10 steps (1 AI step). You can open, edit and monitor it like any other workflow.

• Every weekday morning — Runs on a schedule (cron 0 8 * * 1-5, UTC — change it in the trigger's settings). Runs Monday to Friday at 8:00 (set your time zone on the trigger).
• Read open tasks from Notion — Notion: Query a database. Reads up to 50 tasks from your Notion tasks database that aren't Done and are overdue or due within the next week, oldest due date first.
• Check the due dates — Step. In code, not AI: works out each task's days overdue or days left in your time zone and keeps only tasks that are overdue or due in the next 2 days (today, tomorrow or the day after). Change the 2 days here (the at_risk bucket's min).
• Anything to chase? — Decision: picks the branch to follow. On days when nothing is overdue or due soon (checked in code), nothing is posted.
• Sort by owner — AI step (runs on your AI provider key). Branch: Chase. Which tasks are overdue or at risk was worked out in code. AI groups them by owner and writes a short nudge list for each person.
• Post the summary in Slack — Slack: Post a message. Posts one summary line (today's date and how many tasks are overdue or due soon, counted in code) to your team channel.
• Each owner — Repeats the steps below for each item (up to 30 per run). Repeats the next step once per owner (up to 30).
• [For each item — “Each owner”] Reply with their list — Slack: Reply in a thread. Branch: Each owner. Replies in the summary's thread with that person's overdue and due-soon tasks, each with its Notion link.
• Posted — Kept in the run history. Branch: Done. The run history keeps how many owner lists were posted.
• All on track — Kept in the run history. Branch: All on track. Nothing overdue or due soon: nothing is posted.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live.

• Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
• For-each loops repeat only the first 3 items.

Go live

• Open the trigger, check the time (8:00, Monday to Friday) and set your time zone, then switch the schedule on.
• Scheduled runs start only once the schedule is activated, and can't repeat faster than your plan's minimum interval.
• The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
• When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

• Scheduled triggers
• Switching a trigger on (Activation)

Questions

What does my Notion database need?

A date property called “Due” and a Status property (Notion's Status type) whose finished value is “Done”, plus a people property for the owner (e.g. “Assignee”). If yours use other names, edit the filter in “Read open tasks from Notion”.

How does it decide what's overdue or due soon?

In code, not by the AI: “Check the due dates” counts each task's days overdue or days left in your trigger's time zone, and only overdue tasks and those due today, tomorrow or the day after reach the AI. To change the 2-day window, edit the at_risk bucket in that step.

Does it @-mention people?

No. It uses the names from Notion. Slack mentions would need each person's Slack account matched to their Notion user.

Asana, ClickUp, monday.com or Trello?

Not yet: this version reads Notion only.

Troubleshooting

• “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
• A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
• An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
• Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
• It didn't run at the expected time: the schedule must be activated, and its time is in the trigger's timezone.
• A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

• Debugging failed runs
• Error messages
• Get help