One-way sync between Pipedrive and HubSpot
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 5 nodes and runs on a schedule (legacy Cron node). Along the way it connects HubSpot and Pipedrive.
How it runs
Trigger: On a schedule (legacy Cron node).
- Pipedrive: get many (person)
- HubSpot: get many (contact)
- Merge: merges the data from its input branches
- HubSpot: work with contact
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron: replace with Schedule Trigger.
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron | Schedule Trigger |
Nodes used (4)
- HubSpot
n8n-nodes-base.hubspot - Pipedrive
n8n-nodes-base.pipedrive - Merge
n8n-nodes-base.merge - Cron
n8n-nodes-base.cron
From the author
This workflow synchronizes data one-way from Pipedrive to HubSpot. - Cron node schedules the workflow to run every minute. - Pipedrive and Hubspot1 nodes pull in both lists of persons from Pipedrive and contacts from HubSpot. - Merge node with the option…