Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with Telegram via the TelePilot API, enabling various Telegram-related operations programmatically within n8n workflows. Specifically, for the File resource and Download File operation, it allows users to download a file from Telegram by specifying its unique file identifier.
Common scenarios where this node is beneficial include automating the retrieval of media or documents shared in Telegram chats, archiving files, or processing downloaded content further in an automated workflow.
For example, you could use this node to automatically download images sent to a Telegram channel and then upload them to cloud storage or analyze them with image recognition tools.
Properties
| Name | Meaning |
|---|---|
| File ID | Identifier of the file to download |
The File ID property is a required string that specifies the unique identifier of the Telegram file you want to download.
Output
The node outputs an array of JSON objects representing the downloaded file data. The exact structure depends on the TelePilot API response but generally includes metadata about the file and its contents.
If the file contains binary data (e.g., images, videos, documents), the node will provide this data in the output, allowing subsequent nodes to process or save the file.
Dependencies
- Requires an active Telegram API authentication credential (an API key and related credentials) configured in n8n.
- Depends on the TelePilot API client library internally to communicate with Telegram.
- The user must be logged in via the TelePilot session management; otherwise, the node will throw errors prompting login.
Troubleshooting
- Session Not Logged In: If the Telegram session is not authenticated, the node will throw errors indicating the need to log in. Use the login operations provided by the node to authenticate before downloading files.
- Invalid File ID: Providing an incorrect or expired file ID may result in errors or empty responses. Verify the file ID is correct and accessible.
- Session Closed or Terminated: Errors like "A closed client cannot be reused" indicate the session was closed. Re-authenticate using the login flow.
- Unauthorized Errors: These suggest invalid or expired credentials. Refresh or re-enter your Telegram API credentials.
- Network Issues: Ensure stable internet connectivity as the node communicates with Telegram servers.
Links and References
- TelePilot Login Guide — Instructions for authenticating your Telegram account.
- Telegram Bot API Documentation — General reference for Telegram API capabilities (note: TelePilot uses TDLib under the hood, which differs somewhat).
- n8n Documentation — For general help on using n8n nodes and workflows.