OpenRuna
Sign in
← Workflows

0201_Telegram_Executecommand_Process_Webhook

21 nodes · switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile

Engine
n8n
Nodes
21
Trigger
scheduled/triggered
Source file
0201_Telegram_Executecommand_Process_Webhook.json

Workflow flow

IntegrationsSwitchTelegramHTTPSpreadsheetFileWriteBinaryFileReadBinaryFileExecuteCommandFunctionSetIFMerge
100%
/start/getweather/getweather
TRIGGER

Telegram Trigger

Telegram

Switch

Switch

Merge

Merge

Merge1

Merge

msg_pleasewait

Telegram

msg_greet

Telegram

msg_wrongcommand

Telegram

Merge2

Merge

Filename

Set

City List

Function

Get weather data

HTTP

Any errors API?

IF

Convert API response

Function

msg_errorAPI

Telegram

Spreadsheet File

SpreadsheetFile

Write csv

WriteBinaryFile

Run R script

ExecuteCommand

R successful?

IF

msg_errorR

Telegram

Read Binary File

ReadBinaryFile

msg_getweather

Telegram

21 steps · flows top to bottom, branches left to right

Browse by integration

switchtelegramhttpRequestspreadsheetFilewriteBinaryFilereadBinaryFileexecuteCommand
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

0201_Telegram_Executecommand_Process_Webhook (21-node n8n automation, switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

This n8n workflow, "0201_Telegram_Executecommand_Process_Webhook", wires together switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand in 21 nodes. 21 nodes · switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 21-node flow from scratch.
  • Benchmark it against your current switch integration to spot missing steps or redundant nodes.
  • Import "0201_Telegram_Executecommand_Process_Webhook" into n8n, reconnect credentials for switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand, and run the same automation in your own workspace.
  • Use it as a starting template when wiring switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "0201_Telegram_Executecommand_Process_Webhook" exposes 21 configured nodes. Trigger type: scheduled/triggered. Integrations: switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand. Set your credentials on the switch node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "0201_Telegram_Executecommand_Process_Webhook" JSON into a plain-English runbook, node by node. It can flag where switch rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0201_Telegram_Executecommand_Process_Webhook" — extract switch IDs and secrets into environment variables without changing the 21-node structure.

Frequently asked questions

How do I import "0201_Telegram_Executecommand_Process_Webhook" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "0201_Telegram_Executecommand_Process_Webhook" use?
It uses: switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand. The flow diagram above shows how each service connects across the 21 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own switch and telegram credentials in n8n after import.
What trigger type does "0201_Telegram_Executecommand_Process_Webhook" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "0201_Telegram_Executecommand_Process_Webhook" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for switch, telegram, httpRequest, spreadsheetFile, writeBinaryFile, readBinaryFile, executeCommand.

Related resources