Keep incident updates moving from Bitbucket to Telegram
Give your team one readable incident update with the impact and next action that were actually provided.
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
During an incident, important status changes can get lost while people switch between issue tracking and chat.
- Put the issue status and next step in a familiar chat.
- Keep the update limited to information supplied in the request.
- Make missing impact or ownership details visible.
Setup
Build it in a few focused steps.
- 1Connect Bitbucket and Telegram once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to format incident issue details from each webhook as a concise Telegram update and mark any missing impact or next step.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real incident issue webhook.
Questions about this workflow
Does this monitor Bitbucket issues by itself?
No. The webhook starts the automation, so your Bitbucket integration or other system must send the incident details to it.
Will Notis invent an impact statement if one is missing?
No. Ask Notis to state that the impact was not provided when the webhook does not include it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitbucket to Telegram. A trigger fires from one place; an action lands in another.
Bitbucket 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.
Bitbucket 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.