Score customer churn risk and trigger CS follow-ups with Postgres, Mixpanel, Zendesk, Gmail, Calendly, ClickUp, and Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs on a schedule (every 6 hours). Along the way it connects Postgres, Zendesk, Gmail and ClickUp and 1 more. It also calls mixpanel.com and api.calendly.com over HTTP.
How it runs
Trigger: On a schedule (every 6 hours).
- Get Product Usage (DB) (Postgres): run a query
- Get Mixpanel Engagement (HTTP Request): calls mixpanel.com (POST)
- Get Latest NPS Scores (Postgres): run a query
- Get Recent Support Tickets (Zendesk): get many
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Calculate Churn Risk Score (Code): runs custom JavaScript code
- Is Churn Risk? (If): checks a condition and branches into true / false
- Is High Risk? (If): checks a condition and branches into true / false
…plus 5 more steps. See the full node list below.
Services it uses
HTTP calls to: mixpanel.com, api.calendly.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Postgres
n8n-nodes-base.postgres - HTTP Request
n8n-nodes-base.httpRequest - Zendesk
n8n-nodes-base.zendesk - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - ClickUp
n8n-nodes-base.clickUp - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs every 6 hours to combine customer usage and NPS data from Postgres with Mixpanel engagement and Zendesk ticket signals, calculate a churn risk score, and trigger Customer Success interventions via Gmail, Calendly, ClickUp,…