Block 1 - Mixpanel Webhook
- Type / Role
- n8n-nodes-base.webhook - webhook
- Config choices
- Version 2
How it works This workflow automatically detects at risk customers by listening for inactivity signals from Mixpanel, scoring their churn risk, syncing everything to HubSpot, creating a prioritized...
n8n-nodes-base.webhook, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.set, n8n-nodes-base.hubspot, n8n-nodes-base.clickup, n8n-nodes-base.slack, n8n-nodes-base.httprequest
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.
Original n8n.io sourceThis workflow automatically detects at-risk customers by listening for inactivity signals from Mixpanel, scoring their churn risk, syncing everything to HubSpot, creating a prioritized ClickUp follow-up task, and alerting the customer success team on Slack — all without any manual effort.
Trigger & parse
Mixpanel Webhook – Receives POST events from Mixpanel when a customer inactivity event is fired (e.g. user_inactive_30_days). Supports both single events and batch arrays.
Parse Mixpanel Payload – Normalizes the raw Mixpanel payload, extracting email, name, user ID, company, plan, MRR, inactive days, last active date, last feature used, total sessions, location, and CSM assignment. Skips records with no identifying information.
Event validation
Is Churn Event – Confirms the event name matches user_inactive_30_days, has no parse errors, and includes a valid email before proceeding.
Risk scoring
Enrich User Data – Calculates churn score (Medium / High / Critical) and task priority based on inactive days, sets a due date of 24 hours and a follow-up date of 3 days, and builds the alert subject line with risk level.
CRM lookup
HubSpot Find Contact – Searches HubSpot for an existing contact by email, retrieving name, company, lifecycle stage, owner, lead status, and phone.
Contact Found – Routes to the full retention flow if a contact exists, or to a Slack fallback alert if no contact is found.
Slack Contact Not Found – Posts a Slack warning to the team for manual action when no HubSpot contact matches the churn event email.
Deal management
HubSpot Get Deals – Fetches all deals associated with the found HubSpot contact via the CRM Associations API.
Deal Exists – Routes to update the existing deal or create a new one based on whether an associated deal is found.
HubSpot Update Deal – Updates the existing deal stage to appointmentscheduled and sets the close date to the follow-up date.
HubSpot Create Deal – Creates a new churn risk deal linked to the contact, with annual value (MRR × 12), deal name, and follow-up close date.
Set Deal ID – Normalizes the deal ID from either the update or create branch for consistent downstream use.
CRM logging & task creation
HubSpot Log Note – Posts a detailed churn risk note on the HubSpot contact record linked to both the contact and the deal, including all churn signals and MRR data.
ClickUp Create Task – Creates a prioritized CS follow-up task with a full action checklist covering outreach, Mixpanel review, discovery call scheduling, and escalation criteria. Due within 24 hours.
Slack CS Alert – Posts a comprehensive churn risk alert to the CS Slack channel with customer details, revenue impact, churn signals, risk score, HubSpot links, and a full action checklist.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Detect Mixpanel churn and create HubSpot, ClickUp, and Slack retention alerts |
|---|---|
| Complexity | advanced |
| Nodes | 23 |
| Categories | CRM, AI Summarization |
| Author | Avkash Kakdiya |
| Published | 21 May 2026 |
Use the JSON export at /data/workflows/15877/15877.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works This workflow automatically detects at risk customers by listening for inactivity signals from Mixpanel, scoring their churn risk, syncing everything to HubSpot, creating a prioritized...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your CRM, AI Summarization use case.