Churn Prediction System

Who is this for?

Churn scoring n8n workflow for success teams with a Sheets export of 200 accounts that runs on schedule before calls. Usage scans, risk scores and follow-ups pile up across HTTP data, Sheets and Slack when worked by hand. You import the dg-1004 JSON slug-specific with exact credentials, tested first-try, and the Sheets plus Slack audit pack is already wired.

What problem does this solve?

You open the HTTP export to pull Fetch Customer Data, score risk with Calculate Churn Score logic in Sheets, then write Slack alerts and Email retention drafts by hand. On schedule, this workflow fetches via Fetch Customer Data, scores via Calculate Churn Score, filters via Filter High Risk and routes via Alert Account Manager and Trigger Retention Campaign with Google Sheets - Audit Log tracking. You just check hot accounts in Slack.

What this workflow does

1. Fetch Customer Data (HTTP API)
2. Alert Account Manager (Slack)
3. Trigger Retention Campaign (Email)
4. Google Sheets - Audit Log (Google Sheets)
- Includes Daniel Grey pack: Slack - Error Alerts, Google Sheets - Audit Log, Wait - Rate Limit, Set - Audit Trail (all wired).

How it works

A schedule kicks it off automatically → Fetch Customer Data, Calculate Churn Score, Filter High Risk, ending in Alert Account Manager.

Setup

1. Open danielgrey.shop/app/templates/dg-1004 → Copy JSON → n8n → Import from Clipboard (or Push to n8n)
2. Connect credentials: Google Sheets, Slack
3. Check the schedule timing, run once manually to verify — Time required: ~10 min review — then Activate.

Requirements

- n8n 2.37 or later
- Credentials for Google Sheets, Slack
- One-time $179 — yours forever, Pro unlocks it too.

Customising

- Tune scoring weights in Calculate Churn Score and cutoff in Filter High Risk for your ICP.
- Update message copy in Alert Account Manager and Trigger Retention Campaign for owner routing.
- The Daniel Grey pack (Slack - Error Alerts, Google Sheets - Audit Log, Wait - Rate Limit, Set - Audit Trail) is already wired — keep it or delete it.

v2.0 (Sep 2026, n8n 2.x): Raw Stripe REST replaced with the Stripe node (get all customers) — this also fixes the churn scorer, which now reads every customer instead of the list wrapper. Tested on n8n 2.37 (2.x).