The flow
Starts it 1Model 4Logic 4Service 4
The steps in the order they run, from what starts it.
- 1When Support Tickets ScannedSchedule triggerStarts it
- 2DeepSeek AI ModelLm Chat Deep SeekModel
- 3DeepSeek Model FixerLm Chat Deep SeekModel
- 4Retrieve HubSpot TicketsHubspotService
- 5Churn Risk Assessment AgentAgentModel
- 6Parse Structured OutputOutput Parser StructuredModel
- 7Compile Tickets by ContactCodeLogic
- 8Log Failure for ReviewNo OpLogic
- 9Set Risk Assessment FieldsSetLogic
- 10Update Churn Risk in HubSpotHubspotService
- 11Route by Churn Risk LevelSwitchLogic
- 12Notify Slack of Churn RiskSlackService
- 13Initiate Churn Follow-Up TaskHubspotService
How it's built
- Starts on
- A clock
- Steps
- 13, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- HubSpot, Slack
- Model
- DeepSeek
Questions
What does it need to run?
An n8n account, plus your own HubSpot and Slack accounts, and a key for DeepSeek. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
Yes. It calls DeepSeek. Model calls are billed by the provider, not by n8n.
How long does it take to set up?
Plan an afternoon. 13 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 13 steps before you point it at anything that matters.