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

Lead Scoring & Notification Workflow

Lead Scoring & Notification Workflow is a 8-node automation blueprint connecting Hunter, MadKudu, Telegram. Inspect its trigger, execution graph, branches, and implementation requirements.

HunterMadKuduTelegram

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.

8

Nodes

7

Links

1

Run groups

Connected tools

3 integrations

  • Hunter
  • MadKudu
  • Telegram

Canvas controls

Fit wide systems, then zoom into any run group.

Lead Scoring & Notification Workflow execution lanes1 run groups containing 8 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.n8n Form Trigger. trigger node, formTrigger. 0 incoming and 1 outgoing connections.STARTn8n Form TriggerTRIGGERFORMTRIGGER0 IN / 1 OUTVerify email with Hunter. integration node, hunter. 1 incoming and 1 outgoing connections.STEP 02Verify email with HunterINTEGRATIONHUNTER1 IN / 1 OUTCheck if the email is valid. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Check if the email is validDECISIONIF1 IN / 2 OUTScore lead with MadKudu. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Score lead with MadKuduINTEGRATIONHTTPREQUEST1 IN / 1 OUTEmail is not valid, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 04Email is not valid, do no…INTEGRATIONNOOP1 IN / 0 OUTif customer fit score > 60. decision node, if. 1 incoming and 2 outgoing connections.STEP 05if customer fit score > 60DECISIONIF1 IN / 2 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 IN / 0 OUTNot interesting enough. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMENot interesting enoughINTEGRATIONNOOP1 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.8 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

n8n Form Trigger

7 Execution Links

  1. Start

    n8n Form Trigger

    Trigger

  2. Step 2

    Verify email with Hunter

    Integration

  3. Step 3

    Check if the email is valid

    Decision

  4. Step 4

    Score lead with MadKudu

    Integration

    Email is not valid, do nothing

    Integration

  5. Step 5

    if customer fit score > 60

    Decision

  6. Outcome

    Telegram

    Integration

    Not interesting enough

    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