Knock
Receive Knock webhook events through a proxy
Knock signatures aren't supported yet. Send Knock events through a proxy that adds a shared secret. Inbound webhooks need the Pro or Enterprise plan.
Wexio cannot verify Knock signatures, so there is no Knock preset. Use Shared secret (default) and put a proxy between Knock and Wexio.
Before You Start
- You can create webhook subscriptions in your Knock account.
- You have an n8n or Zapier account to act as the proxy.
Setup
1. Connect It in Wexio
Go to Settings → Webhooks and API → Webhooks and click New connection. Choose Inbound and leave Authentication mode on Shared secret (default). Copy the endpoint URL and the secret. Wexio shows the secret once. The header name is listed as Secret header (x-webhook-secret).
2. Set Up the Proxy
In n8n or Zapier, receive the Knock event, then forward it to the Wexio endpoint URL with an HTTP request that sets two things.
- Header. Add
x-webhook-secretwith the secret from Wexio. - Body. Send the Knock event as JSON with
Content-Type: application/json.
Follow the n8n or Zapier page for the exact steps. Point your Knock webhook at the proxy, not at Wexio.
3. Resolve Contacts
Pick the field in the Knock 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
Trigger a Knock event, then open Webhook History. A request that passed verification is listed as received. A failed one shows its error.
Troubleshooting
| Symptom | Fix |
|---|---|
UNAUTHORIZED: Invalid secret | The x-webhook-secret header is wrong or missing in the proxy. Copy the secret fresh from Wexio |
Related
- n8n - build the proxy in n8n
- Zapier - build the proxy in Zapier
- Custom Shared Secret - how the secret header works
- Webhook History - check why a request failed