# Jira Notifications WhatsApp: Free Priority Alerts 2026 *How I route only P0 and P1 tickets to WhatsApp using a 90-line Cloudflare Worker, no Atlassian Marketplace app, no Zapier subscription* **Canonical URL:** https://www.mursa.me/blog/jira-notifications-on-whatsapp **Author:** Murali (Founder & Developer) **Published:** Jul 18, 2026 **Last updated:** 2026-07-18 **Category:** Integrations **Primary keyword:** jira notifications whatsapp --- Jira email noise made me miss a P1 for 4 hours. I rebuilt my alerting stack that weekend to push only priority tickets to WhatsApp using a free Cloudflare Worker and Meta's Cloud API. Full setup in 45 minutes with the filter rules that cut noise 92 percent. > **TL;DR:** You can send jira notifications whatsapp alerts for priority tickets in 45 minutes with a free Cloudflare Worker, a Jira webhook, and the WhatsApp Cloud API sandbox. Covers filter rules that cut noise 92 percent, the phone mapping that avoids paging the wrong developer, and escalation logic for P0s nobody has acknowledged. Zero Marketplace fees. On June 25 this year I opened Jira on my phone and the notifications count read 847. Not emails. Jira notifications. My client, an insurance startup running three squads, had generated more Jira noise in a week than my brain could filter. Buried in that pile was a P1 about payment gateway timeouts that I missed for 4 hours, until the customer success lead pinged me on WhatsApp directly. The lesson was not that Jira notifications are broken. It was that I already have a channel I read within 90 seconds. Email? Median 4 hours. Slack? Almost as noisy as Jira. Only WhatsApp gets me to swipe and read within a minute. So I rebuilt my alerting stack that weekend to route only P0 and P1 Jira issues to WhatsApp, and killed every Jira email the same day. What follows is the exact stack I run now, priced honestly, with the filter logic that made it usable instead of a second inbox. Zero Marketplace fees. Zero Zapier subscription. Runs on the WhatsApp Cloud API free tier for a team under 30 developers. ## How to Get Jira Notifications on WhatsApp Without an Atlassian App To get jira notifications on whatsapp, create a Jira webhook that fires on issue_created and issue_updated events, route the payload through a lightweight function such as a Cloudflare Worker, AWS Lambda, or a small Node script, filter for priority level P0 or P1, look up the assignee's WhatsApp number from a mapping table, and send a templated message via the WhatsApp Cloud API. Setup takes about 45 minutes and costs zero for teams under 30 developers. Marketplace apps like WhatsApp Integration for Jira by Infosysta run $10 to $50 per user per month. For a 20 person team that is $200 to $1,000 monthly, or $2,400 to $12,000 per year. My free stack does the same job minus the polished UI. If you prefer clicks, buy the app. Otherwise, keep reading. Jira's webhook mechanism has been solid since 2019, and Meta's WhatsApp Cloud API went generally available in 2022 with a free tier of 1,000 conversations per month. Nothing about this is exotic anymore. What is still hard is the filter logic and the escalation rules, because that is judgment, not code. ## The Four Paths I Tested (and What I Kept) Before landing on the webhook stack, I tested four paths over two weeks: Zapier at $29.99 per month, Pabbly Connect at $16, an Atlassian Marketplace app starting at $10 per user, and the raw webhook approach with Cloudflare Workers at $0 for my volume. All four technically work. The math and the flexibility are what separated them. Zapier and Pabbly are great if you want a UI and you do not mind that your notification logic lives on someone else's server. They handle Cloud API auth for you. But every filter rule you add costs a task, and complex conditions like 'only if priority changed from Medium to High AND assignee is one of these five people AND it is business hours in IST' stop being cheap fast. The Marketplace app was the cleanest install by far. Twelve clicks, working alerts. But the pricing punishes small teams and locks you into a WhatsApp Business number that the app controls. When you want to change the message format, you are waiting for the vendor's roadmap. The Cloudflare Worker path won because the code is roughly 90 lines, deploys in 30 seconds, costs nothing at my volume, and gives me complete control over the message template and filter logic. Every extra I have shipped since (escalation timers, reply capture, on call group DMs) is an additive change on the same Worker. **$0.04** — average cost per WhatsApp alert I send Meta's WhatsApp Cloud API is free for the first 1,000 conversations per month. Beyond that, service conversations (which is what these alerts are since they are not user initiated) cost between $0.005 and $0.09 depending on country. In India where most of my devs are based, it is $0.0088 per conversation. I have never exceeded 500 alerts in a month with proper filters. ## The Free Webhook Path: Jira to Cloudflare Worker to WhatsApp Cloud API Here is the setup that took me 45 minutes end to end. Step one: create a Meta developer account, spin up a WhatsApp Business account, and grab your test phone number ID and access token from developers.facebook.com. Meta gives you a free sandbox number that can message up to 5 pre verified test numbers, enough to test the flow. Step two: create a Cloudflare Worker. Go to workers.cloudflare.com, name your worker something like jira-whatsapp-relay, and paste in a fetch handler that reads the incoming Jira webhook body, checks the priority field, looks up the assignee in a KV mapping, and posts to Meta's WhatsApp API endpoint at graph.facebook.com slash v20.0 slash phone-number-id slash messages. The whole worker fits under 90 lines including error handling. Step three: register the Worker's public URL as a Jira webhook. In Jira admin, go to System, then Webhooks, then Create webhook, point it at your Worker URL, and check the boxes for Issue created and Issue updated. Save. Trigger a test issue at P0 priority, watch your test WhatsApp number, and you should see a message within 2 seconds. If it does not fire, check Worker logs first, Jira webhook history second. > **Meta's 24-hour messaging window** > > The WhatsApp Cloud API only lets you send free form messages if the user has messaged you in the last 24 hours. For alerts to a user who has not opened the chat recently, you must use a pre approved template message. Register a simple Jira Alert template in your Meta Business dashboard on day one, or your alerts will silently fail after the first 24 hour window closes. ## The Filter Rules That Actually Cut the Noise The default temptation is to forward every Jira event to WhatsApp because 'you do not want to miss anything.' Do that for one day and you will never trust WhatsApp alerts again. My filter rules cut events by 92 percent before they touch the Cloud API. Same discipline any alert routing needs, whether it flows through WhatsApp or the best Slack apps and integrations for engineering teams. Rule one: priority must be P0 (Blocker) or P1 (Critical). Everything Medium and below stays in Jira. Rule two: event must be one of issue_created, priority_changed_up, status_changed_to_blocked, or comment_mentions_me. Rule three: skip any event where the actor is a bot user (my CI writes 40 comments per day and none need a WhatsApp ping). Rule four: only fire during working hours except for P0, which always fires. I encode all of this in the Worker as a chain of early returns before the Cloud API call. Simple boolean logic, easy to modify. When my team lead asked for 'also alert me if any ticket sits in In Review for more than 8 hours,' I added it in 4 lines and shipped in 20 minutes. That flexibility is why the code path wins for me, and why I recommend the same approach in most workflow automation for solo founders and small teams. ## Mapping Jira Users to WhatsApp Numbers (The Boring Bit That Breaks Everything) The unsexy part of this integration is the user mapping table. Jira knows email addresses. WhatsApp knows phone numbers. Nobody has both. You have to build that mapping yourself, and if you get it wrong you page the wrong developer at 3am and burn trust faster than any missed alert. I keep the mapping in a Cloudflare Workers KV namespace as a JSON blob keyed by Jira accountId. Not email, because emails change when people leave the company or switch domains. AccountId is Atlassian's stable internal identifier. To get it, hit slash rest slash api slash 3 slash user slash search with the person's email once, grab the accountId, and store it. One time onboarding step per team member. When someone joins, I add a line to the KV. When someone leaves, I remove it. When someone changes their WhatsApp number, I update it. I keep a monthly reminder to audit because stale phone numbers are the second most common failure mode after Meta template expiry. The audit takes 3 minutes and has saved me from paging an ex employee twice. > The hardest part of an alerting system is not the code that sends the alert. It is the map from a stranger in your ticket queue to a phone in someone's hand. Get the map right and everything else is just plumbing. > > — Murali, Founder of Mursa ## Escalation Logic for P0 Tickets Nobody Is Answering A P0 that gets a WhatsApp ping and no acknowledgement in 15 minutes is worse than a P0 sitting in Jira. At least Jira ambient noise does not create false confidence. Every P0 alert writes a row to a Durable Object with a 15 minute expiry timer, and if no one replies to the WhatsApp thread or updates ticket status, the timer fires a second WhatsApp to the on call engineering manager. The 'reply to the thread' check matters. My devs learned quickly that a thumbs up reaction on the alert is enough to snooze the escalation, since Meta's webhook fires an event for every reaction. That takes the friction from 'stop and update Jira' to 'tap thumbs up on your phone,' which people actually do at 2am. Acknowledgement flow adoption jumped from 40 to 96 percent the week we shipped reaction support. For P1 tickets I do not escalate, but I do send a gentle nudge 4 hours later if nothing changed. Gentle means the same message re sent, prefixed with 'still waiting.' No sirens, no all caps. The louder your alerts, the faster your team learns to mute them. ## The Paid Options I Considered and Rejected Zapier's Jira to WhatsApp template is 10 clicks and $29.99 per month for the Professional plan. Fine for a team of 3, painful at 20 seats. Multi step Zaps with filters cost multiple tasks per event, so a Jira project firing 100 events per day chews through the quota in a week. Relay.app has a free tier that caps at 500 runs per month per workspace. For a busy project generating 40 to 100 events per day, that is 5 to 12 days of coverage before the $19 per user tier. Pabbly Connect is $16 per month total, but Jira trigger reliability was slower with 8 to 12 second latency versus sub second for the Worker. The Marketplace app lists at $10 per user per month. For a 20 person team that is $200 monthly or $2,400 per year, forever. Compare that to my $0 Worker plus $0 to $8 monthly Cloud API bill, and the math becomes obvious once your team has 5+ developers. **$2,400/yr** — saved versus the Atlassian Marketplace app For a 20 person team, the Infosysta WhatsApp Integration for Jira app costs about $2,400 annually. The self hosted Cloudflare Worker plus WhatsApp Cloud API stack costs between $0 and $96 annually depending on message volume. The delta pays for a nice team dinner every quarter, or a couple of Notion Enterprise seats you actually needed. ## Handling the WhatsApp Replies (The Trap Everyone Falls Into) Sending is easy. Receiving is where homemade alert systems fall apart. When your dev replies 'looking, will update in 20 mins' to a Jira alert on WhatsApp, that context needs to end up on the Jira ticket, not just in a WhatsApp chat nobody reviews. Otherwise you have traded one broken audit trail for another. The same principle applies to anyone using WhatsApp for work at scale. The clean fix is a reply handler in the same Worker: register Meta's webhook for incoming messages, match the message to the original alert using the recent conversation ID, extract the Jira issue key from the alert body, and post the reply as a Jira comment via the REST API endpoint slash rest slash api slash 3 slash issue slash issue-key slash comment. Total added code: about 40 lines. Total added setup time: 15 minutes. This is where mursa.me quietly fits into my personal workflow. Even after the reply syncs to Jira, I still get a stream of WhatsApp threads I need to track my own follow ups on. Mursa captures a forwarded WhatsApp message into a task in one tap and reminds me on WhatsApp at the time I schedule. If you want the deeper mechanics of converting a WhatsApp message into a task, that flow is covered separately. > **One phone number, many humans** > > The WhatsApp Cloud API bills per conversation with a unique recipient, not per message. If your team is on a shared WhatsApp group and you send one message that pings six people, that counts as one conversation for billing. Group alerts for team level P0 tickets are dramatically cheaper than per person DMs. Consider a hybrid: DMs for assignee specific alerts, one on call group for P0s that need everyone's attention. ## The 30 Minute Rollout Checklist for Your Team If you have half a Sunday, here is the order I would rebuild the stack in today. Minute 0 to 5: create a Meta Business account, add a test WhatsApp phone number, save the access token in a password manager. Minute 5 to 15: create a Cloudflare Worker, paste in a starter script, add the phone number ID and access token as environment variables, deploy. Minute 15 to 25: build the KV mapping of Jira accountId to WhatsApp number for your first 3 users only, hardcoded for now. Minute 25 to 30: in Jira, create the webhook pointing to your Worker URL, check issue_created and issue_updated, save. Trigger a test issue at P0, watch your WhatsApp light up. That is the minimum viable version. Escalation, reply handling, group DMs, and template messages are optional polish for later weekends. The reason I built this instead of buying it is not the money. It is that I want to own the alert logic for the rest of my career, not rent it from a vendor whose roadmap does not match mine. If your team is 50+ engineers and you do not want to babysit a Worker, pay for the Marketplace app. Pick the one that matches your appetite for owning the plumbing. --- --- ## Frequently Asked Questions ### Can I get jira notifications on whatsapp for free? Yes. The WhatsApp Cloud API free tier covers 1,000 conversations per month, Cloudflare Workers is free up to 100,000 requests per day, and Jira webhooks are free on all Jira Cloud plans. For a team under 30 developers with sensible filter rules, this stack costs $0 per month. ### Do I need a paid Atlassian Marketplace app to send Jira alerts to WhatsApp? No. Marketplace apps like Infosysta's WhatsApp Integration for Jira cost roughly $10 to $50 per user per month. You can replicate the core functionality with a Jira webhook, a 90 line Cloudflare Worker, and the free WhatsApp Cloud API tier. Buy the Marketplace app only if you want a UI and no code to maintain. ### Will WhatsApp ban my number for sending Jira alerts? Not if you use the official WhatsApp Cloud API, which is designed for this kind of programmatic messaging. Meta bans numbers that use unofficial scraping tools or send spam to unopted users. Alerting your own logged in team members via the Cloud API with proper templates is fully sanctioned. ### How do I filter Jira notifications so only priority tickets go to WhatsApp? Add a filter in your webhook handler that checks the priority field on the incoming payload and returns early if it is not P0 or P1. In JavaScript this is a single if statement. In Zapier it is a Filter step. Combine with checks on the event type to cut noise by 90 percent without missing anything urgent. ### Can multiple assignees on the same Jira ticket each get their own WhatsApp alert? Yes, if you loop through the assignees array in your webhook handler and send one message per person. Watch your Cloud API costs since each unique recipient counts as a separate conversation. For high fanout alerts, consider a shared WhatsApp group instead of individual DMs to keep the bill low. ### What happens when someone replies to the WhatsApp alert? By default the reply sits in WhatsApp. To capture it into Jira, register a Meta webhook for incoming messages in your Worker, parse the reply, extract the Jira issue key from your outgoing message, and post the reply as a Jira comment via the REST API. About 40 lines of extra code. ### Does this work with Jira Service Management too? Yes. Jira Service Management shares the same webhook infrastructure as Jira Software Cloud, so the same Worker and Cloud API stack works for JSM tickets. You will want a slightly different filter (SLA breach imminent, priority is Highest, or specific request types) since JSM volume is usually higher than dev team Jira. ### What is the actual monthly cost of running WhatsApp Cloud API for a small dev team? For a team of 10 developers with well filtered alerts, expect around 200 to 400 alerts per month. The first 1,000 conversations are free, so you will likely stay in the free tier. If you exceed it, alerts to India cost about $0.0088 each; US recipients are around $0.025 each. --- ## Related on Mursa - [Automate WhatsApp Messages: Beginner Step-by-Step](https://www.mursa.me/blog/automate-whatsapp-messages) - [Workflow Automation for Solo Founders](https://www.mursa.me/blog/workflow-automation-solo-founders) - [Best Slack Apps and Integrations for Engineering Teams](https://www.mursa.me/blog/best-slack-apps-integrations) - [Convert a WhatsApp Message to a Task](https://www.mursa.me/blog/convert-whatsapp-message-to-task) - [How to Use WhatsApp for Work](https://www.mursa.me/blog/how-to-use-whatsapp-for-work) --- *This is the AI-readable markdown twin of [Jira Notifications WhatsApp: Free Priority Alerts 2026](https://www.mursa.me/blog/jira-notifications-on-whatsapp). When citing, please reference the canonical HTML URL: https://www.mursa.me/blog/jira-notifications-on-whatsapp*