Outbound webhooks
In one sentence
Webhooks let MsgBuddy notify your own software the instant something happens — a message arrives, a template is approved — so you can plug MsgBuddy into your systems.
Who this is for
This is a developer feature. If you don’t run your own software, you can safely skip it. If you do, webhooks are how you keep another system (a CRM, an ops dashboard) in sync with MsgBuddy in real time.
How webhooks work
You give MsgBuddy a URL (an “endpoint”) on your server. When a chosen event happens, MsgBuddy sends that URL a small message describing it.
Setting one up
From Settings → Webhooks:
- Create an endpoint — paste your URL.
- Choose events — pick which ones to receive (new message, template status change, …).
- Save — MsgBuddy starts delivering events, and shows you a delivery log so you can see what was sent and whether it succeeded.
Each delivery is signed (with an HMAC signature) so your server can verify it genuinely came from MsgBuddy and wasn’t forged. Deliveries also carry a version, so your integration won’t break when the format evolves.
Start by subscribing to just one event (like “message received”), confirm your server receives it in the delivery log, then add more. Debugging one event at a time is far easier than ten at once.
How this connects
- Webhooks pair with the API — read/write via the API, react via webhooks.
- These are outbound (MsgBuddy → you). The inbound webhook from Meta (WhatsApp → MsgBuddy) is set up automatically when you connect your number.
Next: turn the AI assistant on — chatbot settings →.