Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Lead Management and Notification Workflow

Lead Management and Notification Workflow is a 12-node automation blueprint connecting Lemlist, HubSpot, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

LemlistHubSpotSlackOpenAI

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.

12

Nodes

12

Links

1

Run groups

Connected tools

4 integrations

  • Lemlist
  • HubSpot
  • Slack
  • OpenAI

Canvas controls

Fit wide systems, then zoom into any run group.

Lead Management and Notification Workflow execution lanes1 run groups containing 12 workflow nodes and 12 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.Lemlist - Lead Replied. trigger node, lemlistTrigger. 0 incoming and 2 outgoing connections.STARTLemlist - Lead RepliedTRIGGERLEMLISTTRIGGER0 IN / 2 OUTOpenAI. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 02OpenAIOPENAIOPENAI1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 03MergeDECISIONMERGE2 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 5 outgoing connections.STEP 04SwitchDECISIONSWITCH1 IN / 5 OUTLemlist - Unsubscribe. integration node, lemlist. 1 incoming and 0 outgoing connections.STEP 05Lemlist - UnsubscribeINTEGRATIONLEMLIST1 IN / 0 OUTlemlist - Mark as interested. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 05lemlist - Mark as interes…INTEGRATIONHTTPREQUEST1 IN / 0 OUTHubSpot - Get contact ID. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 05HubSpot - Get contact IDHUBSPOTHUBSPOT1 IN / 1 OUTHubSpot - Get contact ID1. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 05HubSpot - Get contact ID1HUBSPOTHUBSPOT1 IN / 1 OUTSlack1. Slack node, slack. 1 incoming and 0 outgoing connections.STEP 05Slack1SLACKSLACK1 IN / 0 OUTHubSpot - Create Deal. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 06HubSpot - Create DealHUBSPOTHUBSPOT1 IN / 1 OUTfollow up task. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.STEP 06follow up taskHUBSPOTHUBSPOT1 IN / 0 OUTSlack. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMESlackSLACKSLACK1 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.12 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

Lemlist - Lead Replied

12 Execution Links

  1. Start

    Lemlist - Lead Replied

    Trigger

  2. Step 2

    OpenAI

    AI reasoning

  3. Step 3

    Merge

    Decision

  4. Step 4

    Switch

    Decision

  5. Step 5

    Lemlist - Unsubscribe

    Integration

    lemlist - Mark as interested

    Integration

    HubSpot - Get contact ID

    Integration

    HubSpot - Get contact ID1

    Integration

    Slack1

    Integration

  6. Step 6

    HubSpot - Create Deal

    Integration

    follow up task

    Integration

  7. Outcome

    Slack

    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