Jira and Twilio connect through Jira's built-in webhook system and REST API to send SMS alerts when critical issues are created, escalated, or transition to specific statuses, ensuring on-call engineers receive incident notifications on their phones even when they are not watching the Jira board. This integration is particularly useful for engineering and DevOps teams that use Jira for incident tracking and want SMS as a secondary escalation channel alongside email and Slack when a P1 or P2 issue fires. The connection uses a Jira webhook to detect issue events, a middleware endpoint to evaluate the event and select the correct recipient phone, and Twilio's Messages API to deliver the alert.
What You Need Before You Start
You need Jira Software or Jira Service Management at any plan tier, and administrator access to configure webhooks in Jira Cloud under Settings, then System, then Webhooks, or in Jira Data Center under Administration, then System, then WebHooks. From Twilio, collect your Account SID, Auth Token, and an SMS-capable phone number, and prepare a mapping table that links Jira usernames or account IDs to mobile phone numbers for each team member who should receive SMS alerts. Your middleware server needs a publicly accessible HTTPS URL for the Jira webhook to POST to, as Jira Cloud requires HTTPS and a valid certificate before saving the webhook configuration. Identify the Jira issue field values you want to trigger on, specifically the priority name values like Critical and Blocker and the issue type names, by calling GET https://your-domain.atlassian.net/rest/api/3/priority with Basic authentication using your Atlassian email and an API token from https://id.atlassian.com/manage-profile/security/api-tokens.
Step-by-Step Integration Guide
Create a Jira webhook by navigating to Settings, then System, then WebHooks in Jira Cloud and clicking Create a WebHook, entering your middleware URL such as https://yourapp.com/jira/webhook, selecting the Issue events checkboxes for issue created and issue updated, and optionally adding a JQL filter in the advanced section such as project = OPS AND priority in (Critical, Blocker) to restrict which issues trigger the webhook. In your middleware, receive the Jira webhook POST and parse the webhookEvent field to distinguish jira:issue_created from jira:issue_updated, then extract issue.fields.priority.name, issue.fields.status.name, issue.fields.assignee.accountId, issue.fields.summary, and issue.key from the payload. Look up the assignee phone number from your mapping table using the accountId value, and optionally fetch the assignee's display name for the message by calling GET https://your-domain.atlassian.net/rest/api/3/user?accountId={accountId} with your Basic auth credentials. Send the SMS via POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json with To set to the mapped phone number and Body set to a message like issue.key plus issue.fields.summary plus status plus priority, keeping the body under 160 characters to avoid multi-part SMS splitting on older handsets.
Common Issues and How to Fix Them
Jira Cloud sends webhook payloads with a user-agent header and expects your endpoint to return HTTP 200 within 5 seconds, and if it times out on the first attempt, Jira retries the event up to 10 times over the next hour before dropping it. Return HTTP 200 immediately from your webhook handler and process the Twilio API call asynchronously in a background job to avoid timeout failures causing unwanted retries. The Jira webhook fires for every issue update including comment additions, label changes, and watcher additions, generating far more events than you want to act on. Add a conditional check in your handler that inspects the changelog array in the webhook payload for the specific field that changed, checking changelog.items[n].field equal to status or priority before proceeding, and discard all other update events silently. Jira webhook registration requires the URL to be accessible at the moment of saving, and saving a webhook pointing to a development server not yet running results in a confusing validation error. Test your endpoint is reachable by using a tool like curl before opening the Jira webhook settings, and use a permanent staging URL rather than a local tunneling URL for anything beyond initial development.
How to Get More from This Integration
Build an on-call rotation resolver by storing your on-call schedule in a simple database table with start and end timestamps per engineer, and having your middleware query the table on each webhook event to find the currently on-call engineer's phone rather than always sending to a fixed recipient list. Extend the integration to voice calls for the most critical priority levels by having your middleware call POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Calls.json when the issue priority is P0 or Blocker, using TwiML to read the issue key and summary aloud so the engineer hears the alert even in a noisy environment where an SMS might go unnoticed. Add a two-way acknowledgment loop by routing Twilio inbound SMS from on-call engineers back to your middleware, which checks for keywords like ACK or ESCALATE and then calls the Jira REST API at PUT https://your-domain.atlassian.net/rest/api/3/issue/{issueKey}/transitions to move the issue to an Acknowledged status, closing the loop without the engineer needing to open Jira. Create a Jira automation rule under Project Settings, then Automation that fires when an issue has been in a critical status for more than 30 minutes without a status change, calling your middleware via a webhook action to trigger an escalation SMS to the team lead in addition to the original assignee.
Conclusion
Jira and Twilio together ensure that critical issues and incidents reach your on-call engineers by SMS the moment they appear, eliminating the gap between a Jira ticket and a human response. Contact Telphi Consulting to build and configure this incident alerting integration for your Jira project.
Ready to Transform Your Business Communications?
Get a free consultation with our VoIP experts and discover how we can help you save costs, improve efficiency, and scale your business.
Comments (0)
Join the discussion and share your thoughts (AI-moderated for quality)
Be the first to comment
No comments yet. Share your thoughts below.