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

Lead Management and Enrichment Workflow

Lead Management and Enrichment Workflow is a 11-node automation blueprint connecting Clearbit, Google Sheets, Leedfeeder API. Inspect its trigger, execution graph, branches, and implementation requirements.

ClearbitGoogle SheetsLeedfeeder API

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

10

Links

1

Run groups

Connected tools

3 integrations

  • Clearbit
  • Google Sheets
  • Leedfeeder API

Canvas controls

Fit wide systems, then zoom into any run group.

Lead Management and Enrichment Workflow execution lanes1 run groups containing 11 workflow nodes and 10 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.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTSetup. transform node, set. 1 incoming and 1 outgoing connections.STEP 02SetupTRANSFORMSET1 IN / 1 OUTGet all Leedfeeder accounts. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get all Leedfeeder accountsINTEGRATIONHTTPREQUEST1 IN / 1 OUTSplit out accounts. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 04Split out accountsTRANSFORMSPLITOUT1 IN / 1 OUTOnly for wanted accounts. decision node, filter. 1 incoming and 1 outgoing connections.STEP 05Only for wanted accountsDECISIONFILTER1 IN / 1 OUTGet Leads. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Get LeadsINTEGRATIONHTTPREQUEST1 IN / 1 OUTSplit Out Leads. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 07Split Out LeadsTRANSFORMSPLITOUT1 IN / 1 OUTFilter leads by engagement. decision node, filter. 1 incoming and 1 outgoing connections.STEP 08Filter leads by engagementDECISIONFILTER1 IN / 1 OUTEnrich company. integration node, clearbit. 1 incoming and 1 outgoing connections.STEP 09Enrich companyINTEGRATIONCLEARBIT1 IN / 1 OUTFilter Leads by company criteria. decision node, filter. 1 incoming and 1 outgoing connections.STEP 10Filter Leads by company c…DECISIONFILTER1 IN / 1 OUTSave leads to Google Sheets. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMESave leads to Google SheetsGOOGLE SHEETSGOOGLESHEETS1 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

Schedule Trigger

10 Execution Links

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Setup

    Transform

  3. Step 3

    Get all Leedfeeder accounts

    Integration

  4. Step 4

    Split out accounts

    Transform

  5. Step 5

    Only for wanted accounts

    Decision

  6. Step 6

    Get Leads

    Integration

  7. Step 7

    Split Out Leads

    Transform

  8. Step 8

    Filter leads by engagement

    Decision

  9. Step 9

    Enrich company

    Integration

  10. Step 10

    Filter Leads by company criteria

    Decision

  11. Outcome

    Save leads to Google Sheets

    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