Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
Event-Driven AutomationAI systemIntermediate

Telegram AI Schedule Bot

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

TelegramGoogle SheetsLangchain AI

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

15

Nodes

14

Edges

6

Zones

System stack

3 integrations

  • Telegram
  • Google Sheets
  • LangChain
Telegram AI Schedule Bot interactive execution graphStructural view of 15 workflow nodes and 14 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.n8nInput. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.n8nInputTRIGGERCHATTRIGGER0 IN / 1 OUTn8nChatSettings. transform node, set. 1 incoming and 1 outgoing connections.n8nChatSettingsTRANSFORMSET1 IN / 1 OUTtelegramInput. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.telegramInputTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTSendTyping. Telegram node, telegram. 1 incoming and 1 outgoing connections.SendTypingTELEGRAMTELEGRAM1 IN / 1 OUTtelegramChatSettings. Telegram node, set. 1 incoming and 1 outgoing connections.telegramChatSettingsTELEGRAMSET1 IN / 1 OUTSettings. transform node, set. 2 incoming and 1 outgoing connections.SettingsTRANSFORMSET2 IN / 1 OUTSchedule. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.ScheduleGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTScheduleToMarkdown. transform node, code. 1 incoming and 1 outgoing connections.ScheduleToMarkdownTRANSFORMCODE1 IN / 1 OUTScheduleBot. ai node, agent. 3 incoming and 1 outgoing connections.ScheduleBotAIAGENT3 IN / 1 OUTLLM. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.LLMAILMCHATOPENROUTER0 IN / 1 OUTMemory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTSetResponse. transform node, set. 1 incoming and 1 outgoing connections.SetResponseTRANSFORMSET1 IN / 1 OUTn8nResponse. integration node, noOp. 1 incoming and 0 outgoing connections.n8nResponseINTEGRATIONNOOP1 IN / 0 OUTSwitch. decision node, switch. 1 incoming and 2 outgoing connections.SwitchDECISIONSWITCH1 IN / 2 OUTtelegramResponse. Telegram node, telegram. 1 incoming and 0 outgoing connections.telegramResponseTELEGRAMTELEGRAM1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph edc0ce6888058c63Enter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

2 nodes

Events, schedules, and unconnected roots that can start an execution.

telegramInput

Trigger

n8nInput

Trigger

02

Data & operations

7 nodes

Transformations and external-system actions that move the work forward.

SendTyping

Integration

SetResponse

Transform

Settings

Transform

Schedule

Integration

ScheduleToMarkdown

Transform

n8nChatSettings

Transform

+ 1 more in system map
03

Intelligence & routing

4 nodes

Model calls and control points that interpret, branch, or govern the run.

ScheduleBot

AI reasoning

Switch

Decision

LLM

AI reasoning

Memory

AI reasoning

04

Terminal actions

2 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

telegramResponse

Integration

n8nResponse

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
prefix
Quality score
13 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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