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

WeatherBot Automation Workflow

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

TelegramWeather API

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

21

Links

1

Run groups

Connected tools

2 integrations

  • Telegram
  • Weather API

Canvas controls

Fit wide systems, then zoom into any run group.

WeatherBot Automation Workflow execution lanes1 run groups containing 21 workflow nodes and 21 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 OUTSwitch. decision node, switch. 1 incoming and 4 outgoing connections.STEP 02SwitchDECISIONSWITCH1 IN / 4 OUTMerge1. decision node, merge. 1 incoming and 1 outgoing connections.STEP 03Merge1DECISIONMERGE1 IN / 1 OUTmsg_pleasewait. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 03msg_pleasewaitTELEGRAMTELEGRAM1 IN / 1 OUTMerge. decision node, merge. 1 incoming and 1 outgoing connections.STEP 03MergeDECISIONMERGE1 IN / 1 OUTmsg_greet. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 04msg_greetTELEGRAMTELEGRAM1 IN / 0 OUTMerge2. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04Merge2DECISIONMERGE2 IN / 1 OUTmsg_wrongcommand. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 04msg_wrongcommandTELEGRAMTELEGRAM1 IN / 0 OUTFilename. transform node, set. 1 incoming and 1 outgoing connections.STEP 05FilenameTRANSFORMSET1 IN / 1 OUTCity List. transform node, function. 1 incoming and 1 outgoing connections.STEP 06City ListTRANSFORMFUNCTION1 IN / 1 OUTGet weather data. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Get weather dataINTEGRATIONHTTPREQUEST1 IN / 1 OUTAny errors API?. decision node, if. 1 incoming and 2 outgoing connections.STEP 08Any errors API?DECISIONIF1 IN / 2 OUTmsg_errorAPI. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 09msg_errorAPITELEGRAMTELEGRAM1 IN / 0 OUTConvert API response. transform node, function. 1 incoming and 1 outgoing connections.STEP 09Convert API responseTRANSFORMFUNCTION1 IN / 1 OUTSpreadsheet File. integration node, spreadsheetFile. 1 incoming and 1 outgoing connections.STEP 10Spreadsheet FileINTEGRATIONSPREADSHEETFILE1 IN / 1 OUTWrite csv. integration node, writeBinaryFile. 1 incoming and 1 outgoing connections.STEP 11Write csvINTEGRATIONWRITEBINARYFILE1 IN / 1 OUTRun R script. integration node, executeCommand. 1 incoming and 1 outgoing connections.STEP 12Run R scriptINTEGRATIONEXECUTECOMMAND1 IN / 1 OUTR successful?. decision node, if. 1 incoming and 2 outgoing connections.STEP 13R successful?DECISIONIF1 IN / 2 OUTRead Binary File. integration node, readBinaryFile. 1 incoming and 1 outgoing connections.STEP 14Read Binary FileINTEGRATIONREADBINARYFILE1 IN / 1 OUTmsg_errorR. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 14msg_errorRTELEGRAMTELEGRAM1 IN / 0 OUTmsg_getweather. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMEmsg_getweatherTELEGRAMTELEGRAM1 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

Telegram Trigger

21 Execution Links

  1. Start

    Telegram Trigger

    Trigger

  2. Step 2

    Switch

    Decision

  3. Step 3

    Merge1

    Decision

    msg_pleasewait

    Integration

    Merge

    Decision

  4. Step 4

    msg_greet

    Integration

    Merge2

    Decision

    msg_wrongcommand

    Integration

  5. Step 5

    Filename

    Transform

  6. Step 6

    City List

    Transform

  7. Step 7

    Get weather data

    Integration

  8. Step 8

    Any errors API?

    Decision

  9. Step 9

    msg_errorAPI

    Integration

    Convert API response

    Transform

  10. Step 10

    Spreadsheet File

    Integration

  11. Step 11

    Write csv

    Integration

  12. Step 12

    Run R script

    Integration

  13. Step 13

    R successful?

    Decision

  14. Step 14

    Read Binary File

    Integration

    msg_errorR

    Integration

  15. Outcome

    msg_getweather

    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