Integrations, API and webhooks

OMAI is a finished product rather than a platform you build on. It talks to a small, fixed set of services in order to do its job, and it does not expose a way for your own systems to talk to it. This article says exactly which is which, so you can decide whether OMAI fits a requirement you already have.

What OMAI connects to today

Six outside services are involved in running the product. Only the first one is something you connect yourself; the rest are wired into the platform and are not configurable per account.

Israeli tax documents — the חשבונית מס/קבלה for a payment and the תעודת זיכוי for a refund — are issued through an accounting provider on OMAI’s side. You never configure it, and it never appears in the dashboard; the result is the document linked from the Invoices table. See Invoices and receipts.

The one connection you make yourself

Connecting your WhatsApp number is the only integration work you do. It happens inside Meta’s own window: you sign in to Facebook, pick the business portfolio, choose the number, and Meta grants OMAI permission to send and receive on it. OMAI stores the resulting access token in Azure Key Vault and subscribes to the webhook that delivers your incoming messages.

That permission is yours to withdraw. Disconnecting the number in WhatsApp Connection stops delivery immediately, and you can also revoke OMAI’s access from Meta’s side. See Connecting with Embedded Signup and Managing connections.

There is no public API

OMAI does not publish an API for customers. There is no developer portal, no API key, no personal access token, no client credentials and no place in the dashboard to create any of those. The account has exactly one credential: the one you sign in with.

The application does have HTTP endpoints under /api/, and you will see them in your browser’s network tab. They are internal: every one of them authenticates the browser session cookie and refuses anything else, and they are scoped to the organization that session belongs to. They are versionless, they change whenever the screens that use them change, and they are not documented or supported for outside use. Building against them will break without notice.

There are no outgoing webhooks

OMAI cannot post an event to a URL you own. There is no field anywhere for a callback URL, no signing secret to copy, no delivery log and no retry queue — because there is nothing that delivers. A new message, a handoff, a completed payment or a plan change raises no outbound HTTP call to a customer system.

The word “webhook” does appear in OMAI, pointing the other way. Meta posts your incoming WhatsApp messages to OMAI, Twilio posts number and delivery events, and the payment provider posts the result of a charge. Those are inbound endpoints that only those providers can reach — their signatures are verified and unsigned payloads are rejected. None of them can be repointed at an address of yours.

No automation builder and no CRM connectors

To be precise about what does not exist, because these are the four questions that come up most:

• No automation platform connector. There is no Zapier, Make or n8n app, and no other hosted automation service is wired in.
• No CRM connector. OMAI does not sync contacts, conversations or leads to Salesforce, HubSpot, Pipedrive, monday.com or anything else, in either direction.
• No workflow or rule builder. You cannot define “when X happens, do Y” inside OMAI. The assistant’s behaviour is shaped by its settings, its hours and its knowledge base — not by rules you compose.
• No calendar, e-commerce, ticketing or payment-link integrations. The assistant answers from what you have told it; it cannot look up an order, read a diary, book a slot or take a payment inside the conversation.

The Leads screen is sometimes mistaken for a CRM hand-off. It is not: it reads lead records but nothing in the product writes one, so on a live account it stays empty. See Leads.

Getting your data out

What exists instead of an API is a full export. Settings → Account & privacy → Export your data builds one JSON file covering the whole organization — conversations, messages, contacts, settings and more — and streams it to your computer as a download. There is no date range, no per-conversation download and no stored copy or link.

It is a manual, human-initiated action: someone signs in and presses the button. It cannot be scheduled and it cannot be called by a script. Every run is recorded in the audit log. If you need OMAI data in another system today, this file is the route — parse it there. See Exporting your data.

If you need one of these

Tell us the requirement rather than the mechanism. “Every new enquiry has to appear in our CRM within the hour” is something we can respond to usefully; “do you have a webhook” only gets a no. Write to support@omai-software.com with what you are trying to achieve, which system it has to reach, and whether it is a blocker for you.

We will tell you plainly whether it is possible today. This article deliberately does not describe a roadmap: it documents what the product does now, and what it does not do now is a straight no rather than a not-yet. See Contacting support.