Agent setup guide
Churn Risk Watch
Scores every account's churn risk weekly and alerts CS in Slack with a play for each at-risk account.
What it does
Scores every account's churn risk weekly and alerts CS in Slack with a play for each at-risk account.
- Runs weekly (Mondays at 7:00 by default) and reads your account health tab in Google Sheets.
- Renewal and last-contact dates are worked out in code, never by the AI: days until each renewal (within 60 days?) and days since the last contact (60 or more?), in your trigger's time zone.
- AI scores each account's churn risk from 0 to 100 from the usage, seat, support, NPS, renewal and contact signals in the sheet, weighted by what you say healthy looks like.
- Explains every high-risk score with the values behind it and recommends one play from your CS playbook, with the account owner.
- Picks out expansion candidates (seats nearly full, growing usage).
- Saves the full weekly report to Notion and, when any account is high risk, alerts your CS channel in Slack.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Google Sheets, Notion and Slack, connected in Settings → Integrations.
- A Google Sheet with one row per account and its usage and renewal data, kept up to date by export or another workflow.
What it doesn't do
- It doesn't connect to product analytics, billing or support tools directly; it reads the sheet.
- It isn't a trained statistical model and can't guarantee a 30-day warning: scores are AI judgments you can check.
- It doesn't contact customers or create CRM tasks; your CS team runs the plays.
- It reviews up to a few hundred accounts per run; split larger books into several tabs and copies of the agent.
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: Google Sheets, Notion and Slack.
- Nothing to send: the agent runs on a schedule.
- About 20 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 Google Sheets
Connect the Google account that can open your account health sheet (Settings → Integrations → Google Sheets).
3. Connect Notion
Connect the Notion workspace for the weekly reports (Settings → Integrations → Notion), and share the database with Fluxo Flow.
4. Connect Slack
Connect the Slack workspace your CS team uses (Settings → Integrations → Slack).
5. Pick your account health sheet
Open “Read your account health sheet”, pick your Google account, paste the spreadsheet link and pick the tab.
| Setting | What to enter | In step |
|---|---|---|
| Google account | The Google account that can open your account health sheet. Pick your connected Google Sheets account. | “Read your account health sheet” |
| Account health spreadsheet | Paste the link of the Google Sheet with one row per customer account. | “Read your account health sheet” |
| Accounts tab | The tab with one row per account (up to a few hundred accounts). | “Read your account health sheet” |
6. Describe healthy accounts and your plays
Open “Score churn risk and find expansion” and replace the placeholder with your signals, column meanings and CS plays.
| Setting | What to enter | In step |
|---|---|---|
| Your healthy-account signals and CS plays | Replace the placeholder with what your product does, what healthy usage looks like, what each column means and the plays your CS team runs. It starts as “[DESCRIBE YOUR PRODUCT, YOUR HEALTHY-ACCOUNT SIGNALS AND YOUR CS PLAYS HERE]” until you replace it. | “Score churn risk and find expansion” |
7. Pick the Notion database
Open “Save the weekly risk report to Notion” and pick your account and database.
| Setting | What to enter | In step |
|---|---|---|
| Notion account | The Notion workspace the weekly report is saved to. Pick your connected Notion account. | “Save the weekly risk report to Notion” |
| Notion database for reports | The database each weekly report becomes a page in. Share it with Fluxo Flow first: ••• → Connections. | “Save the weekly risk report to Notion” |
8. Pick the Slack account and CS channel
Open “Alert customer success in 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 churn alert is posted to. Pick your connected Slack account. | “Alert customer success in Slack” |
| Customer success channel | Where your CS team sees at-risk accounts, e.g. #customer-success. | “Alert customer success in Slack” |
9. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
10. Switch the trigger on
Open the trigger, check the day, time and time zone, and 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 Monday at 7:00 — Runs on a schedule (cron 0 7 * * 1, UTC — change it in the trigger's settings). Runs once a week before your CS stand-up (change the schedule and time zone on the trigger).
- Read your account health sheet — Google Sheets: Read rows. Reads every row of your accounts tab in Google Sheets: one row per customer account with usage, support and renewal columns.
- Work out renewal and contact dates — Step. In code, not AI: adds to every account the days until its renewal (and whether that's within 60 days) and the days since the last contact (and whether that's 60 days or more). No account is dropped. Change the 60s here (within).
- Score churn risk and find expansion — AI step (runs on your AI provider key). AI scores each account's churn risk 0–100 from the signals in your sheet, explains the score, suggests a play for each at-risk account and picks out expansion candidates. Renewal and contact dates are worked out in code first.
- Save the weekly risk report to Notion — Notion: Create a page in a database. Creates a page in your Notion database with the summary, the at-risk accounts and their plays, expansion candidates and every account's score.
- Report saved — Kept in the run history. The run history keeps every weekly report.
- Any high-risk accounts? — Decision: picks the branch to follow. Weeks with at least one high-risk account page your CS channel in Slack; quiet weeks only get the Notion report.
- Alert customer success in Slack — Slack: Post a message. Branch: High risk found. Posts the high-risk accounts with their signals, recommended play and owner, plus expansion candidates, to your CS channel.
- CS alerted — Kept in the run history. The run history keeps the alert.
- No high-risk accounts — Kept in the run history. Branch: None. Nothing posted to Slack this week; the report is in Notion.
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, check the day, time and time zone, and 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
Where does the usage data come from?
From a Google Sheet you keep up to date: an export from your product analytics, billing or CRM, or another workflow that writes to it. The agent doesn't connect to those tools directly.
Is this a machine-learning model?
No. AI scores each account with the rules and signals you describe, and explains every score so your team can judge it.
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 .