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

AI-Driven Telegram Customer Support Workflow

AI-Driven Telegram Customer Support Workflow is a 30-node automation blueprint connecting Telegram, OpenAI, Redis. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramOpenAIRedis

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.

30

Nodes

28

Links

2

Run groups

Connected tools

3 integrations

  • Telegram
  • OpenAI
  • Redis

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Driven Telegram Customer Support Workflow execution lanes2 run groups containing 30 workflow nodes and 28 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 OUTGet Interaction State. integration node, redis. 1 incoming and 1 outgoing connections.STEP 02Get Interaction StateINTEGRATIONREDIS1 IN / 1 OUTSwitch Interaction. decision node, switch. 1 incoming and 3 outgoing connections.STEP 03Switch InteractionDECISIONSWITCH1 IN / 3 OUTOnboarding Agent. ai node, agent. 3 incoming and 1 outgoing connections.STEP 04Onboarding AgentAIAGENT3 IN / 1 OUTGet Canned Response. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 04Get Canned ResponseTELEGRAMTELEGRAM1 IN / 0 OUTAfter Sales Agent. ai node, agent. 4 incoming and 1 outgoing connections.STEP 04After Sales AgentAIAGENT4 IN / 1 OUTGet Onboarding Chat History. integration node, redis. 1 incoming and 1 outgoing connections.STEP 05Get Onboarding Chat HistoryINTEGRATIONREDIS1 IN / 1 OUTSend Response3. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05Send Response3TELEGRAMTELEGRAM1 IN / 0 OUTInformation Extractor. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 06Information ExtractorAIINFORMATIONEXTRACTOR2 IN / 1 OUTWith Defaults. transform node, code. 1 incoming and 1 outgoing connections.STEP 07With DefaultsTRANSFORMCODE1 IN / 1 OUTHas All Criteria?. decision node, if. 1 incoming and 2 outgoing connections.STEP 08Has All Criteria?DECISIONIF1 IN / 2 OUTHandoff Subworkflow1. integration node, executeWorkflow. 1 incoming and 1 outgoing connections.STEP 09Handoff Subworkflow1INTEGRATIONEXECUTEWORKFLOW1 IN / 1 OUTContinue Conversation. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 09Continue ConversationTELEGRAMTELEGRAM1 IN / 0 OUTSend Response. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 10Send ResponseTELEGRAMTELEGRAM1 IN / 1 OUTUpdate Agent Memory1. ai node, memoryManager. 2 incoming and 0 outgoing connections.OUTCOMEUpdate Agent Memory1AIMEMORYMANAGER2 IN / 0 OUTModel. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1ModelOPENAILMCHATOPENAI0 IN / 1 OUTMemory. ai node, memoryRedisChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MemoryAIMEMORYREDISCHAT0 IN / 1 OUTModel1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Model1OPENAILMCHATOPENAI0 IN / 1 OUTMemory1. ai node, memoryRedisChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Memory1AIMEMORYREDISCHAT0 IN / 1 OUTHandoff Tool. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Handoff ToolAITOOLWORKFLOW0 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTMemory3. ai node, memoryRedisChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Memory3AIMEMORYREDISCHAT0 IN / 1 OUTHandoff Subworkflow. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTHandoff SubworkflowTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTNotify user. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 02Notify userTELEGRAMTELEGRAM1 IN / 1 OUTSet Interaction to Human. integration node, redis. 1 incoming and 1 outgoing connections.STEP 03Set Interaction to HumanINTEGRATIONREDIS1 IN / 1 OUTHuman Handoff using Send and Wait. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 04Human Handoff using Send …TELEGRAMTELEGRAM1 IN / 1 OUTSet Interaction to Bot. integration node, redis. 1 incoming and 1 outgoing connections.STEP 05Set Interaction to BotINTEGRATIONREDIS1 IN / 1 OUTUpdate Agent Memory. ai node, memoryManager. 2 incoming and 1 outgoing connections.STEP 06Update Agent MemoryAIMEMORYMANAGER2 IN / 1 OUTSend Response2. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMESend Response2TELEGRAMTELEGRAM1 IN / 0 OUTMemory2. ai node, memoryRedisChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Memory2AIMEMORYREDISCHAT0 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.30 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

14 Execution Links7 Support Dependencies

  1. Start

    Telegram Trigger

    Trigger

  2. Step 2

    Get Interaction State

    Integration

  3. Step 3

    Switch Interaction

    Decision

  4. Step 4

    Onboarding Agent

    AI reasoning

    Get Canned Response

    Integration

    After Sales Agent

    AI reasoning

  5. Step 5

    Get Onboarding Chat History

    Integration

    Send Response3

    Integration

  6. Step 6

    Information Extractor

    AI reasoning

  7. Step 7

    With Defaults

    Transform

  8. Step 8

    Has All Criteria?

    Decision

  9. Step 9

    Handoff Subworkflow1

    Integration

    Continue Conversation

    Integration

  10. Step 10

    Send Response

    Integration

  11. Outcome

    Update Agent Memory1

    AI reasoning

Attached dependencies

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

7 nodes

  • Memory3

    AI reasoning dependency

  • Model

    AI reasoning dependency

  • Memory

    AI reasoning dependency

  • OpenAI Chat Model

    AI reasoning dependency

  • Model1

    AI reasoning dependency

  • Memory1

    AI reasoning dependency

  • Handoff Tool

    AI reasoning dependency

02

Run Group

Handoff Subworkflow

6 Execution Links1 Support Dependency

  1. Start

    Handoff Subworkflow

    Trigger

  2. Step 2

    Notify user

    Integration

  3. Step 3

    Set Interaction to Human

    Integration

  4. Step 4

    Human Handoff using Send and Wait

    Integration

  5. Step 5

    Set Interaction to Bot

    Integration

  6. Step 6

    Update Agent Memory

    AI reasoning

  7. Outcome

    Send Response2

    Integration

Attached dependencies

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

1 node

  • Memory2

    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