Agent setup guide
Month-End Close Tracker
During close, every weekday: reads your Notion close checklist and posts who's late, what's blocked and what's left to Slack.
What it does
During close, every weekday: reads your Notion close checklist and posts who's late, what's blocked and what's left to Slack.
- Every weekday morning, reads the open items of your month-end close checklist database in Notion (up to 100).
- 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.
- AI lists what's late (and by how many days, counted in code), due today, blocked (and on what) and left per owner, against your close calendar.
- While the close is in progress, posts one status to your Slack close channel, ending with the most urgent item.
- Between closes (nothing late or due soon) it posts nothing.
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 close checklist database with task, owner, due date and status properties, kept up to date by the team.
What it doesn't do
- It tracks your checklist; it doesn't do reconciliations, journal entries or any accounting work (see Bank & Payout Reconciliation for that).
- It doesn't change tasks in Notion or DM people — one channel post per day.
- It never invents tasks, owners or reasons for delays; it reports what the checklist says.
- It reads up to 100 open items per run.
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 Slack.
- Nothing to send: the agent runs on a schedule.
- About 15 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 the Notion workspace with your close checklist (Settings → Integrations → Notion).
3. Connect Slack
Connect the Slack workspace your finance team uses (Settings → Integrations → Slack).
4. Describe your checklist and close calendar
Open “Work out who's late and what's blocked” and replace the placeholder with your property names, done statuses, close window and target close day.
| Setting | What to enter | In step |
|---|---|---|
| Checklist properties and close calendar | Replace the placeholder with your property names (task, owner, due, status, notes/blocker, period), which statuses mean done, when your close window runs (e.g. last business day to business day 5) and your target close day. The late / due-soon tiers are set in “Check the due dates”. It starts as “[DESCRIBE YOUR CLOSE CHECKLIST PROPERTIES, CLOSE CALENDAR AND TARGET CLOSE DAY HERE]” until you replace it. | “Work out who's late and what's blocked” |
5. Pick your close checklist
Open “Read your close checklist”, pick your workspace and database, and enter the filter that keeps only open items.
| Setting | What to enter | In step |
|---|---|---|
| Notion workspace | The Notion workspace your close checklist is in. Pick your connected Notion account. | “Read your close checklist” |
| Close checklist database | The Notion database with one page per close task. Share it with Fluxo Flow first: ••• → Connections. | “Read your close checklist” |
| Filter for open items | Notion's filter that keeps only open tasks, e.g. {"property": "Status", "status": {"does_not_equal": "Done"}} (use "select" for a Select property). | “Read your close checklist” |
6. Pick the Slack account and close channel
Open “Post the close status to Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
| Setting | What to enter | In step |
|---|---|---|
| Slack account | The Slack workspace the close status is posted to. Pick your connected Slack account. | “Post the close status to Slack” |
| Close channel | The channel your finance team follows during close, e.g. #month-end-close. | “Post the close status to Slack” |
7. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
8. Switch the trigger on
Open the trigger, set your time zone (days late are counted in it) and switch the schedule on. It checks every weekday at 9:00 and posts only during close.
How it works
The agent is a normal workflow with 9 steps (1 AI step). You can open, edit and monitor it like any other workflow.
- Weekdays at 9:00 — Runs on a schedule (cron 0 9 * * 1-5, UTC — change it in the trigger's settings). Runs every weekday morning; it only posts while your close is in progress (open items due soon or late). Set your time zone on the trigger.
- Read your close checklist — Notion: Query a database. Reads the open items of your close checklist database in Notion (up to 100): task, owner, due date, status and notes.
- Check the due dates — Step. In code, not AI: works out each open item's days late or days left in your time zone and puts it in a tier — late, due today, due in the next 3 days or later (items without a due date are kept, untiered). Change the tiers here (buckets).
- Count what's late or due soon — Step. In code, not AI: counts the open items that are late, due today or due in the next 3 days — the close is in progress when there is at least one.
- Work out who's late and what's blocked — AI step (runs on your AI provider key). The due dates were tiered in code. AI reads the open checklist items, decides whether the close is in progress, and lists what's late, due today, blocked and left per owner.
- Close in progress? — Decision: picks the branch to follow. Posts only while the close is running; between closes nothing is posted.
- Post the close status to Slack — Slack: Post a message. Branch: Close in progress. Posts who's late, what's due today, what's blocked and what's left per owner to your close channel.
- Status posted — Kept in the run history. The run history keeps the day's close status.
- No close in progress — Kept in the run history. Branch: Between closes. Nothing due soon or late; nothing was 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.
Go live
- Open the trigger, set your time zone (days late are counted in it) and switch the schedule on. It checks every weekday at 9:00 and posts only during close.
- 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 the checklist need?
A Notion database with one page per close task and properties for the task name, owner (a person), due date and status — plus optional notes/blocker and period. Recurring close templates work well: duplicate the tasks each month with new due dates.
What filter do I enter?
Notion's filter for “not done”. For a Status property: {"property": "Status", "status": {"does_not_equal": "Done"}}. For a Select property use "select" instead of "status"; for a checkbox named Done: {"property": "Done", "checkbox": {"equals": false}}.
How are late and due-soon items worked out?
In code: “Check the due dates” counts each item's days late or days left in your trigger's time zone from its Due date property (also Due date, Deadline or Date), and only those tiers reach the AI. To change the 3-day “due soon” tier, edit the buckets there (and “Count what's late or due soon”).
Does it DM people?
No. It posts one status to your close channel and names the owners.
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.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .