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

Telegram Tron Wallet Blacklist Checker

Telegram Tron Wallet Blacklist Checker is a 6-node automation blueprint connecting Telegram, Tron Blacklist API. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramTron Blacklist 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.

6

Nodes

6

Links

1

Run groups

Connected tools

2 integrations

  • Telegram
  • Tron Blacklist API

Canvas controls

Fit wide systems, then zoom into any run group.

Telegram Tron Wallet Blacklist Checker execution lanes1 run groups containing 6 workflow nodes and 6 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 OUTCheck Wallet Address Format. decision node, if. 1 incoming and 2 outgoing connections.STEP 02Check Wallet Address FormatDECISIONIF1 IN / 2 OUTTron BlackList Stable Token Api Request. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Tron BlackList Stable Tok…INTEGRATIONHTTPREQUEST1 IN / 1 OUTSet Error Message (Wallet Address Format). transform node, code. 1 incoming and 1 outgoing connections.STEP 03Set Error Message (Wallet…TRANSFORMCODE1 IN / 1 OUTCheck Api Response. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Check Api ResponseTRANSFORMCODE1 IN / 1 OUTTelegram Send Message. Telegram node, telegram. 2 incoming and 0 outgoing connections.OUTCOMETelegram Send MessageTELEGRAMTELEGRAM2 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.6 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

6 Execution Links

  1. Start

    Telegram Trigger

    Trigger

  2. Step 2

    Check Wallet Address Format

    Decision

  3. Step 3

    Tron BlackList Stable Token Api Request

    Integration

    Set Error Message (Wallet Address Format)

    Transform

  4. Step 4

    Check Api Response

    Transform

  5. Outcome

    Telegram Send Message

    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