The flow
Starts it 1Logic 7Service 8
The steps in the order they run, from what starts it.
- 1Daily churn analysis at 2 AMSchedule triggerStarts it
- 2Fetch active customer profilesHttp RequestService
- 3Fetch customer activity logs (30 days)Http RequestService
- 4Fetch transaction history (90 days)Http RequestService
- 5Merge customer and activity dataMergeLogic
- 6Engineer behavioral featuresCodeLogic
- 7Call ML churn prediction modelHttp RequestService
- 8Score and classify churn riskCodeLogic
- 9Route by risk levelSwitchLogic
- 10Create retention campaign taskHttp RequestService
- 11Store churn predictions in databasePostgresService
- 12Generate churn analytics reportCodeLogic
- 13Filter at-risk customersFilterLogic
- 14Post churn alert to SlackHttp RequestService
- 15Email report to customer success teamEmail SendService
- 16Log analysis completionCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Email, Postgres
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email and Postgres 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.