Monitor Telegram Bot Health for Jira Automations
Before sending a notification, Notis checks that the Telegram bot is healthy and responsive. If the bot goes down, you know immediately instead of discovering it hours later.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Get Bot Info
Get basic information about the bot using the bot api getme method.
Why this helps
Your Telegram bot silently stops working. Notifications fail, but you don't notice until someone complains that alerts stopped arriving.
- Catch bot failures early
- Automated health checks
- Reliable notifications
- Zero silent failures
Setup
Build it in a few focused steps.
- 1Connect Jira and Telegram to Notis via the portal.
- 2Create an automation: 'When a new issue is created, check that the Telegram bot is healthy. If the bot is unresponsive, alert me immediately.'
- 3Select Jira's 'New Issue' trigger and your alert channel.
- 4Verify by checking health reports in Notis logs.
Questions about this workflow
How often is bot health checked?
Before each notification is sent. If the bot is down, notifications are queued and retried automatically.
What happens if the bot is unresponsive?
Notis alerts you and attempts to reconnect. You can manually refresh the bot connection via the portal.
Can this also check Jira connectivity?
Yes. Your prompt can request: 'Check both Jira and Telegram are responsive before sending notifications.'
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Telegram. A trigger fires from one place; an action lands in another.
Jira triggers
Telegram actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
Delete Message
Delete a message, including service messages, with certain limitations.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Not just Jira and Telegram. Any combination from 1,000+ 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.