Route External Webhooks to Telegram for Team Alerts
When your other tools trigger events, keep your team in the loop. This automation sends webhook notifications straight to Telegram so nothing happens in isolation.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
Founders use multiple SaaS tools, and important events in one tool don't automatically reach the team. This creates information silos where some team members miss critical updates from other systems.
- Connect any external tool that sends webhooks to Telegram
- Keep the team aware of events from all your systems in one chat
- Reduce context-switching between multiple platforms
- Eliminate information silos across your stack
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Telegram to Notis.
- 2Create an automation: 'When I receive a webhook from [your external tool], send a message to Telegram'.
- 3Notis provides a unique webhook URL for this automation.
- 4Configure your external tool to send webhooks to that URL (copy and paste the URL into the third-party tool's webhook settings).
- 5Trigger a test event in the external tool and confirm the Telegram message appears in your chosen channel.
Questions about this workflow
Can I customize how the webhook data appears in Telegram?
Yes. Tell Notis in the automation prompt how to format the message. For example: 'Show the user name, action, and timestamp' or 'Extract only the status and alert level'.
What if the webhook payload is complex or nested?
Notis can parse complex JSON payloads. In your prompt, specify which fields matter to you and how they should be displayed in Telegram.
Is the webhook URL secure?
Notis generates unique URLs for each automation and can include authentication tokens if needed. You can rotate the webhook URL anytime for security.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Telegram. A trigger fires from one place; an action lands in another.
Google Drive triggers
Telegram actions
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
File Created
Triggers when a new file is created in Google Drive.
Delete Message
Delete a message, including service messages, with certain limitations.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Edit Message
Edit text messages sent by the bot.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Not just Google Drive and Telegram. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Telegram.