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

Telegram-Gmail AI Automation Workflow

Telegram-Gmail AI Automation Workflow is a 12-node automation blueprint connecting Gmail, Telegram, Langchain AI. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailTelegramLangchain AI

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

11

Links

1

Run groups

Connected tools

3 integrations

  • Gmail
  • Telegram
  • LangChain

Canvas controls

Fit wide systems, then zoom into any run group.

Telegram-Gmail AI Automation Workflow execution lanes1 run groups containing 12 workflow nodes and 11 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.Telegram Trigger. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTTelegram TriggerTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTWhen clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTGet mails in INBOX. Gmail node, gmail. 2 incoming and 1 outgoing connections.STEP 02Get mails in INBOXGMAILGMAIL2 IN / 1 OUTFilter processed. decision node, filter. 1 incoming and 1 outgoing connections.STEP 03Filter processedDECISIONFILTER1 IN / 1 OUTCategoriser. ai node, agent. 4 incoming and 1 outgoing connections.STEP 04CategoriserAIAGENT4 IN / 1 OUTAggregate. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 05AggregateTRANSFORMAGGREGATE1 IN / 1 OUTReporter. ai node, agent. 2 incoming and 1 outgoing connections.STEP 06ReporterAIAGENT2 IN / 1 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 IN / 0 OUTOpenRouter Chat Model. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenRouter Chat ModelAILMCHATOPENROUTER0 IN / 1 OUTmail_archiver. Gmail node, gmailTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1mail_archiverGMAILGMAILTOOL0 IN / 1 OUTmail_label_setter. Gmail node, gmailTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1mail_label_setterGMAILGMAILTOOL0 IN / 1 OUTOpenRouter Chat Model1. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenRouter Chat Model1AILMCHATOPENROUTER0 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.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

Telegram Trigger

7 Execution Links4 Support Dependencies

  1. Start

    Telegram Trigger

    Trigger

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Get mails in INBOX

    Integration

  3. Step 3

    Filter processed

    Decision

  4. Step 4

    Categoriser

    AI reasoning

  5. Step 5

    Aggregate

    Transform

  6. Step 6

    Reporter

    AI reasoning

  7. Outcome

    Telegram

    Integration

Attached dependencies

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

4 nodes

  • OpenRouter Chat Model

    AI reasoning dependency

  • mail_archiver

    Integration dependency

  • mail_label_setter

    Integration dependency

  • OpenRouter Chat Model1

    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