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 retrieval of media or documents shared in Telegram chats.
- Archiving files received on Telegram into other systems or cloud storage.
- Processing downloaded files further in an automated workflow (e.g., image recognition, data extraction).
Example: A user can set up a workflow that listens for new messages containing files in a Telegram chat, then automatically downloads those files for backup or processing.
Properties
| Name | Meaning |
|---|---|
| File ID | Identifier of the file to download. This is a required string input where you specify the unique ID of the Telegram file you want to download. |
Output
The node outputs a JSON array containing the result of the download operation. The json output field includes metadata about the downloaded file as returned by the TelePilot API. This typically contains information such as file path, size, and status.
If the file content itself is handled as binary data, it would be represented in the binary output fields (not explicitly detailed here), allowing subsequent nodes to process or save the actual file content.
Dependencies
- Requires an active Telegram API authentication credential (an API key/token) configured in n8n.
- Depends on the TelePilot API client library internally to communicate with Telegram.
- The node expects a valid logged-in Telegram session; otherwise, it prompts for login via a separate login flow.
Troubleshooting
- Session Not Logged In: If the Telegram session is not authenticated, the node will throw errors instructing to log in first. Use the login commands or nodes as per the guide at https://telepilot.co/login-howto.
- Invalid File ID: Providing an incorrect or non-existent file ID will likely cause the download to fail. Verify the file ID before use.
- Session Closed or Terminated: Errors indicating a closed client require re-authentication. Restart the login process.
- Unauthorized Errors: These indicate expired or invalid credentials; re-login is necessary.
- Network issues or API rate limits may also cause failures; ensure stable connectivity and respect Telegram API usage policies.
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 on Credentials — How to configure API keys and tokens securely in n8n.