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

Daily Stripe to Pipedrive Charge Sync

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

StripePipedrive

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.

11

Nodes

11

Links

1

Run groups

Connected tools

2 integrations

  • Stripe
  • Pipedrive

Canvas controls

Fit wide systems, then zoom into any run group.

Daily Stripe to Pipedrive Charge Sync execution lanes1 run groups containing 11 workflow nodes and 11 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.Every day at 8 am. integration node, cron. 0 incoming and 1 outgoing connections.STARTEvery day at 8 amINTEGRATIONCRON0 IN / 1 OUTGet customers. Stripe node, stripe. 0 incoming and 1 outgoing connections.STARTGet customersSTRIPESTRIPE0 IN / 1 OUTGet last execution timestamp. transform node, functionItem. 1 incoming and 1 outgoing connections.STEP 02Get last execution timest…TRANSFORMFUNCTIONITEM1 IN / 1 OUTRename fields and keep only needed fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Rename fields and keep on…TRANSFORMSET1 IN / 1 OUTSearch for charges in Stripe. Stripe node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Search for charges in Str…STRIPEHTTPREQUEST1 IN / 1 OUTSplit array of charges to items. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 04Split array of charges to…TRANSFORMITEMLISTS1 IN / 1 OUTAdd customer name to charge data. decision node, merge. 2 incoming and 2 outgoing connections.STEP 05Add customer name to char…DECISIONMERGE2 IN / 2 OUTSearch organisation. integration node, pipedrive. 1 incoming and 1 outgoing connections.STEP 06Search organisationINTEGRATIONPIPEDRIVE1 IN / 1 OUTAdd organisation Information to charge data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 07Add organisation Informat…DECISIONMERGE2 IN / 1 OUTCreate note with charge information. integration node, pipedrive. 1 incoming and 1 outgoing connections.STEP 08Create note with charge i…INTEGRATIONPIPEDRIVE1 IN / 1 OUTSet new last execution timestamp. transform node, functionItem. 1 incoming and 0 outgoing connections.OUTCOMESet new last execution ti…TRANSFORMFUNCTIONITEM1 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.11 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

Every day at 8 am

11 Execution Links

  1. Start

    Every day at 8 am

    Integration

    Get customers

    Integration

  2. Step 2

    Get last execution timestamp

    Transform

    Rename fields and keep only needed fields

    Transform

  3. Step 3

    Search for charges in Stripe

    Integration

  4. Step 4

    Split array of charges to items

    Transform

  5. Step 5

    Add customer name to charge data

    Decision

  6. Step 6

    Search organisation

    Integration

  7. Step 7

    Add organisation Information to charge data

    Decision

  8. Step 8

    Create note with charge information

    Integration

  9. Outcome

    Set new last execution timestamp

    Transform

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