Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
Event-Driven AutomationAI systemIntermediate

Telegram Message Processing with AI

Telegram Message Processing with AI is a 13-node automation blueprint connecting Telegram, Supabase, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramSupabaseOpenAI

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.

13

Nodes

12

Edges

6

Zones

System stack

3 integrations

  • Telegram
  • Supabase
  • OpenAI
Telegram Message Processing with AI interactive execution graphStructural view of 13 workflow nodes and 12 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Receive Message. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.Receive MessageTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTAdd to Queued Messages. integration node, supabase. 1 incoming and 1 outgoing connections.Add to Queued MessagesINTEGRATIONSUPABASE1 IN / 1 OUTGet Queued Messages. integration node, supabase. 1 incoming and 1 outgoing connections.Get Queued MessagesINTEGRATIONSUPABASE1 IN / 1 OUTWait 10 Seconds. integration node, wait. 1 incoming and 1 outgoing connections.Wait 10 SecondsINTEGRATIONWAIT1 IN / 1 OUTSort by Message ID. integration node, sort. 1 incoming and 1 outgoing connections.Sort by Message IDINTEGRATIONSORT1 IN / 1 OUTCheck Most Recent Message. decision node, if. 1 incoming and 2 outgoing connections.Check Most Recent MessageDECISIONIF1 IN / 2 OUTNo Operation, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.No Operation, do nothingINTEGRATIONNOOP1 IN / 0 OUTDelete Queued Messages. integration node, supabase. 1 incoming and 1 outgoing connections.Delete Queued MessagesINTEGRATIONSUPABASE1 IN / 1 OUTAggregate. transform node, aggregate. 1 incoming and 1 outgoing connections.AggregateTRANSFORMAGGREGATE1 IN / 1 OUTAI Agent. ai node, agent. 3 incoming and 1 outgoing connections.AI AgentAIAGENT3 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTReply. Telegram node, telegram. 1 incoming and 0 outgoing connections.ReplyTELEGRAMTELEGRAM1 IN / 0 OUTPostgres Chat Memory. PostgreSQL node, memoryPostgresChat. 0 incoming and 1 outgoing connections.Postgres Chat MemoryPOSTGRESQLMEMORYPOSTGRESCHAT0 IN / 1 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 b56471ca548c8d93Enter 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

1 node

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

Receive Message

Trigger

02

Data & operations

6 nodes

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

Wait 10 Seconds

Integration

Add to Queued Messages

Integration

Aggregate

Transform

Delete Queued Messages

Integration

Sort by Message ID

Integration

Get Queued Messages

Integration

03

Intelligence & routing

4 nodes

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

OpenAI Chat Model

AI reasoning

Check Most Recent Message

Decision

AI Agent

AI reasoning

Postgres Chat Memory

AI reasoning

04

Terminal actions

2 nodes

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

Reply

Integration

No Operation, do nothing

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
14 / 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