Notifications are messages triggered by your own systems rather than by someone in MsgOrb. A booking is confirmed, an order ships, a ticket changes state — that system posts to MsgOrb and MsgOrb sends the WhatsApp message.
Three event types exist, each with its own page under Automations → Notification in the sidebar:
| Event | Page | Typical source |
|---|---|---|
| Appointment | Appointment | Calendly, a clinic or salon booking system |
| Delivery | Delivery | Shopify, a courier or an order system |
| Status Update | Status Update | A CRM, help desk or case system |
What each page gives you
- 1The endpoint URL for that event type, ready to copy.
- 2The API key for the workspace, passed in the
x-api-keyheader. - 3A template selector — the approved UTILITY template this event will send.
- 4A field mapper that translates your system's payload into the fields MsgOrb expects.
- 5Connection logs — the last 100 calls with their HTTP status and error text.
The rule that matters most
Notifications are proactive: they reach people who have not messaged you. That means Meta requires an approved template, and MsgOrb enforces it. An event with no template selected is refused with HTTP 409 and a message telling you to choose one. MsgOrb never falls back to free text here, because Meta would not deliver it.
Multiple businesses in one workspace
If you run several businesses from one workspace, add &business=<group_id> to the endpoint URL. Each business gets its own template choice, its own field mapping and its own log view. Without the parameter, the workspace default configuration is used.