Jabee documentation

How each part works, what it will and will not do, and the code where there is code. Written for the person who has to make it work rather than the person deciding whether to buy it.

Start here

• Quickstart

  From nothing to an assistant answering a real WhatsApp message, in about ten minutes.

• Connecting WhatsApp, Messenger and Instagram

  What Embedded Signup does, what your Facebook Page brings with it, and the two windows Meta enforces.

For developers

• MCP server

  Wire approvals into Claude Code, Cursor or anything that speaks MCP. One environment variable, three tools.

• Grafana and Alertmanager

  A webhook contact point that puts your alerts on WhatsApp. No template, no relay, any Grafana version including Cloud.

• Uptime Kuma

  The Webhook notification type with a custom body. Both the down and the up alert, and why there is no switch for that.

• Zabbix

  A webhook media type and twenty lines of script, with the title cap and the retry key that make it behave.

• GitHub Actions

  One step with if: failure(), a link to the run, and the injection you avoid by passing values through env.

• cron and systemd

  A || after the job, or one OnFailure= unit for the whole machine, for the jobs that run and fail.

• Heartbeat checks

  A URL the job pings when it finishes, so silence is what raises the alert. For the job that never ran at all.

• n8n, Make and Zapier

  An HTTP request node instead of the WhatsApp node, so no business account or template approval is involved.

• Home Assistant

  A rest_command and one automation, for the few alerts that have to reach a silenced phone.

• Claude Code notifications

  A WhatsApp message when a long run finishes, or when it is sitting there waiting for you. A Stop hook, or the MCP server.

• The three kinds of WhatsApp MCP

  Which kind reads your chats, which kind risks your number, and which needs no number of your own. With the install block.

• There is no sandbox

  What Meta's test number really is, why yours stopped working, and three real sends to your own phone instead.

• Approvals API

  Ask a person to approve something on WhatsApp. Buttons, an Edit that returns text, and a signed webhook back.

• Sending notifications

  Tell your own people something happened, from Jabee's number, with no number of your own.

• Webhooks and signatures

  Verifying the HMAC, dropping duplicates, and what gets retried when your endpoint is down.

• Connecting your own API

  A URL, a key and one sentence about when to call it. How Jabee decides, and what it sends.

• Systems that answer later

  When your side takes minutes, hand back a reference and post the result when you have it.

Running it

• The shared inbox

  Assignment, the three filters, saved replies, and the three ways you get told somebody is waiting.

• Intents: say exactly this, or do this first

  Taking control of particular questions without building a flowchart.

• Appointments

  Booking in the conversation, an .ics on every confirmation, and a calendar feed to subscribe to.

• Products

  A catalogue read off your own website, with the filters your products already carry.

• Enquiries

  What Jabee writes down when somebody asks for a quote or a callback, and where it goes.

• Your team and who gets told

  Logins, handsets with no login, routing by language or keyword, and the alerts rules.

• Several businesses on one account

  For agencies. One login, a switcher, and a page showing what each client costs you.

If something here is wrong

Email hello@jabee.ai. These pages are kept beside the code that implements them, so a mistake here is usually a mistake there too and worth hearing about.