Daily Alerts for Overdue Jira Issues
Every morning, overdue issues get highlighted in Telegram and sent to your team lead. No more surprises at deadline time; overdue work is visible and actionable.
Trigger
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.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
Issues quietly slip past their due dates. You discover they're late during a status meeting, when it's too late to adjust.
- Early visibility of delays
- Fast escalation paths
- Prevent deadline surprises
- Improve delivery confidence
Setup
Build it in a few focused steps.
- 1Connect Jira and Telegram to Notis via the portal.
- 2Create an automation: 'Every morning, send a message to #leads with any issues that are past their due date.'
- 3Select the 'Daily Schedule' trigger at your preferred time and your leads channel.
- 4Verify the first overdue alert appears correctly.
Questions about this workflow
How does Notis know which issues are overdue?
From the due date field in Jira. Any issue with a due date in the past is flagged as overdue.
Can I exclude certain projects or issue types?
Yes. Your prompt can specify: 'Only show overdue issues from the Product project, not internal tasks.'
Should overdue issues be auto-escalated?
Notis can escalate to team leads. Your prompt defines the action: 'Send to @lead or reassign to the project manager.'
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.