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

AI-Enhanced Telegram Scheduling Bot

AI-Enhanced Telegram Scheduling Bot is a 15-node automation blueprint connecting Telegram, Google Sheets, LangChain. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramGoogle SheetsLangChain

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.

15

Nodes

14

Links

1

Run groups

Connected tools

3 integrations

  • Telegram
  • Google Sheets
  • LangChain

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Enhanced Telegram Scheduling Bot execution lanes1 run groups containing 15 workflow nodes and 14 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.n8nInput. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTn8nInputTRIGGERCHATTRIGGER0 IN / 1 OUTtelegramInput. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTtelegramInputTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTn8nChatSettings. transform node, set. 1 incoming and 1 outgoing connections.STEP 02n8nChatSettingsTRANSFORMSET1 IN / 1 OUTSendTyping. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 02SendTypingTELEGRAMTELEGRAM1 IN / 1 OUTtelegramChatSettings. Telegram node, set. 1 incoming and 1 outgoing connections.STEP 03telegramChatSettingsTELEGRAMSET1 IN / 1 OUTSettings. transform node, set. 2 incoming and 1 outgoing connections.STEP 04SettingsTRANSFORMSET2 IN / 1 OUTSchedule. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 05ScheduleGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTScheduleToMarkdown. transform node, code. 1 incoming and 1 outgoing connections.STEP 06ScheduleToMarkdownTRANSFORMCODE1 IN / 1 OUTScheduleBot. ai node, agent. 3 incoming and 1 outgoing connections.STEP 07ScheduleBotAIAGENT3 IN / 1 OUTSetResponse. transform node, set. 1 incoming and 1 outgoing connections.STEP 08SetResponseTRANSFORMSET1 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 2 outgoing connections.STEP 09SwitchDECISIONSWITCH1 IN / 2 OUTn8nResponse. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMEn8nResponseINTEGRATIONNOOP1 IN / 0 OUTtelegramResponse. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMEtelegramResponseTELEGRAMTELEGRAM1 IN / 0 OUTLLM. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1LLMAILMCHATOPENROUTER0 IN / 1 OUTMemory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MemoryAIMEMORYBUFFERWINDOW0 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.15 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

n8nInput

12 Execution Links2 Support Dependencies

  1. Start

    n8nInput

    Trigger

    telegramInput

    Trigger

  2. Step 2

    n8nChatSettings

    Transform

    SendTyping

    Integration

  3. Step 3

    telegramChatSettings

    Transform

  4. Step 4

    Settings

    Transform

  5. Step 5

    Schedule

    Integration

  6. Step 6

    ScheduleToMarkdown

    Transform

  7. Step 7

    ScheduleBot

    AI reasoning

  8. Step 8

    SetResponse

    Transform

  9. Step 9

    Switch

    Decision

  10. Outcome

    n8nResponse

    Integration

    telegramResponse

    Integration

Attached dependencies

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

2 nodes

  • LLM

    AI reasoning dependency

  • Memory

    AI reasoning dependency

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