Clean company profiles: HubSpot for routing
Runs on a schedule across HubSpot, Slack and MySQL, runs the custom logic in a Code node. Built for routing, around a "Fetch Changes Since Watermark" step, in 19 documented nodes.
Clean company profiles with HubSpot and HTTP / REST API for your team for Routing. An original, ready-to-import n8n workflow built around the 'Data Enrichment' pattern for sales & CRM. It runs on a schedule and orchestrates 19 nodes across HubSpot, Slack, HTTP / REST API. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. Nothing slips through the cracks.
Key benefits
- ✓Keeps HubSpot and Slack in step for routing, without anyone re-typing a row
- ✓A failed HubSpot or Slack call is retried rather than dropped, at any of the 19 nodes in this routing build
- ✓Every routing run leaves an audit row behind, alongside HubSpot
- ✓Fans the same result out to MySQL in the same run, for routing
- ✓Pinned sample data ships with it — run all 19 nodes for routing before wiring HubSpot
Use cases
- →Teams keeping HubSpot and Slack aligned by hand for routing
- →Routing work where "Fetch Changes Since Watermark" is still a manual step before HubSpot
- →Routing work that only reaches HubSpot on a schedule, when someone remembers to start it
Integrations
Workflow preview (19 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (19 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Advanced levelAdds branching depth and audit logging on top of the core pattern.
- •Building a provider waterfall that only pays for a fallback on a real miss
- •Scoring records after enrichment so the score sees the richest data
- •Moving data between HubSpot, MySQL and Slack in a single run
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (HubSpot, Slack, HTTP / REST API, MySQL). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Clean company profiles with Slack for routing
Routing on n8n: runs on a schedule across Slack, HubSpot and MySQL, starting at "Read Pending Queue (HubSpot)". Walks the list in batches, pausing between them. 18 documented nodes.
Augment contact records: HubSpot + approval pause
Routing on n8n: runs on a schedule across HubSpot, Slack and MySQL, starting at "Read Pending Queue (MySQL)". Walks the list in batches, pausing between them. 21 documented nodes.
Augment company profiles with Slack for routing
Routing on n8n: runs on a schedule across Slack, HubSpot, Notion and MySQL, starting at "Keep Valid Leads". Branches on the check before anything is written. 31 documented nodes.
Augment company profiles: MySQL, scheduled
Routing on n8n: runs on a schedule across MySQL, Slack and HubSpot, starting at "Pull Side A (HubSpot)". Diffs the two sides and writes only the gaps. 23 documented nodes.