Share relevant incident location context
If an incident workflow includes a meaningful location, have Notis send the map point and a short explanation to Telegram.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Location
Send point on the map location to a telegram chat using the bot api.
Why this helps
When a team relies on location context for an incident, coordinates can be hard to recognize or pass along clearly in a text-only update.
- Make location context easier to open and understand in Telegram.
- Keep a relevant map point connected to the incident note.
- Avoid sending location messages when the source provides no meaningful location.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and Telegram once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language.
- 3In one instruction, ask Notis to send a Telegram location only when the incoming context includes a relevant point, with a short incident note.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real request that contains a valid location and review the Telegram result.
Questions about this workflow
Do Bugsnag incidents always have a location?
No. Use this workflow only when your webhook input or connected data includes a meaningful location. Otherwise the automation should skip the location action.
What starts the workflow?
An HTTP request to the Notis webhook starts it. This is not a native Bugsnag event trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugsnag to Telegram. A trigger fires from one place; an action lands in another.
Bugsnag triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
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.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
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.).
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.
Bugsnag and Telegram, or any other combination from 1,000+ 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.