ChatOps on WhatsApp: when a reply is an instruction

Last updated 17 November 2026

By Mumen Tayyem, founder of Jabee

Published 17 November 2026.

ChatOps was always a Slack idea: a bot in a channel, a few slash commands, and a deploy you can trigger from your phone without opening a laptop. It works, and it assumes something that is often untrue for a small team — that everyone is in Slack, on that phone, with notifications on.

The app that is actually open is WhatsApp. This is the same loop on it: your system sends a message, you type a reply, and your own code receives what you typed as a signed webhook. Both directions over a number you never bought and never verified.

What arrives when you type back

When the handset you verified sends something on the alert thread that is neither an answer to an open request nor STOP, it is relayed to your webhook address:

X-Jabee-Event: message.received

{
  "id": "4b1c...",
  "event": "message.received",
  "message": {
    "text": "redeploy staging",
    "from": "9715xxxxxxxx",
    "received_at": "2026-11-13T11:20:04.000Z",
    "about_approval_id": null,
    "whatsapp_message_id": "wamid...."
  }
}

about_approval_id is set when the message was a swipe-reply to one of your own requests, so a system with three open questions can tell which one "do it" was about. For an ordinary message it is null.

That is the entire feature. There is no command parser, no intent model and no dashboard screen for it — deliberately. What a reply means is your business's own vocabulary, and a layer in the middle guessing at it is a layer that will one day guess wrong about a production deploy.

The part you must not skip

The text is untrusted. Anyone holding that phone can type anything into it, and the relay makes no judgement about what the words mean. Two consequences, and both are yours to implement:

// Verify, then authorise, then act. In that order.
const result = verify(rawBody, req.headers["x-jabee-signature"], secret);
if (!result.ok) return res.writeHead(401).end(result.reason);

const { message } = JSON.parse(rawBody);
if (!ALLOWED.has(message.from)) return res.writeHead(204).end();   // who
if (!COMMANDS.has(message.text.trim().toLowerCase())) return res.writeHead(204).end();  // what

First, verify the signature: X-Jabee-Signature: t=<unix>,v1=<hex>, where the hex is the HMAC-SHA256 of <t>.<raw body> under your signing secret. Compute it over the raw bytes before anything parses the JSON, compare in constant time, and refuse a timestamp more than five minutes old so a captured delivery cannot be replayed next week. A working receiver in Node and in Python, with tests for the tampered, replayed and malformed cases, is in examples/.

Second, authorise. An allowlist of commands beats a parser, and "anything from my verified phone can do anything" is not an authorisation model — it is a lost phone away from being a breach.

What it is not

Being plain about the edges is cheaper than a support thread later:

Why both directions matter at all

One direction on its own is a notifier, and there are free ones. The pair is a loop: a job can tell you it is stuck, you can tell it what to do, and it can ask you before doing the irreversible part. That is the loop an agent needs too — which is why the same key drives an MCP server that gives an AI agent tell_person and ask_person tools.

Both directions are API-only and intentionally so. Setting the address and the signing secret is one screen in the dashboard, under Management then Approvals; everything after that is your code. The reference is the webhook documentation.

Questions

Do I need my own WhatsApp number for this? No. Messages go out from Jabee's approved sender and replies come back to your webhook, so there is nothing to register and no template to get through Meta's review. Connecting your own number is the option if you need several people to receive messages.

Who can send a message that reaches my webhook? Only the handset your business verified. Anyone else messaging that number reaches no account. You should still authorise the sender in your own code, because a phone can be lost or shared.

What stops somebody replaying a captured delivery? The timestamp is inside the signature, so a delivery captured today cannot be re-sent next week and still verify. Refuse any t more than five minutes old; the examples do.

Can I use this to take commands from customers? No, and not by configuration either — the relay only carries the verified handset. For customer conversations you connect your own WhatsApp number, which is a different product.

How do I tell which open request a reply was about? Swipe-reply to the request on the phone and about_approval_id carries its id. Without that it is null, which is why an allowlist of unambiguous commands is worth more than a clever parser.

Is there a dashboard for this? No. You set the webhook URL and secret in the dashboard, and after that it is API-only on purpose: what a reply means is your own vocabulary, not something we should be guessing at.