Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Pipedrive-MySQL Bidirectional Sync

Pipedrive-MySQL Bidirectional Sync is a 14-node automation blueprint connecting Pipedrive, MySQL. Inspect its trigger, execution graph, branches, and implementation requirements.

PipedriveMySQL

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

14

Nodes

13

Links

1

Run groups

Connected tools

2 integrations

  • Pipedrive
  • MySQL

Canvas controls

Fit wide systems, then zoom into any run group.

Pipedrive-MySQL Bidirectional Sync execution lanes1 run groups containing 14 workflow nodes and 13 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTPipedrive. integration node, pipedrive. 0 incoming and 1 outgoing connections.STARTPipedriveINTEGRATIONPIPEDRIVE0 IN / 1 OUTMySQL. MySQL node, mySql. 1 incoming and 1 outgoing connections.STEP 02MySQLMYSQLMYSQL1 IN / 1 OUTSet. transform node, set. 1 incoming and 1 outgoing connections.STEP 02SetTRANSFORMSET1 IN / 1 OUTCompare Datasets. decision node, compareDatasets. 2 incoming and 3 outgoing connections.STEP 03Compare DatasetsDECISIONCOMPAREDATASETS2 IN / 3 OUTCreate Person. integration node, pipedrive. 1 incoming and 0 outgoing connections.STEP 04Create PersonINTEGRATIONPIPEDRIVE1 IN / 0 OUTIF Data Changed. decision node, if. 1 incoming and 1 outgoing connections.STEP 04IF Data ChangedDECISIONIF1 IN / 1 OUTCreate Contact. MySQL node, mySql. 1 incoming and 0 outgoing connections.STEP 04Create ContactMYSQLMYSQL1 IN / 0 OUTDate & Time. integration node, dateTime. 1 incoming and 1 outgoing connections.STEP 05Date & TimeINTEGRATIONDATETIME1 IN / 1 OUTIF Updated On. decision node, if. 1 incoming and 2 outgoing connections.STEP 06IF Updated OnDECISIONIF1 IN / 2 OUTSet Input1. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Set Input1TRANSFORMSET1 IN / 1 OUTSet Input2. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Set Input2TRANSFORMSET1 IN / 1 OUTUpdate Person. integration node, pipedrive. 1 incoming and 0 outgoing connections.OUTCOMEUpdate PersonINTEGRATIONPIPEDRIVE1 IN / 0 OUTUpdate Contact. MySQL node, mySql. 1 incoming and 0 outgoing connections.OUTCOMEUpdate ContactMYSQLMYSQL1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.14 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Schedule Trigger

13 Execution Links

  1. Start

    Schedule Trigger

    Trigger

    Pipedrive

    Integration

  2. Step 2

    MySQL

    Integration

    Set

    Transform

  3. Step 3

    Compare Datasets

    Decision

  4. Step 4

    Create Person

    Integration

    IF Data Changed

    Decision

    Create Contact

    Integration

  5. Step 5

    Date & Time

    Integration

  6. Step 6

    IF Updated On

    Decision

  7. Step 7

    Set Input1

    Transform

    Set Input2

    Transform

  8. Outcome

    Update Person

    Integration

    Update Contact

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas