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

AI-Driven Telegram Financial Analysis Bot

AI-Driven Telegram Financial Analysis Bot is a 24-node automation blueprint connecting Telegram, OpenAI, Airtable. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramOpenAIAirtable

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.

24

Nodes

23

Links

3

Run groups

Connected tools

3 integrations

  • Telegram
  • OpenAI
  • Airtable

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Driven Telegram Financial Analysis Bot execution lanes3 run groups containing 24 workflow nodes and 23 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.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTTelegram Trigger. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTTelegram TriggerTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTSet Text1. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set Text1TRANSFORMSET1 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 2 outgoing connections.STEP 02SwitchDECISIONSWITCH1 IN / 2 OUTDownload File. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 03Download FileTELEGRAMTELEGRAM1 IN / 1 OUTSet Text. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Set TextTRANSFORMSET1 IN / 1 OUTTranscribe. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 04TranscribeOPENAIOPENAI1 IN / 1 OUTAI Agent. ai node, agent. 7 incoming and 1 outgoing connections.STEP 05AI AgentAIAGENT7 IN / 1 OUTSend Analysis. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMESend AnalysisTELEGRAMTELEGRAM1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Window Buffer MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTSave Ticker. Airtable node, airtableTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Save TickerAIRTABLEAIRTABLETOOL0 IN / 1 OUTGet Chart. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Get ChartAITOOLWORKFLOW0 IN / 1 OUTWorkflow Input Trigger. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTWorkflow Input TriggerTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTSet Values. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set ValuesTRANSFORMSET1 IN / 1 OUTGet Chart URL. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get Chart URLINTEGRATIONHTTPREQUEST1 IN / 1 OUTDownload Chart. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Download ChartINTEGRATIONHTTPREQUEST1 IN / 1 OUTTechnical Analysis. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 05Technical AnalysisOPENAIOPENAI1 IN / 1 OUTSend Chart. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 06Send ChartTELEGRAMTELEGRAM1 IN / 1 OUTresponse. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEresponseTRANSFORMSET1 IN / 0 OUTSchedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet tokens. Airtable node, airtable. 1 incoming and 1 outgoing connections.STEP 02Get tokensAIRTABLEAIRTABLE1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 03Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTRun Agent. integration node, httpRequest. 1 incoming and 1 outgoing connections.OUTCOMERun AgentINTEGRATIONHTTPREQUEST1 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.24 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

Webhook

9 Execution Links4 Support Dependencies

  1. Start

    Webhook

    Trigger

    Telegram Trigger

    Trigger

  2. Step 2

    Set Text1

    Transform

    Switch

    Decision

  3. Step 3

    Download File

    Integration

    Set Text

    Transform

  4. Step 4

    Transcribe

    AI reasoning

  5. Step 5

    AI Agent

    AI reasoning

  6. Outcome

    Send Analysis

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

4 nodes

  • OpenAI Chat Model

    AI reasoning dependency

  • Window Buffer Memory

    AI reasoning dependency

  • Save Ticker

    Integration dependency

  • Get Chart

    AI reasoning dependency

02

Run Group

Workflow Input Trigger

6 Execution Links

  1. Start

    Workflow Input Trigger

    Trigger

  2. Step 2

    Set Values

    Transform

  3. Step 3

    Get Chart URL

    Integration

  4. Step 4

    Download Chart

    Integration

  5. Step 5

    Technical Analysis

    AI reasoning

  6. Step 6

    Send Chart

    Integration

  7. Outcome

    response

    Transform

03

Run Group

Schedule Trigger

4 Execution Links

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Get tokens

    Integration

  3. Step 3

    Loop Over Items

    Integration

  4. Outcome

    Run Agent

    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