Assess churn risk from HubSpot tickets with DeepSeek and Slack alerts
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 AI workflow has 13 nodes and runs on a schedule (every day at 07:00). Along the way it connects HubSpot, DeepSeek Chat Model and Slack.
How it runs
Trigger: On a schedule (every day at 07:00).
- Retrieve HubSpot Tickets (HubSpot): get many (ticket)
- Compile Tickets by Contact (Code): runs custom JavaScript code
- Churn Risk Assessment Agent (AI Agent): runs an AI agent, with model: DeepSeek AI Model; output parser: Parse Structured Output
- Set Risk Assessment Fields (Edit Fields (Set)): sets 8 fields: riskLevel, riskSummary, recommendedAction…
- Update Churn Risk in HubSpot (HubSpot): update (contact)
- Route by Churn Risk Level (Switch): routes items into 2 branches
- Notify Slack of Churn Risk (Slack): uses Slack
- Initiate Churn Follow-Up Task (HubSpot): create (engagement)
Services it uses
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 - HubSpot
n8n-nodes-base.hubspot - Code
n8n-nodes-base.code - AI Agent
@n8n/n8n-nodes-langchain.agent - DeepSeek Chat Model
@n8n/n8n-nodes-langchain.lmChatDeepSeek - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Edit Fields (Set)
n8n-nodes-base.set - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Quick overview This workflow runs daily to pull HubSpot support tickets, aggregates them per contact, uses a DeepSeek AI Agent to assess churn risk, writes the risk level and summary back to HubSpot, and alerts Customer Success in Slack while creating HubSpot…