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

Email Automation and Classification Workflow

Email Automation and Classification Workflow is a 11-node automation blueprint connecting Gmail, LangChain, SendInBlue. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailLangChainSendInBlue

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

12

Links

1

Run groups

Connected tools

3 integrations

  • Gmail
  • LangChain
  • SendInBlue

Canvas controls

Fit wide systems, then zoom into any run group.

Email Automation and Classification Workflow execution lanes1 run groups containing 11 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.Gmail Trigger. Gmail node, gmailTrigger. 0 incoming and 1 outgoing connections.STARTGmail TriggerGMAILGMAILTRIGGER0 IN / 1 OUTEmails from Existing Contracts. decision node, if. 1 incoming and 1 outgoing connections.STEP 02Emails from Existing Cont…DECISIONIF1 IN / 1 OUTReply. decision node, if. 1 incoming and 1 outgoing connections.STEP 03ReplyDECISIONIF1 IN / 1 OUTText Classifier. ai node, textClassifier. 2 incoming and 3 outgoing connections.STEP 04Text ClassifierAITEXTCLASSIFIER2 IN / 3 OUTGuestPost Inquiry. integration node, emailSend. 1 incoming and 1 outgoing connections.STEP 05GuestPost InquiryINTEGRATIONEMAILSEND1 IN / 1 OUTYoutube Video Inquiry. integration node, emailSend. 1 incoming and 1 outgoing connections.STEP 05Youtube Video InquiryINTEGRATIONEMAILSEND1 IN / 1 OUTSend Email. integration node, emailSend. 1 incoming and 1 outgoing connections.STEP 05Send EmailINTEGRATIONEMAILSEND1 IN / 1 OUTMark as Read. Gmail node, gmail. 3 incoming and 2 outgoing connections.STEP 06Mark as ReadGMAILGMAIL3 IN / 2 OUTCreate Contact in Brevo. integration node, sendInBlue. 1 incoming and 0 outgoing connections.OUTCOMECreate Contact in BrevoINTEGRATIONSENDINBLUE1 IN / 0 OUTApply Label. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMEApply LabelGMAILGMAIL1 IN / 0 OUTGoogle Gemini Chat Model. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat ModelGOOGLE AILMCHATGOOGLEGEMINI0 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.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

Gmail Trigger

11 Execution Links1 Support Dependency

  1. Start

    Gmail Trigger

    Trigger

  2. Step 2

    Emails from Existing Contracts

    Decision

  3. Step 3

    Reply

    Decision

  4. Step 4

    Text Classifier

    AI reasoning

  5. Step 5

    GuestPost Inquiry

    Integration

    Youtube Video Inquiry

    Integration

    Send Email

    Integration

  6. Step 6

    Mark as Read

    Integration

  7. Outcome

    Create Contact in Brevo

    Integration

    Apply Label

    Integration

Attached dependencies

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

1 node

  • Google Gemini Chat Model

    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