WhatsApp alerts and approvals in Zapier

A Zap that puts a message on your team's WhatsApp, and a Zap that waits for somebody to tap Approve. No WhatsApp Business account, no number of your own, and no template to get approved by Meta.

Zapier ships an official WhatsApp integration, and it wants what every official one wants: your own WhatsApp Business Account, a registered number, and a message template reviewed by Meta before the first send. For telling your own two engineers that a backup failed, that is a fortnight of paperwork for a one-line notification.

This is the other way round. You call an endpoint that already has a registered number and an approved template, and it reaches your own people — never your customers. That restriction is not a missing feature; it is what makes a shared sender possible at all.

What exists today

Two things, and it is worth being plain about which is which.

RouteState
Webhooks by Zapier → POST to the Jabee APIWorks now. Everything on this page below the key step uses it. Webhooks is a premium Zapier app, so it needs a paid Zapier plan.
A Jabee app in the Zapier directoryNot listed yet, so do not go looking for it. The integration is written and tested against the live API — one trigger, two actions — and this page will say so when it is published.

1. Make a key, and pick a phone

In the Jabee dashboard, go to Management then Approvals and create an API key. It starts jak_. Copy it now; it is not shown again.

Then decide whose phone this reaches. On the Alerts screen, Where alerts go shows the handset in use — by default the phone the account owner verified. To use a different one, it proves itself by sending Jabee a code from the handset. One phone per business: to reach several people you connect your own WhatsApp number, which is the inbox.

2. Send an alert from a Zap

Add an action, search for Webhooks by Zapier, and choose the POST event.

URL             https://api.jabee.ai/api/v1/alerts
Payload Type    json
Wrap Request    no
Unflatten       no

Data
  title         Payment failed for {{customer_name}}
  body          {{amount}} {{currency}} — {{failure_reason}}
  url           https://dashboard.example.com/invoices/{{invoice_id}}
  external_id   invoice-{{invoice_id}}

Headers
  Authorization Bearer jak_your_key_here

title is the only required field. Test the step and the message arrives in about a second.

Put the key in Headers rather than in the URL. A credential in a URL reaches task history, any proxy in front of it, and whatever you paste into a support thread — and a leaked key here sends WhatsApp messages.

Every field the endpoint takes

FieldWhat it does
titleRequired. One line, at most 120 characters. Longer is a 400, not a trim.
bodyThe detail, at most 2000 characters. Delivered word for word; nothing interprets it.
urlA full http or https address. Anything shorter than that is refused.
external_idYour own id, up to 200 characters. A repeat of one already used answers 200 with existing: true and delivers nothing.
expires_in_minutes5 to 10080, a week. Defaults to 1440.
metadataAn object of your own, up to 16KB, returned unchanged on every read. Never shown on WhatsApp.
optionsApprovals only. One to three of approve, skip, edit; the default is approve and skip.

There is no recipient and no team. Both were removed in November 2026 and are now refused with a 400 rather than ignored, because an alert that reports success and arrives on a phone nobody is watching is worse than a failed Zap.

3. Ask, rather than tell

The same call to /api/v1/approvals instead of /api/v1/alerts arrives as a question with buttons:

URL             https://api.jabee.ai/api/v1/approvals
Payload Type    json

Data
  title         Refund 420 AED to order {{order_id}}?
  body          {{customer_name}} says the second seat was never delivered.
  options       approve,skip
  external_id   refund-{{order_id}}

A Zap step cannot sit and wait for a person, so this is two Zaps, not one. The first asks and ends. The second starts when the answer arrives, and matches it back to the first on the external_id you chose.

Three buttons exist and no more — Approve, Skip, Edit — because Meta fixes a template's quick replies at approval time. Edit is one-way: the words somebody types come back to you in response_text and nothing is said to them on the WhatsApp thread. If they asked a question there, answering it is your job.

4. Catch the answer

Start the second Zap with Webhooks by Zapier → Catch Hook, copy the URL it gives you, and paste it into the webhook field on the Jabee Approvals page. Jabee then POSTs there when a request ends.

EventArrives when
approval.answeredSomebody tapped a button. The whole request is under approval, with status of approved, skipped or edited.
approval.expiredNobody answered before expires_at.
approval.failedIt could not be delivered at all.
message.receivedThe verified handset typed something that was not a button and not STOP. Under message: text, from, received_at, about_approval_id, whatsapp_message_id.

Three things about this are worth knowing before you build on it.

There is one webhook address per business. So that single Catch Hook URL receives all four events, and if your own server is already on that field, pointing it at Zapier takes it away from your server. Tell the events apart with a Zapier filter: an approval event has approval status, an inbound message has message text.

Jabee signs every delivery and a Catch Hook does not check it. The headers are X-Jabee-Event, X-Jabee-Delivery and X-Jabee-Signature, the last being an HMAC-SHA256 over the raw body under a whsec_ secret. Zapier's Catch Hook accepts whatever is POSTed to it, so the secrecy of the Catch Hook URL is the only thing protecting that Zap. Treat the URL as a credential, and for anything that moves money verify the signature on a server of your own instead. The contract is in the webhooks reference.

Delivery is at least once. Jabee retries a failed POST at 30s, 2m, 10m, 30m, 1h, 3h and 6h. Deduplicate on X-Jabee-Delivery, or on the request id plus its round.

If pasting a URL into another product's settings is not something you want to do, the alternative is to poll: GET /api/v1/approvals?status=approved on a schedule, newest first. That is exactly what the Jabee Zapier app's trigger does, for exactly this reason.

The Jabee app, when it is listed

What it will add is the plumbing above without the plumbing: a connection you paste the key into once, fields with help text, and errors in English rather than status codes.

StepWhat it is
Trigger: Approval AnsweredPolls for requests somebody has answered. Fires again when a revised request is answered a second time, which a trigger keyed on the request id alone would miss.
Action: Send AlertA one-way notice. Nothing to answer.
Action: Request ApprovalAsks the question and returns at once. Pair it with the trigger above.

There is deliberately no inbound-message trigger in it. A Zapier trigger either polls an endpoint or subscribes to one, and a message typed back from the handset has neither: it exists only as a webhook delivery. So message.received stays a Catch Hook, which is the honest answer rather than a worse version of one.

The three limits that will bite you

One message per task, not per Zap. A Zap runs once for every item its trigger returns, so a trigger that finds forty new rows sends forty WhatsApp messages and spends forty of your monthly allowance. Summarise before the webhook step, or filter in front of it. "14 payments failed overnight" is a better message than fourteen messages.

120 characters on the title. If the title is built from data you do not control, cut it in a Formatter step first. Longer is refused, not shortened.

200 new requests per business per 24 hours, and 60 API calls a minute per key. The daily one protects the standing of the number every business on the plan shares; a runaway Zap hits it long before it hits the monthly allowance.

What it costs

$29 a month for 500 alerts and approvals together, then 3 cents each. The first three sends are free and need no card, so you can wire a Zap up and watch a message land before paying for anything. No per-seat charge.

Webhooks by Zapier is a premium Zapier app, so until the Jabee app is listed this also needs a paid Zapier plan.

Questions

Can Zapier send a WhatsApp message without a WhatsApp Business account?

Yes, to your own team. Use Webhooks by Zapier → POST to https://api.jabee.ai/api/v1/alerts, payload type JSON, a title, and an Authorization header of Bearer jak_.... The number and the Meta-approved template are Jabee's, so there is no developer account, no number to register and no template to submit — and it cannot message your customers, which is the trade that makes it possible.

Is there a Jabee app in the Zapier directory?

Not yet. The integration is written and tested against the live API — one trigger and two actions — and it has not been listed in the directory. Until it is, Webhooks by Zapier does everything it does.

Can a Zap wait for somebody to approve on WhatsApp?

Not in one Zap: a step cannot block for a day, and the default expiry is a day. Use two. The first POSTs to /api/v1/approvals and ends; the second starts when the answer arrives, on a Catch Hook or by polling. Match them on the external_id you sent.

Why did my Zap send forty WhatsApp messages?

Because a Zap runs once per item, and a trigger that returned forty rows is forty runs. Each one also spent one of the 500 a month. Summarise or filter before the webhook step.

Can Zapier be told when my phone replies to a Jabee alert?

Yes, with a Catch Hook. Anything the verified handset types on the alert thread that is not a button and not STOP is posted to your webhook address as a message.received event, so a reply typed from a phone can start a Zap. There is one webhook address per business, so that URL also receives the approval events; a Zapier filter on the body tells them apart.

Does Zapier check Jabee's webhook signature?

No. Jabee signs every delivery with X-Jabee-Signature, and a Catch Hook accepts whatever is POSTed to its URL — so that URL is the only secret involved. Treat it as a credential, and verify the signature on your own server for anything that moves money. See the webhooks reference.

Do I need a WhatsApp number or a Meta account?

No, neither, at any point. The message goes over Meta's official Cloud API on Jabee's registered number using Jabee's approved template. There is no number of yours involved, so there is nothing of yours to get banned.

Can it message my customers?

No, deliberately. It reaches your own people, once they have verified a phone. A shared number messaging strangers is what gets numbers banned. To reach customers you connect your own number, which is the inbox.

What happens if nobody ever answers the messages?

Three notifications in a row with no tap and no reply and we stop sending to that handset, with an email to the account owner saying so. Alerts carry a Got it button; tapping it, or sending any message to the Jabee number, starts it again. One number's standing with Meta is shared by every business on it, which is why the rule exists.