Dub
Receive Dub webhook events in Wexio
Dub signs webhook bodies with HMAC-SHA256 in Dub-Signature (hex, no prefix). You connect it with the Dub preset, which uses Generic HMAC SHA-256. This mode has no replay protection, because the signature covers the body only and carries no timestamp. Inbound webhooks need the Pro or Enterprise plan.
Before You Start
- You can create webhook endpoints in your Dub account.
- You know which Dub events you want to react to.
Setup
1. Connect It in Wexio
Go to Settings → Webhooks and API → Webhooks and click New connection. Choose Inbound. Under Provider presets, click the Dub chip in HMAC presets. It sets Authentication mode to Generic HMAC SHA-256 and fills in these fields. Check that they match.
| Field | Value |
|---|---|
| Signature header name | Dub-Signature |
| Encoding | Hex |
| Header prefix (optional) | Leave empty |
Copy the Wexio endpoint URL.
2. Set Up the Provider
In Dub, add a webhook endpoint with the URL from Wexio and copy the signing secret. Paste it into the Wexio Signing secret field and save.
3. Resolve Contacts
Pick the field in the Dub payload that matches a Wexio contact. Capture a sample event to see the payload shape, as described in Inbound Webhooks.
4. Bind a Flow
Attach a Webhook Received trigger to the connection and branch on the event type field in the payload.
Check That It Works
Send a test event from Dub, then open Webhook History. A request that passed verification is listed as received. A failed one shows its error.
Troubleshooting
| Symptom | Fix |
|---|---|
UNAUTHORIZED: HMAC signature mismatch | The secret is wrong, or the header name, encoding or prefix differs from the table above. Copy the secret fresh from Dub |
Related
- Custom HMAC - how Generic HMAC SHA-256 verifies a request
- Inbound Webhooks - auth modes, contact resolution and response codes
- Webhook History - check why a request failed