Send Chat Data to Your System (Webhook)
POST selected conversation data from a Bot Flow to your HTTPS endpoint. The bot continues immediately — it does not wait for your server.
This is not Public API / OMS inbound (G15) and not Meta WhatsApp Flows.
Detail: Integrations · Send to Webhook.
Before you start
| Need | Where |
|---|---|
| HTTPS URL you control | Your server or a test receiver |
| Bot Flow to edit | Build Your First Bot Flow |
| Consent for outbound customer data | Your responsibility as the destination owner |
Path at a glance
- Create a Webhook integration
- Copy the signing secret
- Add Send to Webhook in a Bot Flow
- Choose the payload
- Place the step and go live
- Verify on your server
1. Create a Webhook integration
- Open Settings → Integrations.
- Click Create Integration.
- Set type Webhook (Send to Webhook).
- Enter Webhook URL (HTTPS) (HTTPS only).
- Leave Allow contact phone in webhook payloads off unless you need the phone and have consent.
- Save.
If you paste a webhook.site editor link, Kazenly stores the HTTPS receive URL instead.
2. Copy the signing secret
After create (or Rotate signing secret on save on edit):
- Copy Signing secret (copy now) — shown once.
- Confirm I've copied it — Done.
Verify requests on your server with that secret. Rotating invalidates the previous secret.
3. Add Send to Webhook in a Bot Flow
- Open Settings → Bot Flows or Automations → WhatsApp.
- Edit a flow → add step type Send to Webhook.
- Expand Data leaves Kazenly — you are responsible for consent and sub-processor disclosure; Kazenly cannot erase data from your destination. Phone is included only when the integration allows phone (off by default).
4. Choose the payload
| Option | Behaviour |
|---|---|
| Webhook integration | Pick the integration from step 1 |
| Send full context | Answer fields plus safe context; secrets/bookkeeping stripped; phone only if allowed |
| Fields to include | When full context is off — chips from an earlier Send WhatsApp Flow step |
| Contact fields | Optional ticks; Sensitive badge when marked; empty: No contact field definitions yet. |
| Static custom fields | Add field for fixed tags (for example source name) |
Place Send WhatsApp Flow before this step if you want Flow answer chips.
5. Place the step and go live
Typical order: Message / Send WhatsApp Flow → Send to Webhook → Assign Agent (or Condition).
Save the Bot Flow and ensure it is active (keyword or Default Bot Flow).
6. Verify on your server
- Trigger the bot so the webhook step runs.
- Confirm HTTPS delivery and signature verification.
- Confirm the bot continued to the next step without waiting.
Delivery is best-effort over HTTPS.
Quick paths
| Path | Setup |
|---|---|
| A. Minimal | Webhook integration → Send to Webhook → Send full context → Assign Agent |
| B. Flow answers only | Send WhatsApp Flow → Send to Webhook (fields chips) → Assign Agent |
| C. Contact fields | Define Contact Fields → tick Contact fields on the step |
| D. Include phone | Enable Allow contact phone on the integration (consent required) |
Related
- Send to Webhook
- Integrations
- Bot Flows
- Bot Flow with WhatsApp Flow and Branching
- Contact Fields
- Connect an OMS — inbound API (different direction)