Actions30
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with the Telegram API via the TelePilot library, enabling automation and interaction with Telegram accounts. Specifically, the "File" resource with the "Get Remote File" operation allows users to download a remote file from Telegram by providing its unique 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 file 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 file's unique remote ID. |
Output
The node outputs an array of JSON objects corresponding to the results of the invoked Telegram API call. For the "Get Remote File" operation, the output JSON contains detailed metadata about the requested remote file, including information such as file size, path, and other Telegram-specific file attributes.
If the node supports binary data output (not explicitly shown for this operation), it would represent the actual file content downloaded from Telegram.
Dependencies
- Requires valid Telegram API credentials (API ID, API Hash, phone number) configured in n8n.
- Depends on the TelePilot library for managing Telegram client sessions and API calls.
- The node expects an active logged-in Telegram session; otherwise, it prompts for login via a separate login flow.
- No additional external services are required beyond Telegram's API.
Troubleshooting
- Not logged in error: If the Telegram session is not authenticated, the node will throw an error instructing to log in using the ChatTrigger node and follow the login guide at https://telepilot.co/login-howto.
- Session closed or terminated: Errors like "A closed client cannot be reused" indicate that the Telegram session was closed; re-login is necessary.
- Unauthorized errors: Occur if credentials are invalid or expired; re-authentication is required.
- Invalid File ID: If the provided remote file ID is incorrect or expired, the node may fail to retrieve the file.
- Network issues: Temporary connectivity problems can cause failures; retrying may help.
- Use the "Continue On Fail" option in n8n to handle errors gracefully within workflows.
Links and References
- TelePilot official documentation and login guide: https://telepilot.co/login-howto
- Telegram Bot API documentation (for general understanding): https://core.telegram.org/bots/api
- n8n documentation on credentials and node usage: https://docs.n8n.io/