Pipedrive to HubSpot Contact Synchronization - n8n Workflow

• Sales Operations teams requiring synchronization between disparate CRM systems.


• Marketing professionals who need Pipedrive lead data funneled into HubSpot for campaigns.


• Users looking for proven n8n templates for CRM data migration and management.


• Anyone who needs a robust n8n workflow solution for scheduled data comparisons.

Keeping multiple Customer Relationship Management (CRM) systems in sync can be a significant administrative burden. This powerful n8n workflow template solves that problem by providing a reliable, automated pipeline to move contact data from Pipedrive to HubSpot. The solution uses a scheduled n8n trigger to check for updates frequently, ensuring all new 'Person' records created in Pipedrive are mirrored in HubSpot.

The key advantage of this specific n8n workflow is its intelligent deduplication mechanism. Before creating any records, a specialized n8n node compares existing HubSpot contacts against the Pipedrive list using email addresses. Only unique, newly created Pipedrive contacts are then processed and added to HubSpot, maintaining data integrity and preventing costly duplicates. This ready-to-use n8n template drastically reduces manual effort and ensures consistency across your sales and marketing platforms.

The entire process is driven by the Cron n8n trigger, which initiates the synchronization check every minute, providing near real-time updates.

1. Parallel Data Retrieval: The Cron n8n trigger simultaneously activates two independent branches: the Pipedrive n8n node retrieves all 'Person' records, and the first Hubspot n8n node retrieves all existing 'Contact' records.


2. Deduplication Logic: The crucial Merge n8n node takes both datasets. Configured to removeKeyMatches, it compares the primary email field from Pipedrive contacts against the primary identity value (email) in HubSpot contacts. The Merge n8n node then outputs a list containing only the Pipedrive contacts that do not yet exist in HubSpot.


3. Contact Creation: The final Hubspot n8n node takes the deduplicated list of new contacts and creates them within HubSpot. It utilizes dynamic n8n expressions (={{$json["email"][0]["value"]}} and ={{$json["first_name"]}}) to accurately map the data fields from the Pipedrive structure to the required HubSpot contact properties. This ensures a clean and effective transfer using the configured n8n workflow.

To use this n8n workflow template, follow these steps:

1. Import: Copy the provided JSON code and import it into your self-hosted or cloud n8n instance.


2. Pipedrive Credentials: Locate the Pipedrive n8n node and set up or select your existing Pipedrive API credential, ensuring it has necessary access to read person data.


3. HubSpot Credentials: Configure the credentials for both Hubspot n8n nodes (named 'Hubspot' and 'HubSpot2'). These credentials require permissions to read all contacts and create new ones.


4. Activation: The Cron n8n trigger is configured to run every minute. Once credentials are set, activate the n8n workflow. You can modify the Cron n8n node parameters to adjust the synchronization frequency if needed.

Cron (n8n trigger): Acts as the primary n8n trigger, scheduled to run the entire n8n workflow every minute.
Pipedrive (n8n node): Function: Retrieves all person records (contacts) from Pipedrive. Key Configuration: Resource: Person, Operation: getAll, Return All: true.
Hubspot (n8n node): Function: Retrieves all existing contact records from HubSpot. This dataset is used to check for duplicates. Key Configuration: Resource: Contact, Operation: getAll, Return All: true.
Merge (n8n node): Function: Performs the deduplication logic. It compares contacts from both systems based on their email address. Key Configuration: Mode: removeKeyMatches, Property Name 1 (Pipedrive Email Path): email[0].value, Property Name 2 (HubSpot Email Path): identity-profiles[0].identities[0].value.

• HubSpot2 (n8n node): Function: Creates the unique Pipedrive contacts in HubSpot. Key Configuration: Resource: Contact, Data Mapping: Email is set using the expression ={{$json["email"][0]["value"]}} and First Name is mapped via ={{$json["first_name"]}}.