Customer support5 nodes$89 setup
Customer retention alerts
Detect churn signals from support and usage data, then prompt a human outreach.
The business problem
At-risk accounts are noticed at renewal, when it is already too late.
Who it is for
Subscription businesses with usage or support-based churn signals.
What the workflow does
▶
Daily account health checktrigger
Health score below 40?◇
Health score below 40?condition
true → Summarise why the account is at risk · false → Done✦
Summarise why the account is at riskai
Alert the account owner◉
Alert the account ownerintegration
Done■
Doneend
terminalSetup requirements
Define the risk signals and the outreach owner per account tier.
| Integration | Status | Actions used |
|---|---|---|
| Slack | Available | Post message |
| HubSpot | Beta | Create contact, Log activity |
Limitations, stated plainly
- Any integration listed as “requires setup” will fail until an adapter is enabled and credentials are stored.
- AI steps without a configured provider produce deterministic simulation output, labelled as such in the run log.
- Steps marked optional record a failure and let the run continue; all other step failures stop the run.
- Approval steps pause the run until an authorised teammate decides.