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

Pipedrive and Datagma Lead Enrichment Workflow

Pipedrive and Datagma Lead Enrichment Workflow is a 9-node automation blueprint connecting Pipedrive, Datagma. Inspect its trigger, execution graph, branches, and implementation requirements.

PipedriveDatagma

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.

9

Nodes

9

Links

1

Run groups

Connected tools

2 integrations

  • Pipedrive
  • Datagma

Canvas controls

Fit wide systems, then zoom into any run group.

Pipedrive and Datagma Lead Enrichment Workflow execution lanes1 run groups containing 9 workflow nodes and 9 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.Pipedrive Trigger - New Company Created. trigger node, pipedriveTrigger. 0 incoming and 1 outgoing connections.STARTPipedrive Trigger - New C…TRIGGERPIPEDRIVETRIGGER0 IN / 1 OUTDatagma - Enrich Company. integration node, httpRequest. 1 incoming and 2 outgoing connections.STEP 02Datagma - Enrich CompanyINTEGRATIONHTTPREQUEST1 IN / 2 OUTlist people. transform node, itemLists. 1 incoming and 2 outgoing connections.STEP 03list peopleTRANSFORMITEMLISTS1 IN / 2 OUTPipedrive - Enrich Organization. integration node, pipedrive. 1 incoming and 0 outgoing connections.STEP 03Pipedrive - Enrich Organi…INTEGRATIONPIPEDRIVE1 IN / 0 OUTIf lead is Ideal Buyer. decision node, if. 1 incoming and 1 outgoing connections.STEP 04If lead is Ideal BuyerDECISIONIF1 IN / 1 OUTDatagma - Find Emails. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Datagma - Find EmailsINTEGRATIONHTTPREQUEST1 IN / 1 OUTPrepare Data Before Merge. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Prepare Data Before MergeTRANSFORMSET1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 07MergeDECISIONMERGE2 IN / 1 OUTPipedrive - Add Person. integration node, pipedrive. 1 incoming and 0 outgoing connections.OUTCOMEPipedrive - Add PersonINTEGRATIONPIPEDRIVE1 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.9 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

Pipedrive Trigger - New Compan…

9 Execution Links

  1. Start

    Pipedrive Trigger - New Company Created

    Trigger

  2. Step 2

    Datagma - Enrich Company

    Integration

  3. Step 3

    list people

    Transform

    Pipedrive - Enrich Organization

    Integration

  4. Step 4

    If lead is Ideal Buyer

    Decision

  5. Step 5

    Datagma - Find Emails

    Integration

  6. Step 6

    Prepare Data Before Merge

    Transform

  7. Step 7

    Merge

    Decision

  8. Outcome

    Pipedrive - Add Person

    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