Two-Way Sync Pipedrive and MySQL Contacts

Name: Two-Way Sync Pipedrive and MySQL Contacts
Rating: 5 (5 reviews)
Author: Free N8N

Intermediate

12 nodes connected

detail.loadingPreview

Free N8N Temples

182 views

0 downloads

Data Managementautomationcontactsmysqlpipedrivesync

Synchronizes contact data between Pipedrive and a MySQL database to ensure data consistency.

About This Workflow

This workflow is designed to maintain a consistent and up-to-date contact list across both Pipedrive and a MySQL database. It fetches contacts from both sources, compares them, and updates or creates records as needed to ensure a two-way synchronization.

Key functionalities include:

Fetching contacts from Pipedrive.
Querying contacts from a MySQL database.
Comparing datasets based on email to identify differences and common entries.
Updating existing contacts in Pipedrive or MySQL if changes are detected.
Creating new contacts in either system if they are missing in the other.
Handling of updated timestamps to determine the most recent data.

Key Features

Bi-directional Synchronization: Ensures data is consistent in both Pipedrive and MySQL.
Data Comparison: Utilizes compareDatasets to intelligently identify new, updated, and common records.
Conditional Logic: Employs if nodes to execute specific actions based on data changes and timestamps.
Data Transformation: Uses set nodes to format and prepare data for different systems.
Error Handling (Implicit): While not explicitly detailed, the structure allows for identifying discrepancies that can be further handled.
Scheduled Execution: Triggered by a scheduleTrigger for regular synchronization.

How To Use

Schedule Trigger (Schedule Trigger): Configure the workflow to run at a desired interval (e.g., hourly, daily).
Fetch MySQL Contacts (MySQL): Connect to your MySQL database and execute a query to retrieve contact information.
Fetch Pipedrive Contacts (Pipedrive): Connect to your Pipedrive account to retrieve all person records.
Prepare Pipedrive Data (Set): Transform Pipedrive contact data into a standardized format, mapping fields like primary_email to email and handling phone number arrays.
Compare Datasets (Compare Datasets): This is the core of the synchronization. It compares the MySQL contacts (input1) with the prepared Pipedrive contacts (input2) based on the 'email' field. It outputs:
- different: Records that exist in one dataset but not the other, or have different values.
- same: Records that are identical in both datasets.
Handle Data Changes (IF Data Changed): This node checks if there are any differences in 'name' or 'phone' fields between the two datasets.
Timestamp Comparison (IF Updated On): If data has changed, this node compares the updated_on timestamps from both sources to determine which record is more recent.
Prepare Input for Updates/Creations:
- If Pipedrive is more recent (Set Input1): Extracts data from the Pipedrive record that needs to be updated in MySQL.
- If MySQL is more recent (Set Input2): Extracts data from the MySQL record that needs to be updated in Pipedrive.
Update/Create Records:
- Update Pipedrive (Update Person): If Pipedrive has the most recent changes (identified by Set Input1), this node updates the corresponding person in Pipedrive.
- Update MySQL (Update Contact): If MySQL has the most recent changes (identified by Set Input2), this node updates the corresponding contact in MySQL.
- Create Pipedrive (Create Person): If a contact is found in MySQL but not in Pipedrive (as indicated by Compare Datasets output), this node creates a new person in Pipedrive.
- Create MySQL (Create Contact): If a contact is found in Pipedrive but not in MySQL (as indicated by Compare Datasets output), this node creates a new contact in MySQL.
Date & Time Formatting (Date & Time): Used to format timestamps for comparison and potential storage.

Apps Used

automation

contacts

mysql

pipedrive

sync

Workflow JSON

{
  "id": "9690c82d-9edb-4ae8-8e17-98ed83778c01",
  "name": "Two-Way Sync Pipedrive and MySQL Contacts",
  "nodes": 12,
  "category": "Data Management",
  "status": "active",
  "version": "1.0.0"
}

Note: This is a sample preview. The full workflow JSON contains node configurations, credentials placeholders, and execution logic.