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

Lemlist Reply Automation & Categorization

Lemlist Reply Automation & Categorization is a 10-node automation blueprint connecting Lemlist, OpenAI, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

LemlistOpenAISlack

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.

10

Nodes

10

Links

1

Run groups

Connected tools

3 integrations

  • Lemlist
  • OpenAI
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Lemlist Reply Automation & Categorization execution lanes1 run groups containing 10 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.Lemlist Trigger - On new reply. trigger node, lemlistTrigger. 0 incoming and 1 outgoing connections.STARTLemlist Trigger - On new …TRIGGERLEMLISTTRIGGER0 IN / 1 OUTFormat text with Markdown. integration node, markdown. 1 incoming and 2 outgoing connections.STEP 02Format text with MarkdownINTEGRATIONMARKDOWN1 IN / 2 OUTCategorize lemlist reply. ai node, chainLlm. 3 incoming and 1 outgoing connections.STEP 03Categorize lemlist replyAICHAINLLM3 IN / 1 OUTMerge data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04Merge dataDECISIONMERGE2 IN / 1 OUTRoute reply to the right branch. decision node, switch. 1 incoming and 3 outgoing connections.STEP 05Route reply to the right …DECISIONSWITCH1 IN / 3 OUTSend alert to Slack. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMESend alert to SlackSLACKSLACK1 IN / 0 OUTLemlist - Unsubscribe. integration node, lemlist. 1 incoming and 0 outgoing connections.OUTCOMELemlist - UnsubscribeINTEGRATIONLEMLIST1 IN / 0 OUTlemlist - Mark as interested. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMElemlist - Mark as interes…INTEGRATIONHTTPREQUEST1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 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.10 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 Trigger - On new reply

8 Execution Links2 Support Dependencies

  1. Start

    Lemlist Trigger - On new reply

    Trigger

  2. Step 2

    Format text with Markdown

    Integration

  3. Step 3

    Categorize lemlist reply

    AI reasoning

  4. Step 4

    Merge data

    Decision

  5. Step 5

    Route reply to the right branch

    Decision

  6. Outcome

    Send alert to Slack

    Integration

    Lemlist - Unsubscribe

    Integration

    lemlist - Mark as interested

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

2 nodes

  • OpenAI Chat Model

    AI reasoning dependency

  • Structured Output Parser

    AI reasoning dependency

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