Two-way sync between Pipedrive and HubSpot

Needs changes

by Lorena ✓ · 1,477 views · created 2021-11-18 · CRM

Needs 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 7 nodes and runs on a schedule (legacy Cron node). Along the way it connects Pipedrive and HubSpot.

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
Merge: merges the data from its input branches
Update Pipedrive (Pipedrive): work with person
Update HubSpot (HubSpot): work with contact

Services it uses

Pipedrive HubSpot

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)

Cronn8n-nodes-base.cron
Pipedriven8n-nodes-base.pipedrive
HubSpotn8n-nodes-base.hubspot
Mergen8n-nodes-base.merge

From the author

This workflow synchronizes data both ways between Pipedrive and HubSpot. - Cron node schedules the workflow to run every minute. - Pipedrive and Hubspot nodes pull in both lists of persons from Pipedrive and contacts from HubSpot. - Merge1 and Merge2 nodes…
Excerpt from Lorena's description on n8n.io.

View the original on n8n.io → Check your own copy

Two-way sync between Pipedrive and HubSpot

What this workflow does

How it runs

Services it uses

Before you upgrade to n8n 3.0

Nodes used (4)

From the author

Get the weekly “what broke” email