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

Telegram AI Chatbot with Semantic RAG

Telegram AI Chatbot with Semantic RAG is a 16-node automation blueprint connecting Telegram, OpenAI, Postgres PGVector. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramOpenAIPostgres PGVectorLangChain

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.

16

Nodes

16

Edges

6

Zones

System stack

4 integrations

  • Telegram
  • OpenAI
  • PostgreSQL
  • LangChain
Telegram AI Chatbot with Semantic RAG interactive execution graphStructural view of 16 workflow nodes and 16 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 OUTGenerate session id. transform node, set. 2 incoming and 1 outgoing connections.Generate session idTRANSFORMSET2 IN / 1 OUTWhen chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.When chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTAI Agent. ai node, agent. 5 incoming and 1 outgoing connections.AI AgentAIAGENT5 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTSimple Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.Simple MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTPostgres PGVector Store. PostgreSQL node, vectorStorePGVector. 1 incoming and 1 outgoing connections.Postgres PGVector StorePOSTGRESQLVECTORSTOREPGVECTOR1 IN / 1 OUTCall the SQL composer Workflow. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.Call the SQL composer Wor…AITOOLWORKFLOW0 IN / 1 OUTEmbeddings Ollama. ai node, embeddingsOllama. 0 incoming and 1 outgoing connections.Embeddings OllamaAIEMBEDDINGSOLLAMA0 IN / 1 OUTCame from Telegram?. Telegram node, if. 1 incoming and 2 outgoing connections.Came from Telegram?TELEGRAMIF1 IN / 2 OUTSplit text into chunks. transform node, code. 1 incoming and 1 outgoing connections.Split text into chunksTRANSFORMCODE1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 2 outgoing connections.Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 2 OUTBeautify chat response. transform node, set. 1 incoming and 0 outgoing connections.Beautify chat responseTRANSFORMSET1 IN / 0 OUTNo Operation, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.No Operation, do nothingINTEGRATIONNOOP1 IN / 0 OUTEscape Markdown. transform node, code. 1 incoming and 1 outgoing connections.Escape MarkdownTRANSFORMCODE1 IN / 1 OUTRespond on Telegram in batches. Telegram node, telegram. 1 incoming and 1 outgoing connections.Respond on Telegram in ba…TELEGRAMTELEGRAM1 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 a8c98b2aa32a78a8Enter 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.

Telegram Trigger

Trigger

When chat message received

Trigger

02

Data & operations

5 nodes

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

Loop Over Items

Integration

Split text into chunks

Transform

Respond on Telegram in batches

Integration

Escape Markdown

Transform

Generate session id

Transform

03

Intelligence & routing

7 nodes

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

Came from Telegram?

Decision

Postgres PGVector Store

AI reasoning

Call the SQL composer Workflow

AI reasoning

Embeddings Ollama

AI reasoning

Simple Memory

AI reasoning

AI Agent

AI reasoning

+ 1 more in system map
04

Terminal actions

2 nodes

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

Beautify chat response

Transform

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
prefix
Quality score
13 / 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