Step 01
- Home
- Use Cases
- Industries
- Features
- Pricing
- Partner
- Company
- Blogs
- ISO 27001 Certified
Choose which WhatsApp events your application receives and where Robofy sends them. Connect a WhatsApp Business Account to your HTTPS endpoint and subscribe to incoming messages, delivery updates, template status changes, and supported account alerts.
Choose your account. Add your endpoint. Select your events.
A selected WhatsApp event is packaged as a JSON POST request, signed with your configured secret, and delivered to the HTTPS endpoint you control.
Match a subscriptionRobofy forwards only the WhatsApp events selected for this webhook.
Sign the payloadYour secret produces an HMAC-SHA256 signature in the request header.
Verify and respondYour application validates the signature, processes the JSON, and returns a successful response.
Subscribe to one event type or combine several in the same webhook configuration.
Trigger: A customer sends a WhatsApp message.
Process the reply, update a customer record, or trigger a configured workflow.
Trigger: A supported message status update is received.
Update sent, delivered, read, or failed status in your message records.
Trigger: Meta sends a supported account alert.
Notify the team responsible for investigating account alerts.
Trigger: Meta reports a template status change.
Keep template records and operational workflows informed.
Set the account, destination, event subscriptions, and request settings in the Create Webhook form.
Step 01
Step 02
Step 03
Step 04
Add a secret key and Robofy signs each forwarded payload with HMAC-SHA256. Your endpoint can confirm the signature before it processes the event.
The signature is delivered in the X-Hub-Signature-256 request header and verified with the same secret.
Review your configured webhooks, see their selected events, and manage their active status from the webhook list.
Identify each webhook by its name, destination URL, connected account, and event subscriptions.
Edit the webhook when your endpoint, subscriptions, or request settings change.
Switch a webhook between Active and Inactive while keeping its saved configuration.
Access webhook logs for a configured webhook.
Remove webhook configurations that are no longer required.
A WhatsApp webhook delivers event notifications to an application, such as an incoming customer message or a delivery status update. In Robofy, you configure the receiving URL, select a WhatsApp Business Account, and choose which supported events to forward.
Robofy supports Incoming Message, Delivery Status, Account Status, and Template Status subscriptions. Account Status covers supported account alerts received from Meta.
Yes. Select one or several supported event types when creating the webhook. You can update the subscriptions later by editing the configuration.
Yes. Each webhook configuration is associated with a selected connected WhatsApp Business Account.
Yes. The Delivery Status subscription covers supported sent, delivered, read, and failed updates when available.
Configure a secret key for the webhook. Robofy uses it to sign forwarded payloads with HMAC-SHA256 and includes the signature in the X-Hub-Signature-256 header. Your endpoint verifies the signature using the same secret.
First verify the X-Hub-Signature-256 header with the secret configured for the webhook. After accepting the request, process the JSON event in your application and return a successful HTTP response.
No. Receiving a webhook provides event data to your application. Sending a reply is a separate action through a supported messaging API or Robofy sending workflow.
Yes. Use the Active/Inactive control in the webhook list. Disabling a webhook keeps its configuration available so you can enable it again later.
Choose your WhatsApp Business Account, add your endpoint, and select the events your application needs to receive.