Scheduled Two-Way Contact Synchronization Between Pipedrive and HubSpot - n8n Workflow

Use this powerful n8n workflow to achieve robust, scheduled, two-way contact synchronization between Pipedrive and HubSpot. Maintain data integrity using the merge n8n node logic.

Workflow Preview

Ready to automate?

Download this n8n workflow template and start using it instantly.

Who is this best for?


  • Sales Operations Managers needing to synchronize contacts across different CRM platforms.

  • System Administrators managing Pipedrive and HubSpot data integrity.

  • Automation Specialists looking for a robust, differential synchronization n8n workflow example.

  • Users seeking an efficient, scheduled n8n trigger for regular data health checks.

Overview

Maintaining consistency when sales teams use multiple CRMs, like Pipedrive and HubSpot, can be a major challenge. This specialized n8n workflow provides a solution by implementing a scheduled, two-way sync based on email addresses. Using a Cron n8n trigger, the system periodically checks both platforms for new records. The core logic relies on the Merge n8n node to identify contacts that exist in one system but not the other, ensuring only net-new or unique contacts are propagated. This guarantees data integrity across both platforms, making this one of the most valuable n8n templates for CRM management.

How it Works

The entire process is initiated by a scheduled n8n trigger and executes two parallel synchronization streams:


  1. Trigger and Data Fetch: The Cron n8n trigger starts the workflow. Simultaneously, the Pipedrive n8n node and the HubSpot n8n node fetch all current person/contact records from their respective APIs. This sets up the complete data sets needed for comparison.

  2. HubSpot to Pipedrive Sync (Merge 1): The first Merge n8n node compares the HubSpot data (primary input) against the Pipedrive data (secondary input) using email addresses. The removeKeyMatches mode ensures that only HubSpot contacts whose email addresses are not found in Pipedrive are passed forward. These unique HubSpot items are then sent to the Update Pipedrive n8n node.

  3. Pipedrive to HubSpot Sync (Merge 2): The second Merge n8n node compares the Pipedrive data (primary input) against the HubSpot data (secondary input). This process identifies Pipedrive persons whose emails are not found in HubSpot.

  4. Final Action: The unique Pipedrive items are routed to the Update HubSpot n8n node, completing the bidirectional sync. This smart differential approach ensures that only necessary updates are processed in this n8n workflow.

Installation Guide

To implement this n8n workflow, follow these steps:


  1. Import the JSON: Copy the provided n8n workflow JSON and paste it directly into your n8n canvas.

  2. Pipedrive Credentials: Locate the Pipedrive n8n node (both the 'Pipedrive' Get node and 'Update Pipedrive' node) and configure your Pipedrive API credentials. Ensure the credentials have sufficient permissions to read and write person resources.

  3. HubSpot Credentials: Locate the HubSpot n8n node (both the 'HubSpot' Get node and 'Update HubSpot' node) and configure your HubSpot API credentials.

  4. Set the Schedule: Configure the Cron n8n trigger to run at your desired frequency (e.g., once every hour).

  5. Activate: Save and activate the n8n workflow. The automation will now execute on the set schedule, ensuring your data remains synchronized.

Node Details

Cron (n8n trigger): Sets the execution schedule for the entire automation. It ensures the data sync runs periodically without manual intervention.
Pipedrive (n8n node): Fetches all available person records using the getAll operation. This provides the foundational data set for the Pipedrive side of the sync.
HubSpot (n8n node): Fetches all available contact records using the getAll operation. This provides the foundational data set for the HubSpot side.
Merge1 & Merge2 (n8n node): These are the core logic nodes. They are configured with the removeKeyMatches mode to compare email keys between the two systems. This filtering ensures the workflow only attempts to create or update contacts that are missing in the target system.
Key Configuration: Comparing email[0].value (Pipedrive) against identity-profiles[0].identities[0].value (HubSpot).
Update Pipedrive (n8n node): Creates or updates Pipedrive person records. It uses expressions to pull the contact's first name and email from the incoming HubSpot item.


  • Update HubSpot (n8n node): Creates or updates HubSpot contact records. It uses expressions to pull the contact's first name ({{$json["first_name"]}}) and email ({{$json["email"][0]["value"]}}) from the incoming Pipedrive item.

Related n8n Workflows

Free

Nodes: 4 Nodes
Updated: December 26 2025
View all
Created by
Lorena
Lorena

Featured*