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

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

8

Nodes

7

Edges

5

Zones

System stack

3 integrations

  • Hunter
  • MadKudu
  • Telegram
Lead Scoring & Notification Workflow interactive execution graphStructural view of 8 workflow nodes and 7 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.n8n Form Trigger. trigger node, formTrigger. 0 incoming and 1 outgoing connections.n8n Form TriggerTRIGGERFORMTRIGGER0 IN / 1 OUTVerify email with Hunter. integration node, hunter. 1 incoming and 1 outgoing connections.Verify email with HunterINTEGRATIONHUNTER1 IN / 1 OUTCheck if the email is valid. decision node, if. 1 incoming and 2 outgoing connections.Check if the email is validDECISIONIF1 IN / 2 OUTScore lead with MadKudu. integration node, httpRequest. 1 incoming and 1 outgoing connections.Score lead with MadKuduINTEGRATIONHTTPREQUEST1 IN / 1 OUTEmail is not valid, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.Email is not valid, do no…INTEGRATIONNOOP1 IN / 0 OUTif customer fit score > 60. decision node, if. 1 incoming and 2 outgoing connections.if customer fit score > 60DECISIONIF1 IN / 2 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.TelegramTELEGRAMTELEGRAM1 IN / 0 OUTNot interesting enough. integration node, noOp. 1 incoming and 0 outgoing connections.Not interesting enoughINTEGRATIONNOOP1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.8 connected nodesEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The workflow is grouped into operational zones, then reviewed for the controls needed to adapt the pattern safely.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

n8n Form Trigger

Trigger

02

Data & operations

2 nodes

Transformations and external-system actions that move the work forward.

Score lead with MadKudu

Integration

Verify email with Hunter

Integration

03

Intelligence & routing

2 nodes

Model calls and control points that interpret, branch, or govern the run.

Check if the email is valid

Decision

if customer fit score > 60

Decision

04

Terminal actions

3 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Email is not valid, do nothing

Integration

Not interesting enough

Integration

Telegram

Integration

Adjacent systems

Keep tracing the stack.

Related workflows share tools and similar system patterns.

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