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

Telegram Workflow Automation

Telegram Workflow Automation is a 21-node automation blueprint connecting Telegram, Google Sheets. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramGoogle Sheets

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.

21

Nodes

20

Links

1

Run groups

Connected tools

2 integrations

  • Telegram
  • Google Sheets

Canvas controls

Fit wide systems, then zoom into any run group.

Telegram Workflow Automation execution lanes1 run groups containing 21 workflow nodes and 20 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.Trigger. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTTriggerTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTGlobal data. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Global dataTRANSFORMSET1 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 4 outgoing connections.STEP 03SwitchDECISIONSWITCH1 IN / 4 OUTSwitch_MessageType. decision node, switch. 1 incoming and 4 outgoing connections.STEP 04Switch_MessageTypeDECISIONSWITCH1 IN / 4 OUTTelegram3. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 04Telegram3TELEGRAMTELEGRAM1 IN / 1 OUTStart bot?. decision node, if. 1 incoming and 2 outgoing connections.STEP 04Start bot?DECISIONIF1 IN / 2 OUTTrigger Data for Payment. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Trigger Data for PaymentTRANSFORMSET1 IN / 1 OUTCommand?. decision node, if. 1 incoming and 2 outgoing connections.STEP 05Command?DECISIONIF1 IN / 2 OUTTelegram1. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05Telegram1TELEGRAMTELEGRAM1 IN / 0 OUTTelegram2. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05Telegram2TELEGRAMTELEGRAM1 IN / 0 OUTTelegram5. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05Telegram5TELEGRAMTELEGRAM1 IN / 0 OUTMenu. decision node, switch. 1 incoming and 0 outgoing connections.STEP 05MenuDECISIONSWITCH1 IN / 0 OUTTrigger Data for Register. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Trigger Data for RegisterTRANSFORMSET1 IN / 1 OUTChange status. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.STEP 05Change statusGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTPayment Handler. integration node, executeWorkflow. 1 incoming and 0 outgoing connections.STEP 05Payment HandlerINTEGRATIONEXECUTEWORKFLOW1 IN / 0 OUTSwitch_Commands. decision node, switch. 1 incoming and 2 outgoing connections.STEP 06Switch_CommandsDECISIONSWITCH1 IN / 2 OUTTelegram4. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 06Telegram4TELEGRAMTELEGRAM1 IN / 0 OUTRegister. integration node, executeWorkflow. 1 incoming and 0 outgoing connections.STEP 06RegisterINTEGRATIONEXECUTEWORKFLOW1 IN / 0 OUTData for Invoice. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Data for InvoiceTRANSFORMSET1 IN / 1 OUTTelegram6. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 07Telegram6TELEGRAMTELEGRAM1 IN / 0 OUTSend Invoice. integration node, executeWorkflow. 1 incoming and 0 outgoing connections.OUTCOMESend InvoiceINTEGRATIONEXECUTEWORKFLOW1 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.21 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

Trigger

20 Execution Links

  1. Start

    Trigger

    Trigger

  2. Step 2

    Global data

    Transform

  3. Step 3

    Switch

    Decision

  4. Step 4

    Switch_MessageType

    Decision

    Telegram3

    Integration

    Start bot?

    Decision

    Trigger Data for Payment

    Transform

  5. Step 5

    Command?

    Decision

    Telegram1

    Integration

    Telegram2

    Integration

    Telegram5

    Integration

    Menu

    Decision

    Trigger Data for Register

    Transform

    Change status

    Integration

    Payment Handler

    Integration

  6. Step 6

    Switch_Commands

    Decision

    Telegram4

    Integration

    Register

    Integration

  7. Step 7

    Data for Invoice

    Transform

    Telegram6

    Integration

  8. Outcome

    Send Invoice

    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