Meta’s events, without a server of yours.
There is no webhook to paste into Make and no URL you have to host. You connect the channel in Settings and messages start coming in.
Every Conext customer shares the same Meta app subscription. What says who each event belongs to is the id Meta puts in the payload: the number, the Page, or the Instagram account.
It is not a webhook into your database.
Conext does not fire events toward an ERP, a spreadsheet, or Zapier. What exists is the other way: Meta tells us, we store the thread, and the AI drafts. If you need to sync contacts with another system, there is no connector today. The inbox is the system.
We host the URL. The verification challenge (`hub.challenge`) and the signature on every POST are handled with the app secret. On your side there is no webhook token to copy: there is a connect button in Channels.
How it knows which business it is.
WhatsApp brings the `phone_number_id` in the payload. Instagram and Messenger bring `entry[].id`, which is the IGID or the PAGE_ID depending on the `object`. Those three columns are unique: two businesses cannot claim the same number. If the id matches no one, the event is dropped. Guessing would write it in the wrong inbox.
The CRM answers 200 immediately and processes afterwards. If it were slow, Meta would retry and the same message would duplicate. The message id (the wamid, or Messenger’s mid) is the lock: the second delivery does not create another row.
What is processed today.
Text. An audio, a photo, or a location is logged and does not open a reply: the customer would be waiting for something the team cannot see. Receipts do: on WhatsApp each status names the message; on Messenger and Instagram a watermark arrives (“everything before this is delivered”) and that thread’s outbound messages are updated.
If the app is subscribed to `message_echoes`, Meta sends our own outbound back. That echo is dropped: otherwise the AI would answer itself. The objects and statuses are in the documentation reference.
In practice
- 1
Connect the channel
WhatsApp or the Page, from Settings. That is where the ids used to resolve each event are stored.
- 2
Meta posts to our URL
There is nothing to paste into an “outbound webhook” panel. The subscription belongs to Conext’s app.
- 3
The thread shows up in the inbox
If it does not, Meta’s id is not tied to your business or the app is not subscribed to `messages`.
The webhook is from Meta into Conext, not from Conext out to the rest of your tools. That is why connecting the channel is enough, and why there is no Zapier card.
Want to see it with your own threads?
Essential includes one channel, 500 AI conversations per month, and one active agent.