Sales · n8n

Compute a Customer Health Score and Alert on Churn Risk

Save accounts before they leave — combine usage, support and billing signals into a health score and alert CSMs when an account turns risky.

difficulty Advancedsetup 45 minresult Customer success gets early warning on at-risk accounts, enabling saves before churn happens.
  1. 1

    Schedule the Scoring

    Add a Schedule Trigger running daily across your active accounts.

  2. 2

    Gather Signals

    Add HTTP Request nodes pulling usage trends, support ticket volume and payment health per account.

  3. 3

    Compute the Score

    Add a Code node combining the signals into a 0-100 health score with weightings you control.

  4. 4

    Alert on Decline

    Add an IF node flagging accounts that dropped below a threshold or fell sharply, then a Slack alert to the CSM.

  5. 5

    Activate and Test

    Activate the workflow and feed a test account declining signals. Confirm the risk alert fires.

Frequently asked questions

What signals matter most?

Declining core-feature usage and rising support friction are usually the strongest churn predictors — weight them highly.

Can I automate a playbook?

Trigger a save playbook (check-in email, CSM task) automatically when an account crosses into the risk zone.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.