Skip to Workflow Atlas
Event-Driven AutomationIntermediate

Pipedrive to Stripe Product Sync

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

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 Product 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 product created. trigger node, pipedriveTrigger. 0 incoming and 1 outgoing connections.STARTOn product createdTRIGGERPIPEDRIVETRIGGER0 IN / 1 OUTSet item to only current product data. transform node, functionItem. 1 incoming and 2 outgoing connections.STEP 02Set item to only current …TRANSFORMFUNCTIONITEM1 IN / 2 OUTCreate product in Stripe. Stripe node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Create product in StripeSTRIPEHTTPREQUEST1 IN / 1 OUTKeep only productId of created product. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Keep only productId of cr…TRANSFORMSET1 IN / 1 OUTAdd created product Id to data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 05Add created product Id to…DECISIONMERGE2 IN / 1 OUTSplit prices to seperate items. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 06Split prices to seperate …TRANSFORMITEMLISTS1 IN / 1 OUTCreate price records in Stripe. Stripe node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMECreate price records in S…STRIPEHTTPREQUEST1 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 product created

7 Execution Links
  1. Start

    On product created

    Trigger

  2. Step 2

    Set item to only current product data

    Transform

  3. Step 3

    Create product in Stripe

    Integration

  4. Step 4

    Keep only productId of created product

    Transform

  5. Step 5

    Add created product Id to data

    Decision

  6. Step 6

    Split prices to seperate items

    Transform

  7. Outcome

    Create price records in Stripe

    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.