Vercel
Receive Vercel deployment events in Wexio flows
Wexio verifies the x-vercel-signature header, an HMAC-SHA1 of the raw body. The signature carries no timestamp, so there is no replay protection. Inbound webhooks need the Pro or Enterprise plan.
Provider docs: Vercel webhooks
Setup
1. Connect It in Wexio
Go to Settings → Webhooks and API → Webhooks → New connection → Inbound and click the Vercel chip under Dedicated providers, or set Authentication mode to Vercel manually. Copy the Wexio endpoint URL.
2. Set Up the Provider
In Vercel, open Team Settings → Webhooks, create a webhook and set the URL to the Wexio endpoint URL. Pick the events you need.
Vercel shows the webhook secret once, when you create the webhook. Copy it and paste it into the Wexio Signing secret field. If you lost it, delete the webhook in Vercel and create it again.
Send X-Idempotency-Key where you can, because a captured request can be sent again.
3. Resolve Contacts
Pick the field in the Vercel payload that matches a Wexio contact. Deployment events often carry no contact, so you may need a fixed Chat ID. 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 Vercel event, 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. Delete and recreate the webhook in Vercel to get a new one |
UNAUTHORIZED: Missing x-vercel-signature header | The request did not come from Vercel, or a proxy removed the header |
Related
- Inbound Webhooks - auth modes, contact resolution and response codes
- Webhook Received - the trigger that starts your flow
- Webhook History - check why a request failed