Mirror records between tools: MySQL, scheduled
Runs on a schedule across MySQL, HubSpot and Slack, diffs the two sides and writes only the gaps, then rolls the rows up into a few numbers. Built for process orchestration, around a "Pull Side A (HubSpot)" step, in 18 documented nodes.
Mirror records between tools with HubSpot and MySQL. An original, ready-to-import n8n workflow built around the 'Two-System Sync' pattern for productivity & personal. It runs on a schedule and orchestrates 18 nodes across MySQL, HubSpot, Slack. 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 MySQL and HubSpot in step for process orchestration, without anyone re-typing a row
- ✓Compares MySQL against HubSpot before writing, so only genuine differences land
- ✓A failed MySQL or HubSpot call is retried rather than dropped, at any of the 18 nodes in this process-orchestration build
- ✓Branches rejoin before MySQL, so a process-orchestration run reports once rather than 18 times
- ✓Every process-orchestration run leaves an audit row behind, alongside MySQL
Use cases
- →Teams keeping MySQL and HubSpot aligned by hand for process orchestration
- →Reconciling MySQL against HubSpot after the two quietly drifted apart
- →Process orchestration work where "Pull Side A (HubSpot)" is still a manual step before MySQL
- →Process orchestration work that only reaches MySQL on a schedule, when someone remembers to start it
Integrations
Workflow preview (18 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (18 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.
- •Diffing two datasets into add / update / in-sync / backfill lanes
- •Choosing a stable matching key for reconciliation
- •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 (MySQL, HubSpot, Slack, Microsoft Teams). 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
Sync records between tools with HubSpot & MySQL
Process orchestration on n8n: runs on a schedule across HubSpot, MySQL, Slack and Microsoft Teams, starting at "Fetch Changes (HubSpot)". Runs the custom logic in a Code node. 17 documented nodes.
Sync records between tools: MySQL & HubSpot
Triggers on n8n: runs on a schedule across MySQL, HubSpot, Slack, Google Sheets and Microsoft Teams, starting at "Map to Canonical Schema". 22 documented nodes.
Sync records between tools: HubSpot for utilities
Utilities on n8n: runs on a schedule across HubSpot, Slack, MySQL and Microsoft Teams, starting at "Map to Canonical Schema". Routes each kind of record down its own branch. 24 documented nodes.
Sync contacts across systems: HubSpot & MySQL
Triggers on n8n: runs on a schedule across HubSpot, MySQL, Slack, Google Sheets and Microsoft Teams, starting at "Map to Canonical Schema". 22 documented nodes.