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

Lead Enrichment and Notification Workflow

Lead Enrichment and Notification Workflow is a 16-node automation blueprint connecting Clearbit, Pipedrive, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

ClearbitPipedriveSlack

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.

16

Nodes

14

Links

3

Run groups

Connected tools

3 integrations

  • Clearbit
  • Pipedrive
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Lead Enrichment and Notification Workflow execution lanes3 run groups containing 16 workflow nodes and 14 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.Trigger every 5 minutes. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTTrigger every 5 minutesTRIGGERSCHEDULETRIGGER0 IN / 1 OUTSetup. transform node, set. 1 incoming and 1 outgoing connections.STEP 02SetupTRANSFORMSET1 IN / 1 OUTGet all leads. integration node, pipedrive. 1 incoming and 2 outgoing connections.STEP 03Get all leadsINTEGRATIONPIPEDRIVE1 IN / 2 OUTGet organization details. integration node, pipedrive. 1 incoming and 1 outgoing connections.STEP 04Get organization detailsINTEGRATIONPIPEDRIVE1 IN / 1 OUTEnrich company. integration node, clearbit. 1 incoming and 1 outgoing connections.STEP 05Enrich companyINTEGRATIONCLEARBIT1 IN / 1 OUTAdd Organization ID to data. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Add Organization ID to dataTRANSFORMSET1 IN / 1 OUTMerge data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 07Merge dataDECISIONMERGE2 IN / 1 OUTMark lead as enriched in Pipedrive. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08Mark lead as enriched in …INTEGRATIONHTTPREQUEST1 IN / 1 OUTKeep leads that match the criteria. decision node, filter. 1 incoming and 1 outgoing connections.STEP 09Keep leads that match the…DECISIONFILTER1 IN / 1 OUTSend alert to Slack. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMESend alert to SlackSLACKSLACK1 IN / 0 OUTGet all organization keys. integration node, httpRequest. 0 incoming and 1 outgoing connections.STARTGet all organization keysINTEGRATIONHTTPREQUEST0 IN / 1 OUTSplit out organization field. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 02Split out organization fi…TRANSFORMSPLITOUT1 IN / 1 OUTShow only custom organization fields. decision node, filter. 1 incoming and 0 outgoing connections.OUTCOMEShow only custom organiza…DECISIONFILTER1 IN / 0 OUTGet all lead keys. integration node, httpRequest. 0 incoming and 1 outgoing connections.STARTGet all lead keysINTEGRATIONHTTPREQUEST0 IN / 1 OUTSplit out lead field data. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 02Split out lead field dataTRANSFORMSPLITOUT1 IN / 1 OUTShow only custom lead fields. decision node, filter. 1 incoming and 0 outgoing connections.OUTCOMEShow only custom lead fie…DECISIONFILTER1 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.16 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

Trigger every 5 minutes

10 Execution Links

  1. Start

    Trigger every 5 minutes

    Trigger

  2. Step 2

    Setup

    Transform

  3. Step 3

    Get all leads

    Integration

  4. Step 4

    Get organization details

    Integration

  5. Step 5

    Enrich company

    Integration

  6. Step 6

    Add Organization ID to data

    Transform

  7. Step 7

    Merge data

    Decision

  8. Step 8

    Mark lead as enriched in Pipedrive

    Integration

  9. Step 9

    Keep leads that match the criteria

    Decision

  10. Outcome

    Send alert to Slack

    Integration

02

Run Group

Get all organization keys

2 Execution Links

  1. Start

    Get all organization keys

    Integration

  2. Step 2

    Split out organization field

    Transform

  3. Outcome

    Show only custom organization fields

    Decision

03

Run Group

Get all lead keys

2 Execution Links

  1. Start

    Get all lead keys

    Integration

  2. Step 2

    Split out lead field data

    Transform

  3. Outcome

    Show only custom lead fields

    Decision

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