Deliver Documents to Telegram from External Systems
When external tools or custom backends need to share documents, use a Notis webhook to push them directly to Telegram without manual handoffs.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Document
Sends a file to a Telegram chat; URL-based documents must be PDF or ZIP.
Why this helps
Your third-party tools or custom scripts need to notify your team, but they can't access Box or Telegram directly. Manual forwarding is error-prone.
- Bridge gaps between proprietary tools and Telegram
- Automate document sharing without manual copying
- Keep Telegram as your single notification hub
Setup
Build it in a few focused steps.
- 1Connect Telegram to Notis (one-time, via portal).
- 2Create an automation with: 'When a Notis webhook receives a request, send the attached or linked document to Telegram.'
- 3Select 'notis_webhook' as the trigger type.
- 4Configure Telegram as the destination.
- 5Notis will provide a webhook URL. Use that URL in your external system to trigger the automation with a POST request containing the document URL or attachment.
Questions about this workflow
What format should the webhook payload be?
Notis can accept JSON payloads with document URLs or file content. Specify the format when setting up the automation, and Notis will parse it correctly.
Can I include metadata in the webhook?
Yes. Include fields like document type, sender, or priority in the JSON payload, and Notis can include them in the Telegram message.
How secure is the webhook?
Notis webhook URLs are unique and can be IP-restricted. Treat them like API keys and don't share publicly.
When this happens · Trigger
Fires when a Box collaboration’s details change.
Do this · Action
Sends a file to a Telegram chat; URL-based documents must be PDF or ZIP.
Supported Triggers and Actions
Notis builds workflows that link Box to Telegram. A trigger fires from one place; an action lands in another.
Box triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Answer Callback Query
Send an answer to an inline button callback, shown as a chat notification or alert.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Deletes a Telegram message, subject to time, message type, and chat permissions.
Collaboration Details Changed
Fires when a Box collaboration’s details change.
Edit Message
Edits a Telegram message, subject to Telegram’s permissions and restrictions.
Comment Changed
Fires when a Box comment’s content or details change.
Export Chat Invite Link
Generate a new primary chat invite link, revoking the previous one.
New File Comment Added
Fires when a new comment is added to a Box file.
Forward Message
Forwards a Telegram message; service messages and protected content cannot be forwarded.
File Metadata Changed
Fires when a Box file’s metadata or properties change.
Get Chat Info
Retrieve current information about a chat.
File Shared Link Changed
Fires when a Box file’s shared link settings change.
Get Chat Administrators
Lists chat administrators, excluding other bots.
New File Version Uploaded
Fires when a new version is uploaded to a Box file.
Get Chat History
Polls pending bot updates and filters the batch; this is not complete chat history.
Connect any two apps with Notis in the middle.
Box and Telegram, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Telegram.