Skip to Workflow Atlas
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.

Interactive system map

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

14

Nodes

13

Edges

6

Zones

System stack

2 integrations

  • Pipedrive
  • MySQL
Pipedrive-MySQL Bidirectional Sync interactive execution graphStructural view of 14 workflow nodes and 13 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.Schedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTMySQL. MySQL node, mySql. 1 incoming and 1 outgoing connections.MySQLMYSQLMYSQL1 IN / 1 OUTPipedrive. integration node, pipedrive. 0 incoming and 1 outgoing connections.PipedriveINTEGRATIONPIPEDRIVE0 IN / 1 OUTSet. transform node, set. 1 incoming and 1 outgoing connections.SetTRANSFORMSET1 IN / 1 OUTCompare Datasets. decision node, compareDatasets. 2 incoming and 3 outgoing connections.Compare DatasetsDECISIONCOMPAREDATASETS2 IN / 3 OUTCreate Person. integration node, pipedrive. 1 incoming and 0 outgoing connections.Create PersonINTEGRATIONPIPEDRIVE1 IN / 0 OUTIF Data Changed. decision node, if. 1 incoming and 1 outgoing connections.IF Data ChangedDECISIONIF1 IN / 1 OUTCreate Contact. MySQL node, mySql. 1 incoming and 0 outgoing connections.Create ContactMYSQLMYSQL1 IN / 0 OUTDate & Time. integration node, dateTime. 1 incoming and 1 outgoing connections.Date & TimeINTEGRATIONDATETIME1 IN / 1 OUTIF Updated On. decision node, if. 1 incoming and 2 outgoing connections.IF Updated OnDECISIONIF1 IN / 2 OUTSet Input1. transform node, set. 1 incoming and 1 outgoing connections.Set Input1TRANSFORMSET1 IN / 1 OUTUpdate Person. integration node, pipedrive. 1 incoming and 0 outgoing connections.Update PersonINTEGRATIONPIPEDRIVE1 IN / 0 OUTSet Input2. transform node, set. 1 incoming and 1 outgoing connections.Set Input2TRANSFORMSET1 IN / 1 OUTUpdate Contact. MySQL node, mySql. 1 incoming and 0 outgoing connections.Update ContactMYSQLMYSQL1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.14 connected nodesEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The workflow is grouped into operational zones, then reviewed for the controls needed to adapt the pattern safely.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

Schedule Trigger

Trigger

02

Data & operations

6 nodes

Transformations and external-system actions that move the work forward.

MySQL

Integration

Pipedrive

Integration

Date & Time

Integration

Set Input2

Transform

Set Input1

Transform

Set

Transform

03

Intelligence & routing

3 nodes

Model calls and control points that interpret, branch, or govern the run.

Compare Datasets

Decision

IF Data Changed

Decision

IF Updated On

Decision

04

Terminal actions

4 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Create Person

Integration

Create Contact

Integration

Update Contact

Integration

Update Person

Integration

Adjacent systems

Keep tracing the stack.

Related workflows share tools and similar system patterns.

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.