Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Automated Telegram Support Workflow

Automated Telegram Support Workflow is a 31-node automation blueprint connecting Telegram, Custom HTTP API, Redis. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramCustom HTTP APIRedis

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.

31

Nodes

38

Links

1

Run groups

Connected tools

3 integrations

  • Telegram
  • Custom HTTP API
  • Redis

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Telegram Support Workflow execution lanes1 run groups containing 31 workflow nodes and 38 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-Bot. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTTelegram-BotTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTBot-Config. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Bot-ConfigTRANSFORMSET1 IN / 1 OUTFormat. transform node, code. 1 incoming and 1 outgoing connections.STEP 03FormatTRANSFORMCODE1 IN / 1 OUTBot-Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Bot-FieldsTRANSFORMSET1 IN / 1 OUT1st. decision node, switch. 1 incoming and 3 outgoing connections.STEP 051stDECISIONSWITCH1 IN / 3 OUTCheck User in Database. integration node, redis. 1 incoming and 1 outgoing connections.STEP 06Check User in DatabaseINTEGRATIONREDIS1 IN / 1 OUTSupport Forum. decision node, if. 1 incoming and 1 outgoing connections.STEP 06Support ForumDECISIONIF1 IN / 1 OUTIF Verified Channel. decision node, if. 1 incoming and 2 outgoing connections.STEP 06IF Verified ChannelDECISIONIF1 IN / 2 OUTNew User ?. decision node, if. 1 incoming and 2 outgoing connections.STEP 07New User ?DECISIONIF1 IN / 2 OUTFrom Ticket. decision node, if. 1 incoming and 2 outgoing connections.STEP 07From TicketDECISIONIF1 IN / 2 OUTRetrieve all users in DB. integration node, redis. 1 incoming and 1 outgoing connections.STEP 07Retrieve all users in DBINTEGRATIONREDIS1 IN / 1 OUTSave User Data. integration node, redis. 1 incoming and 1 outgoing connections.STEP 08Save User DataINTEGRATIONREDIS1 IN / 1 OUTUpdate User Data. integration node, redis. 1 incoming and 1 outgoing connections.STEP 08Update User DataINTEGRATIONREDIS1 IN / 1 OUTForward Support Reply To User. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08Forward Support Reply To …INTEGRATIONHTTPREQUEST1 IN / 1 OUTIF Topic Created. decision node, if. 1 incoming and 1 outgoing connections.STEP 08IF Topic CreatedDECISIONIF1 IN / 1 OUTFormat Users. transform node, code. 1 incoming and 1 outgoing connections.STEP 08Format UsersTRANSFORMCODE1 IN / 1 OUTCreate Topic (Chat Ticket). integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 09Create Topic (Chat Ticket)INTEGRATIONHTTPREQUEST1 IN / 1 OUTGet User Chat Topic. integration node, redis. 1 incoming and 1 outgoing connections.STEP 09Get User Chat TopicINTEGRATIONREDIS1 IN / 1 OUTSend User Ticket Created Notification. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 09Send User Ticket Created …TELEGRAMTELEGRAM1 IN / 1 OUTFilter Blocked Users. decision node, filter. 1 incoming and 1 outgoing connections.STEP 09Filter Blocked UsersDECISIONFILTER1 IN / 1 OUTSave Topic ID. integration node, redis. 1 incoming and 1 outgoing connections.STEP 10Save Topic IDINTEGRATIONREDIS1 IN / 1 OUTForward New Message. integration node, httpRequest. 2 incoming and 2 outgoing connections.STEP 11Forward New MessageINTEGRATIONHTTPREQUEST2 IN / 2 OUTIF No Topic Created. decision node, if. 1 incoming and 2 outgoing connections.STEP 12IF No Topic CreatedDECISIONIF1 IN / 2 OUTReCreate Topic (Chat Ticket). integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 13ReCreate Topic (Chat Tick…INTEGRATIONHTTPREQUEST1 IN / 1 OUTReSave Topic ID. integration node, redis. 1 incoming and 1 outgoing connections.STEP 14ReSave Topic IDINTEGRATIONREDIS1 IN / 1 OUTForward New Message to the recrated topic. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 15Forward New Message to th…INTEGRATIONHTTPREQUEST1 IN / 1 OUTNo Operation, do nothing. integration node, noOp. 6 incoming and 0 outgoing connections.STEP 16No Operation, do nothingINTEGRATIONNOOP6 IN / 0 OUTSplit In Batches1. integration node, splitInBatches. 3 incoming and 1 outgoing connections.STEP 17Split In Batches1INTEGRATIONSPLITINBATCHES3 IN / 1 OUTBroadcast Channel Post into Users. integration node, httpRequest. 1 incoming and 2 outgoing connections.STEP 18Broadcast Channel Post in…INTEGRATIONHTTPREQUEST1 IN / 2 OUTWait1. integration node, wait. 1 incoming and 1 outgoing connections.STEP 19Wait1INTEGRATIONWAIT1 IN / 1 OUTSet Blocked Member. integration node, redis. 1 incoming and 1 outgoing connections.OUTCOMESet Blocked MemberINTEGRATIONREDIS1 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.31 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-Bot

38 Execution Links

  1. Start

    Telegram-Bot

    Trigger

  2. Step 2

    Bot-Config

    Transform

  3. Step 3

    Format

    Transform

  4. Step 4

    Bot-Fields

    Transform

  5. Step 5

    1st

    Decision

  6. Step 6

    Check User in Database

    Integration

    Support Forum

    Decision

    IF Verified Channel

    Decision

  7. Step 7

    New User ?

    Decision

    From Ticket

    Decision

    Retrieve all users in DB

    Integration

  8. Step 8

    Save User Data

    Integration

    Update User Data

    Integration

    Forward Support Reply To User

    Integration

    IF Topic Created

    Decision

    Format Users

    Transform

  9. Step 9

    Create Topic (Chat Ticket)

    Integration

    Get User Chat Topic

    Integration

    Send User Ticket Created Notification

    Integration

    Filter Blocked Users

    Decision

  10. Step 10

    Save Topic ID

    Integration

  11. Step 11

    Forward New Message

    Integration

  12. Step 12

    IF No Topic Created

    Decision

  13. Step 13

    ReCreate Topic (Chat Ticket)

    Integration

  14. Step 14

    ReSave Topic ID

    Integration

  15. Step 15

    Forward New Message to the recrated topic

    Integration

  16. Step 16

    No Operation, do nothing

    Integration

  17. Step 17

    Split In Batches1

    Integration

  18. Step 18

    Broadcast Channel Post into Users

    Integration

  19. Step 19

    Wait1

    Integration

  20. Outcome

    Set Blocked Member

    Integration

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