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

CRM Data Synchronization Workflow

CRM Data Synchronization Workflow is a 7-node automation blueprint connecting Pipedrive, HubSpot. Inspect its trigger, execution graph, branches, and implementation requirements.

PipedriveHubSpot

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.

7

Nodes

8

Links

1

Run groups

Connected tools

2 integrations

  • Pipedrive
  • HubSpot

Canvas controls

Fit wide systems, then zoom into any run group.

CRM Data Synchronization Workflow execution lanes1 run groups containing 7 workflow nodes and 8 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.Cron. integration node, cron. 0 incoming and 2 outgoing connections.STARTCronINTEGRATIONCRON0 IN / 2 OUTPipedrive. integration node, pipedrive. 1 incoming and 2 outgoing connections.STEP 02PipedriveINTEGRATIONPIPEDRIVE1 IN / 2 OUTHubSpot. HubSpot node, hubspot. 1 incoming and 2 outgoing connections.STEP 02HubSpotHUBSPOTHUBSPOT1 IN / 2 OUTMerge1. decision node, merge. 2 incoming and 1 outgoing connections.STEP 03Merge1DECISIONMERGE2 IN / 1 OUTMerge2. decision node, merge. 2 incoming and 1 outgoing connections.STEP 03Merge2DECISIONMERGE2 IN / 1 OUTUpdate Pipedrive. integration node, pipedrive. 1 incoming and 0 outgoing connections.OUTCOMEUpdate PipedriveINTEGRATIONPIPEDRIVE1 IN / 0 OUTUpdate HubSpot. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.OUTCOMEUpdate HubSpotHUBSPOTHUBSPOT1 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.7 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

Cron

8 Execution Links

  1. Start

    Cron

    Integration

  2. Step 2

    Pipedrive

    Integration

    HubSpot

    Integration

  3. Step 3

    Merge1

    Decision

    Merge2

    Decision

  4. Outcome

    Update Pipedrive

    Integration

    Update HubSpot

    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