Augment contact records: HubSpot + approval pause
Runs on a schedule across HubSpot, Slack and MySQL, walks the list in batches, pausing between them, then drops anything it has already handled. Built for routing, around a "Read Pending Queue (MySQL)" step, in 21 documented nodes.
Augment contact records with HubSpot and HTTP / REST API automatically 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 21 nodes across HubSpot, Slack, MySQL. 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. What used to take a morning now runs on its own.
Key benefits
- ✓Keeps HubSpot and Slack in step for routing, without anyone re-typing a row
- ✓Safe to re-run: records already in HubSpot or Slack are skipped, across all 21 nodes of this routing build
- ✓A failed HubSpot or Slack call is retried rather than dropped, at any of the 21 nodes in this routing build
- ✓The pause before HubSpot is durable — a routing run survives a restart
- ✓Batches the work so HubSpot rate limits never break a routing run
Use cases
- →Teams keeping HubSpot and Slack aligned by hand for routing
- →Routing sequences that run over days and must survive a restart before HubSpot
- →A backlog too large to push into HubSpot in one pass, across 21 nodes
- →Routing work where "Read Pending Queue (MySQL)" is still a manual step before HubSpot
Integrations
Workflow preview (21 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (21 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
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Scoring records after enrichment so the score sees the richest data
- •Upserting so repeat runs update rather than duplicate
- •Moving data between MySQL, HubSpot 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, MySQL, HTTP / REST API). 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 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.
Augment company profiles: MySQL, batched
Routing on n8n: runs on a schedule across MySQL, Slack and HubSpot, starting at "Read Pending Queue (HubSpot)". Walks the list in batches, pausing between them. 16 documented nodes.