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

Telegram AI Chat with Long-Term Memory

Telegram AI Chat with Long-Term Memory is a 15-node automation blueprint connecting Telegram, OpenAI, Google Docs. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramOpenAIGoogle Docs

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.

15

Nodes

13

Links

2

Run groups

Connected tools

3 integrations

  • Telegram
  • OpenAI
  • Google Docs

Canvas controls

Fit wide systems, then zoom into any run group.

Telegram AI Chat with Long-Term Memory execution lanes2 run groups containing 15 workflow nodes and 13 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.Listen for Telegram Events. Telegram node, webhook. 0 incoming and 1 outgoing connections.STARTListen for Telegram EventsTELEGRAMWEBHOOK0 IN / 1 OUTValidation. transform node, set. 1 incoming and 1 outgoing connections.STEP 02ValidationTRANSFORMSET1 IN / 1 OUTCheck User & Chat ID. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Check User & Chat IDDECISIONIF1 IN / 2 OUTMessage Router. decision node, switch. 1 incoming and 3 outgoing connections.STEP 04Message RouterDECISIONSWITCH1 IN / 3 OUTRetrieve Long Term Memories. Google Docs node, googleDocs. 1 incoming and 1 outgoing connections.STEP 05Retrieve Long Term MemoriesGOOGLE DOCSGOOGLEDOCS1 IN / 1 OUTError message. Telegram node, telegram. 2 incoming and 0 outgoing connections.STEP 05Error messageTELEGRAMTELEGRAM2 IN / 0 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 06MergeDECISIONMERGE2 IN / 1 OUTAI Agent. ai node, agent. 3 incoming and 2 outgoing connections.STEP 07AI AgentAIAGENT3 IN / 2 OUTTelegram Response. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegram ResponseTELEGRAMTELEGRAM1 IN / 0 OUTResponse Error message. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMEResponse Error messageTELEGRAMTELEGRAM1 IN / 0 OUTSave Long Term Memories. Google Docs node, googleDocsTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Save Long Term MemoriesGOOGLE DOCSGOOGLEDOCSTOOL0 IN / 1 OUTDeepSeek-V3 Chat. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1DeepSeek-V3 ChatOPENAILMCHATOPENAI0 IN / 1 OUTWhen chat message received. trigger node, chatTrigger. 0 incoming and 0 outgoing connections.CORE RUNTIMEWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 0 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 0 outgoing connections.CORE RUNTIMEWindow Buffer MemoryAIMEMORYBUFFERWINDOW0 IN / 0 OUTDeepSeek-R1 Reasoning. OpenAI node, lmChatOpenAi. 0 incoming and 0 outgoing connections.CORE RUNTIMEDeepSeek-R1 ReasoningOPENAILMCHATOPENAI0 IN / 0 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.15 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

Listen for Telegram Events

11 Execution Links2 Support Dependencies

  1. Start

    Listen for Telegram Events

    Trigger

  2. Step 2

    Validation

    Transform

  3. Step 3

    Check User & Chat ID

    Decision

  4. Step 4

    Message Router

    Decision

  5. Step 5

    Retrieve Long Term Memories

    Integration

    Error message

    Integration

  6. Step 6

    Merge

    Decision

  7. Step 7

    AI Agent

    AI reasoning

  8. Outcome

    Telegram Response

    Integration

    Response Error message

    Integration

Attached dependencies

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

2 nodes

  • Save Long Term Memories

    Integration dependency

  • DeepSeek-V3 Chat

    AI reasoning dependency

02

Run Group

Standalone nodes

0 Execution Links

  1. Core Runtime

    When chat message received

    Trigger

    Window Buffer Memory

    AI reasoning

    DeepSeek-R1 Reasoning

    AI reasoning

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