Skip to main content

Churn risk alerts

Twice a week this workflow looks for the company that is most likely to stop ordering and creates an action in the Action Hub, so a sales rep can call before the customer leaves. By default it flags one company per run, so at most two a week.

To check one company at the moment you want, use the Company churn check. It uses the same score.

In short
Where you use itIn the background. The results show in the Action Hub
StartsBy itself, every Monday and Thursday at 06:00
Changes in PropellerCreates actions. It changes no company and no order
Uses AINo
TextsEnglish and Dutch
Runs in n8nAbout 9 a month
DifficultyMedium. You set who gets the actions

What you get​

One action per run for the company with the highest score. It says which signals dropped and opens the company page.

A churn risk action in the Action Hub, opened to show which signals dropped and the churn score

What you need​

  • An n8n account with the credential Propeller API key. See Set up n8n.
  • An API key with Viewer access on Order Data and Owner access on User management. The workflow reads orders and companies. Owner access on User management is what lets it create actions.

How it works​

The workflow reads the orders of the last 90 days and gives every company that ordered a score from 0 to 100. The score compares the last 30 days with the 60 days before.

SignalShare of the score
The company orders less often40%
The company spends less per order30%
The company is quiet for longer than usual30%

A company gets an action from a score of 30. A company needs at least 2 orders in the 60 days before, so a customer who orders less than once a month is never scored.

A company with a churn action that is still open, or one from the last 30 days, is skipped.

Good to know

The workflows and agents in the Agent Hub are free to use and adapt. They are examples, not supported product features. Test them in a test environment and check the results before you use them on real customers.

Install it​

Install a workflow from the library explains each step.

  1. Import the file into n8n.
  2. Check that the five nodes that talk to Propeller use the credential Propeller API key.
  3. Open the Settings node and set ASSIGN_TO_ADMIN_USER_ID to the colleague who gets the actions. The number is in the Id column under Admin > Backoffice Users.
  4. Check ORDER_STATUSES. See Fill in order status codes.
  5. Click Execute workflow to run it once.
  6. Click Publish.

After a run you find one new action in the Action Hub. A test run is a real run and the action is real. If nothing appears, no company scored 30 or higher. It can also mean that the companies that did were flagged in the last 30 days.

Make it yours​

SettingDefaultWhat it does
TOP_N1Actions per run, highest score first
SCORE_THRESHOLD30The lowest score that gets an action
RECENT_DAYS30The period that is judged
BASELINE_DAYS60The period before it, which counts as normal for the company
COOLDOWN_DAYS30Days before a company can get a new action
ASSIGN_TO_ADMIN_USER_IDnullThe colleague who gets the actions. With null they go to nobody
ORDER_STATUSESNEW, CONFIRMED, VALIDATED, ARCHIVEDThe statuses that count as an order

To change the days or the time, open the node Schedule Mon+Thu 6am.

Limits​

  • A run reads at most 200,000 orders. With more orders in 90 days the run stops with an error and creates nothing.
  • When the orders cannot be read completely, the run also stops. You never get an action that is based on part of the orders.