Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
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

Live system map / verified archive

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.

12

Nodes

11

Edges

6

Zones

System stack

3 integrations

  • Gmail
  • Telegram
  • LangChain
Telegram-Gmail AI Automation Workflow interactive execution graphStructural view of 12 workflow nodes and 11 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Telegram Trigger. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.Telegram TriggerTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTGet mails in INBOX. Gmail node, gmail. 2 incoming and 1 outgoing connections.Get mails in INBOXGMAILGMAIL2 IN / 1 OUTWhen clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.When clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTFilter processed. decision node, filter. 1 incoming and 1 outgoing connections.Filter processedDECISIONFILTER1 IN / 1 OUTCategoriser. ai node, agent. 4 incoming and 1 outgoing connections.CategoriserAIAGENT4 IN / 1 OUTOpenRouter Chat Model. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.OpenRouter Chat ModelAILMCHATOPENROUTER0 IN / 1 OUTmail_archiver. Gmail node, gmailTool. 0 incoming and 1 outgoing connections.mail_archiverGMAILGMAILTOOL0 IN / 1 OUTmail_label_setter. Gmail node, gmailTool. 0 incoming and 1 outgoing connections.mail_label_setterGMAILGMAILTOOL0 IN / 1 OUTAggregate. transform node, aggregate. 1 incoming and 1 outgoing connections.AggregateTRANSFORMAGGREGATE1 IN / 1 OUTReporter. ai node, agent. 2 incoming and 1 outgoing connections.ReporterAIAGENT2 IN / 1 OUTOpenRouter Chat Model1. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.OpenRouter Chat Model1AILMCHATOPENROUTER0 IN / 1 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.TelegramTELEGRAMTELEGRAM1 IN / 0 OUT

Signal inspector

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

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph bfeb12edb4797b1cEnter or click to lock · Escape to clear

Structured review

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

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

2 nodes

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

When clicking ‘Test workflow’

Trigger

Telegram Trigger

Trigger

02

Data & operations

4 nodes

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

mail_label_setter

Integration

mail_archiver

Integration

Aggregate

Transform

Get mails in INBOX

Integration

03

Intelligence & routing

5 nodes

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

OpenRouter Chat Model

AI reasoning

OpenRouter Chat Model1

AI reasoning

Reporter

AI reasoning

Filter processed

Decision

Categoriser

AI reasoning

04

Terminal actions

1 node

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

Telegram

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
exact
Quality score
12 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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