telegram and receive telegram events and sendphoto telegram
Configured with Execute Command, Function, HTTP Request, Read Binary File, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Routing
- Messaging
- Trigger
- Code
- Web / API
- Integration
- Files / media
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Switch | Routing | Switch | See node parameters |
| msg_greet | Messaging | Telegram | See node parameters |
| msg_wrongcommand | Messaging | Telegram | See node parameters |
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| msg_getweather | Messaging | Telegram | sendPhoto |
| City List | Code | Function | See node parameters |
| Convert API response | Code | Function | See node parameters |
| Get weather data | Web / API | HTTP Request | See node parameters |
| Spreadsheet File | Integration | Spreadsheet File | toFile |
| Write csv | Files / media | Write Binary File | See node parameters |
| Filename | Transform | Edit Fields | See node parameters |
| msg_errorAPI | Messaging | Telegram | See node parameters |
| Any errors API? | Routing | If | See node parameters |
| msg_errorR | Messaging | Telegram | See node parameters |
| Read Binary File | Files / media | Read Binary File | See node parameters |
| R successful? | Routing | If | See node parameters |
| Merge | Transform | Merge | See node parameters |
| Merge1 | Transform | Merge | See node parameters |
| msg_pleasewait | Messaging | Telegram | See node parameters |
| Merge2 | Transform | Merge | See node parameters |
| Run R script | Code | Execute Command | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
telegramApi
Workflow notes
Switch
check bot commands
telegram and receive telegram events and sendphoto telegram
telegram and receive telegram events and sendphoto telegram
Purpose and structure
This folder contains the telegram and receive telegram events and sendphoto telegram workflow. Its executable nodes use executeCommand, function, httpRequest, if, merge, readBinaryFile, set, spreadsheetFile, switch, telegram, telegramTrigger, writeBinaryFile. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Telegram Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/0201_Telegram_Executecommand_Process_Webhook.json MIT; preserve source notices.