n8n-nodes-bozonx-telegram-file-proxy
v1.1.0
Published
n8n node to encrypt Telegram file URLs for proxying through Cloudflare Worker
Readme
n8n-nodes-bozonx-telegram-file-proxy
n8n community node to encrypt Telegram file URLs for proxying through Cloudflare Worker.
Use Case
Hide Telegram Bot token in file URLs when passing audio/video/document links to third-party services.
Installation
npm install n8n-nodes-bozonx-telegram-file-proxyOr install directly in n8n:
- Go to Settings > Community Nodes
- Install:
n8n-nodes-bozonx-telegram-file-proxy
Credentials
Telegram File Proxy API
- Telegram Bot Token: Your bot token from @BotFather (e.g.,
123456:ABC-DEF...) - Worker URL: Cloudflare Worker URL (e.g.,
https://hidden-url-proxy.your-account.workers.dev) - AES Key: AES-256 key in base64 format (must match worker's
KEY_BASE64secret)
Generate key:
openssl rand -base64 32Use the output directly (no prefix needed) in both n8n credentials and worker secret.
Node: Telegram File Proxy
Parameters
- File ID: Telegram
file_idfrom message (e.g.,AgACAgIAAxkBAAIBY2...)
The node automatically calls Telegram's getFile API to get the file_path and builds the download URL.
Output
Returns JSON with single field:
{
"encryptedUrl": "https://worker-url/?q=base64(encrypted_container)"
}This URL can be passed to external services without exposing your bot token.
Example Workflow
- Telegram Trigger receives message with file → gets
file_id - Telegram File Proxy node automatically calls
getFileAPI, getsfile_path, encrypts URL - HTTP Request sends
encryptedUrlto speech-to-text service - Service fetches file via worker (token hidden)
Related
- hidden-url-proxy - Cloudflare Worker for decryption and proxying
License
MIT
