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

Telegram Workflow for Shipment and GPS Management

Telegram Workflow for Shipment and GPS Management is a 32-node automation blueprint connecting Telegram, Google Drive, Google Sheets. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramGoogle DriveGoogle SheetsGmail

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.

32

Nodes

30

Links

2

Run groups

Connected tools

4 integrations

  • Telegram
  • Google Drive
  • Google Sheets
  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

Telegram Workflow for Shipment and GPS Management execution lanes2 run groups containing 32 workflow nodes and 30 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.Initiate Workflow Data. transform node, code. 0 incoming and 0 outgoing connections.CORE RUNTIMEInitiate Workflow DataTRANSFORMCODE0 IN / 0 OUTTelegram Trigger. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTTelegram TriggerTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTCommand?. decision node, if. 1 incoming and 2 outgoing connections.STEP 02Command?DECISIONIF1 IN / 2 OUTSwitch Command. decision node, switch. 1 incoming and 5 outgoing connections.STEP 03Switch CommandDECISIONSWITCH1 IN / 5 OUTWaiting Conditions. transform node, code. 1 incoming and 1 outgoing connections.STEP 03Waiting ConditionsTRANSFORMCODE1 IN / 1 OUTwaitingShipmentNumber. transform node, code. 1 incoming and 1 outgoing connections.STEP 04waitingShipmentNumberTRANSFORMCODE1 IN / 1 OUTwaitingGPS. transform node, code. 1 incoming and 1 outgoing connections.STEP 04waitingGPSTRANSFORMCODE1 IN / 1 OUTwaitingPhoto. transform node, code. 1 incoming and 1 outgoing connections.STEP 04waitingPhotoTRANSFORMCODE1 IN / 1 OUTLoad Workspace Data. transform node, code. 1 incoming and 3 outgoing connections.STEP 04Load Workspace DataTRANSFORMCODE1 IN / 3 OUTWelcome Message. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 04Welcome MessageTELEGRAMTELEGRAM1 IN / 0 OUTCheck State. decision node, switch. 1 incoming and 4 outgoing connections.STEP 04Check StateDECISIONSWITCH1 IN / 4 OUTaddShipmentNumber. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05addShipmentNumberTELEGRAMTELEGRAM1 IN / 0 OUTaddGPS. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05addGPSTELEGRAMTELEGRAM1 IN / 0 OUTsendPhoto. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05sendPhotoTELEGRAMTELEGRAM1 IN / 0 OUTLoad Delivery Information. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.STEP 05Load Delivery InformationGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTDistribution Team Confirmation. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 05Distribution Team Confirm…GMAILGMAIL1 IN / 1 OUTConfirmation Driver. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05Confirmation DriverTELEGRAMTELEGRAM1 IN / 0 OUTShipment Number. transform node, set. 1 incoming and 2 outgoing connections.STEP 05Shipment NumberTRANSFORMSET1 IN / 2 OUTStore GPS Location. transform node, set. 1 incoming and 2 outgoing connections.STEP 05Store GPS LocationTRANSFORMSET1 IN / 2 OUTGet Picture. Telegram node, telegram. 1 incoming and 2 outgoing connections.STEP 05Get PictureTELEGRAMTELEGRAM1 IN / 2 OUTInstructions. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 05InstructionsTELEGRAMTELEGRAM1 IN / 0 OUTClear State. transform node, code. 1 incoming and 0 outgoing connections.STEP 06Clear StateTRANSFORMCODE1 IN / 0 OUTStore Shipment. transform node, code. 1 incoming and 0 outgoing connections.STEP 06Store ShipmentTRANSFORMCODE1 IN / 0 OUTaddShipmentNumber result. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 06addShipmentNumber resultTELEGRAMTELEGRAM1 IN / 0 OUTStore GPS. transform node, code. 1 incoming and 0 outgoing connections.STEP 06Store GPSTRANSFORMCODE1 IN / 0 OUTaddGPS result. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 06addGPS resultTELEGRAMTELEGRAM1 IN / 0 OUTUpload Picture. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 06Upload PictureGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTExtract FileName. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Extract FileNameTRANSFORMSET1 IN / 1 OUTShare Picture. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 07Share PictureGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTStore fileName. transform node, code. 1 incoming and 0 outgoing connections.STEP 07Store fileNameTRANSFORMCODE1 IN / 0 OUTSave Public Image Link. transform node, code. 1 incoming and 1 outgoing connections.STEP 08Save Public Image LinkTRANSFORMCODE1 IN / 1 OUTaddPhoto result. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMEaddPhoto resultTELEGRAMTELEGRAM1 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.32 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

Initiate Workflow Data

0 Execution Links

  1. Core Runtime

    Initiate Workflow Data

    Transform

02

Run Group

Telegram Trigger

30 Execution Links

  1. Start

    Telegram Trigger

    Trigger

  2. Step 2

    Command?

    Decision

  3. Step 3

    Switch Command

    Decision

    Waiting Conditions

    Transform

  4. Step 4

    waitingShipmentNumber

    Transform

    waitingGPS

    Transform

    waitingPhoto

    Transform

    Load Workspace Data

    Transform

    Welcome Message

    Integration

    Check State

    Decision

  5. Step 5

    addShipmentNumber

    Integration

    addGPS

    Integration

    sendPhoto

    Integration

    Load Delivery Information

    Integration

    Distribution Team Confirmation

    Integration

    Confirmation Driver

    Integration

    Shipment Number

    Transform

    Store GPS Location

    Transform

    Get Picture

    Integration

    Instructions

    Integration

  6. Step 6

    Clear State

    Transform

    Store Shipment

    Transform

    addShipmentNumber result

    Integration

    Store GPS

    Transform

    addGPS result

    Integration

    Upload Picture

    Integration

    Extract FileName

    Transform

  7. Step 7

    Share Picture

    Integration

    Store fileName

    Transform

  8. Step 8

    Save Public Image Link

    Transform

  9. Outcome

    addPhoto result

    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