Agent setup guide
Overdue Task Chaser for Microsoft Teams
Each weekday morning, finds overdue and at-risk Notion tasks and posts a per-owner nudge list in a Microsoft Teams channel.
What it does
Each weekday morning, finds overdue and at-risk Notion tasks and posts a per-owner nudge list in a Microsoft Teams channel.
- Every weekday morning, reads up to 50 open tasks from your Notion tasks database that are overdue or due within the week.
- Keeps the overdue ones and those due in the next 2 days, worked out in code in your time zone (never by the AI); the rest never reach the AI.
- AI 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 to your Microsoft Teams channel and each person's list as a reply under it (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 Microsoft Teams, connected in Settings → Integrations. Microsoft Teams is waiting for Microsoft's approval, so this agent switches on once it's live.
- 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 posts to one channel as the connected user; it doesn't DM or @mention people (Teams has no find-user-and-DM action here).
- It doesn't change tasks, reassign them or move due dates.
- It reads at most 50 open tasks per run (oldest due date first), from Notion only.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
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 Microsoft Teams.
- Nothing to send: the agent runs on a schedule.
- About 10 minutes.
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.
2. Connect Notion
Connect Notion (Settings → Integrations → Notion) and share your tasks database with it.
3. Connect Microsoft Teams
Connect the Microsoft 365 account that should post the messages (Settings → Integrations → Microsoft Teams).
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).
| Setting | What to enter | In step |
|---|---|---|
| Notion account | The Notion workspace with your tasks database. Pick your connected Notion account. | “Read open tasks from Notion” |
| Tasks database | Pick your Notion tasks database (share it with Fluxo Flow first). It needs a “Due” date and a “Status” (Status type) property. | “Read open tasks from Notion” |
5. Pick the Teams channel
Open “Post the summary in Teams” and pick your account, team and channel, then pick the same three in “Reply with their list”.
| Setting | What to enter | In step |
|---|---|---|
| Microsoft Teams account (summary) | The Microsoft 365 account that posts the messages (they appear as that person). Pick your connected Microsoft Teams account. | “Post the summary in Teams” |
| Team (summary) | The team whose channel gets the messages. | “Post the summary in Teams” |
| Channel (summary) | The channel your team reads, e.g. General or Ops. | “Post the summary in Teams” |
| Microsoft Teams account (owner lists) | The Microsoft 365 account that posts the messages (they appear as that person). Pick your connected Microsoft Teams account. | “Reply with their list” |
| Team (owner lists) | The team whose channel gets the messages. | “Reply with their list” |
| Channel (owner lists) | The channel your team reads, e.g. General or Ops. | “Reply with their list” |
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.
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 due date in your time zone and keeps the overdue ones (due before today) and those due today or in the next 2 days; tasks due later or without a due date are left out. Change the tiers here (buckets).
- Anything to chase? — Decision: picks the branch to follow. On days when nothing is overdue or due soon, nothing is posted.
- Sort by owner — AI step (runs on your AI provider key). Branch: Chase. AI groups the tasks the date check kept by owner and writes a short list for each person; how late or how soon each task is was worked out in code.
- Post the summary in Teams — Microsoft Teams: Send a channel message. Posts one summary line (how many tasks are overdue or due soon, counted in code) to your team's 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 — Microsoft Teams: Reply to a channel message. Branch: Each owner. Replies under the summary 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 (checked in code): nothing is posted and no AI is used.
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.
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”.
Can it message each person directly?
No. It posts in one channel as the connected user; Teams has no find-a-user-and-DM action here, so lists use the names from Notion.
How is “overdue” worked out?
In code, not by the AI: “Check the due dates” compares each task's Due date with today in your trigger's time zone. Overdue = due before today; at risk = due today or in the next 2 days. Change the tiers in that step.
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.
- 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.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .