Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with Telegram via the TelePilot API, enabling automation and interaction with Telegram accounts. Specifically, the "File" resource with the "Get Remote File" operation allows users to download a file from Telegram's servers using its remote file identifier.
Common scenarios for this node include:
- Automating retrieval of files shared in Telegram chats or channels.
- Downloading media or documents referenced by their remote IDs for further processing or storage.
- Integrating Telegram file downloads into broader workflows, such as saving files to cloud storage or triggering other automations upon file receipt.
Example: A user receives a remote file ID from a Telegram message and uses this node to fetch the actual file data for archival or analysis.
Properties
| Name | Meaning |
|---|---|
| File ID | Identifier of the remote Telegram file to download. This is a string representing the remote file ID. |
Output
The node outputs an array of JSON objects representing the result of the requested operation. For the "Get Remote File" operation, the output JSON contains metadata and possibly content information about the downloaded remote file from Telegram.
If the node supports binary data (e.g., actual file contents), it would be included in the binary output fields, allowing subsequent nodes to process or save the file.
Dependencies
- Requires valid Telegram API credentials configured in n8n (an API key credential with necessary permissions).
- Depends on the TelePilot Node Connection Manager to handle Telegram client sessions and API calls.
- The node requires an active logged-in Telegram session; users must authenticate via phone number login flow before performing file operations.
- Network access to Telegram servers is necessary.
Troubleshooting
- Session Not Logged In: If the Telegram session is not authenticated, the node will throw errors prompting to log in first. Users should follow the login instructions at https://telepilot.co/login-howto.
- Unauthorized Errors: These indicate expired or invalid sessions. Re-login is required.
- Closed Client Errors: Occur if the Telegram client session was closed unexpectedly. The node suggests re-authentication.
- Invalid File ID: Providing an incorrect or non-existent remote file ID will likely cause the operation to fail or return empty results.
- Ensure that the "File ID" property is correctly set and corresponds to a valid remote file on Telegram.
Links and References
- TelePilot Login Guide — Instructions for authenticating Telegram sessions.
- Telegram Bot API Documentation — General reference for Telegram API concepts (note: TelePilot uses TDLib under the hood, which differs somewhat).