Overview
This node encrypts Telegram file URLs to proxy them through a Cloudflare Worker. It takes a Telegram file ID, fetches the file path using Telegram's getFile API, constructs the file URL, encrypts it using AES-256-CBC with a provided key, and outputs an encrypted URL that can be used to access the file securely via the proxy. This is useful for securely accessing Telegram files through a proxy service, protecting the original file URL from direct exposure.
Use Case Examples
- Encrypting Telegram file URLs for secure proxy access in automation workflows.
- Using the node to fetch and encrypt file URLs for Telegram bots or integrations that require secure file handling.
Properties
| Name | Meaning |
|---|---|
| File ID | Telegram file_id used to fetch the file path from Telegram's getFile API. |
Output
JSON
encryptedUrl- The encrypted URL for accessing the Telegram file through the Cloudflare Worker proxy.error- Error message if the node fails to process the file ID and continueOnFail is enabled.
Dependencies
- Requires credentials with botToken, workerUrl, and aesKey for Telegram API access and encryption.
Troubleshooting
- Ensure that the botToken, workerUrl, and aesKey credentials are correctly set and complete; missing or incorrect values will cause errors.
- File ID must not be empty; an empty file ID will cause the node to throw an error.
- The AES key must be exactly 32 bytes (256 bits); otherwise, the node will throw an error.
- If the Telegram getFile API call fails, check the validity of the file ID and bot token.
- If continueOnFail is enabled, errors for individual items will be output as error messages in the JSON output rather than stopping execution.
Links
- Telegram File Proxy Node Documentation - Official documentation for the Telegram File Proxy n8n node.