Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Pipedrive to Stripe Customer Sync

Pipedrive to Stripe Customer Sync is a 7-node automation blueprint connecting Pipedrive, Stripe. Inspect its trigger, execution graph, branches, and implementation requirements.

PipedriveStripe

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

7

Links

1

Run groups

Connected tools

2 integrations

  • Pipedrive
  • Stripe

Canvas controls

Fit wide systems, then zoom into any run group.

Pipedrive to Stripe Customer Sync execution lanes1 run groups containing 7 workflow nodes and 7 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.On deal updated. trigger node, pipedriveTrigger. 0 incoming and 1 outgoing connections.STARTOn deal updatedTRIGGERPIPEDRIVETRIGGER0 IN / 1 OUTCurrent won time Not Equal to Previous. decision node, if. 1 incoming and 1 outgoing connections.STEP 02Current won time Not Equa…DECISIONIF1 IN / 1 OUTGet organisation details. integration node, pipedrive. 1 incoming and 2 outgoing connections.STEP 03Get organisation detailsINTEGRATIONPIPEDRIVE1 IN / 2 OUTSearch customer. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Search customerINTEGRATIONHTTPREQUEST1 IN / 1 OUTCustomer does not exist. decision node, if. 1 incoming and 1 outgoing connections.STEP 05Customer does not existDECISIONIF1 IN / 1 OUTContinue with organisation data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 06Continue with organisatio…DECISIONMERGE2 IN / 1 OUTCreate customer. Stripe node, stripe. 1 incoming and 0 outgoing connections.OUTCOMECreate customerSTRIPESTRIPE1 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

On deal updated

7 Execution Links

  1. Start

    On deal updated

    Trigger

  2. Step 2

    Current won time Not Equal to Previous

    Decision

  3. Step 3

    Get organisation details

    Integration

  4. Step 4

    Search customer

    Integration

  5. Step 5

    Customer does not exist

    Decision

  6. Step 6

    Continue with organisation data

    Decision

  7. Outcome

    Create customer

    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