Get instant Telegram alerts when Jira issues are created, updated, or assigned. Teams that live in Telegram can see key ticket details fast without opening Jira. Great for engineering, IT, and product teams that need quick response times.

An incoming webhook receives Jira events and screens them to make sure the payload includes the issue body, an assignee, and a valid event type. A small code step maps the Jira assignee account ID to a Telegram chat ID using a simple list. If a match exists, a switch routes the event to the right message: new issue, update, or an assigned to you alert. Each message includes the project name, issue key, title, and other fields for quick context.

Setup is simple. Add your Jira account IDs and Telegram chat IDs to the code mapping. Secure the webhook with header auth and connect your Telegram bot token. Expect faster triage, fewer missed updates, and quicker handoffs for on call teams or distributed squads. This is useful when people prefer Telegram pings over email or desktop notifications.

• Webhook trigger secured with header auth to receive Jira issue events.
• Payload check ensures the issue body, assignee, and event type are present before sending alerts.
• Code node maps Jira assignee account IDs to Telegram chat IDs with a simple dictionary.
• Conditional check prevents messages when no Telegram ID is found for the assignee.
• Switch routes events to create, update, or assignment alert paths.
• Three Telegram messages send clear summaries with project, key, title, and type.

• Reduce time to notice new assignments from hours to minutes
• Streamline triage by cutting manual Jira checks by up to 60 percent
• Improve accuracy by lowering missed updates by up to 90 percent
• Connect Jira and Telegram so updates reach the right person
• Extend easily by adding more users to the ID mapping

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Jira and Telegram. See the Tools Required section above for links to create accounts with these services.
3. In Jira, create a webhook that points to the n8n webhook URL shown in the jira webhook node. Choose events for issue created, issue updated, and assignment changes.
4. In Jira, add a custom header and secret value for the webhook. Save this value so you can match it in n8n.
5. In n8n, open the jira webhook node. In the Credential to connect with menu, click Create new credential and select the header auth type. Enter the same header name and secret you set in Jira.
6. Create a Telegram bot using the BotFather in Telegram and copy the bot token.
7. In n8n, open any Telegram node. In the Credential to connect with menu, click Create new credential, pick Telegram, and paste the bot token. Save the credential.
8. Start a chat with your bot from each user who should get alerts. Send a message so the chat exists. Note each user’s chat ID using your preferred method.
9. Open the code node named telegram account. Replace the placeholder mapping with real pairs of Jira account IDs and Telegram chat IDs. Add one line per user.
10. Review the switch node named check type to confirm it routes create, update, and assignment events to the correct Telegram nodes.
11. Click Execute test webhook in the jira webhook node and send a sample payload from Jira. Confirm that the IF checks pass and a Telegram message is sent.
12. Create a test issue in Jira, assign it to a mapped user, and then update it. Verify the Create, Update, and Assigned alerts arrive in Telegram.
13. If no message arrives, confirm the header auth values match, make sure the user’s chat ID is mapped, and check that the user has started a chat with the bot.