The flow
Starts it 1Logic 6Service 9
The steps in the order they run, from what starts it.
- 1Every 6 Hours1Schedule triggerStarts it
- 2Get Product Usage (DB)1PostgresService
- 3Get Mixpanel Engagement1Http RequestService
- 4Get Latest NPS Scores1PostgresService
- 5Get Recent Support Tickets1ZendeskService
- 6Merge Usage + Mixpanel1MergeLogic
- 7Merge + NPS1MergeLogic
- 8Merge + Tickets1MergeLogic
- 9Calculate Churn Risk Score1CodeLogic
- 10Is Churn Risk?1IfLogic
- 11Is High Risk?1IfLogic
- 12Send Check-in Email1GmailService
- 13Book CS Call1Http RequestService
- 14Create CS Task (ClickUp)1Click UpService
- 15Escalate to Account Manager1SlackService
- 16Log Intervention1PostgresService
How it's built
- Starts on
- A clock
- Steps
- 16, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- ClickUp, Gmail, Postgres, Slack, Zendesk
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own ClickUp, Gmail, Postgres, Slack and Zendesk accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.