Try it
Twilio signs the exact URL you set in the console, plus every POST param sorted by name, with your auth token (HMAC-SHA1, base64). The guard rebuilds that string and compares.
Retell sends X-Retell-Signature: v=<timestamp>,d=<hex>. The digest is HMAC-SHA256 of the raw body plus the timestamp, with your Retell API key. The guard also rejects anything older than 5 minutes.
Vapi sends a secret you choose in a header: Authorization: Bearer ... by default, or X-Vapi-Secret for older setups. n8n already checks this with Header Auth on the Webhook node, so the workflow uses that. A wrong or missing header gets a 403 from n8n before any node runs.
What breaks without it
- A bot posts
CallStatus=no-answerwith any phone number. Your missed-call text-back texts a stranger from your business number. - Someone replays an old end-of-call report. Your CRM gets a duplicate lead and your owner alert fires again. (Retell replays older than 5 minutes are blocked. Twilio signs no timestamp, so also dedupe by CallSid.)
- Every fake request burns AI credits and SMS spend.
- The common half-fix fails on real traffic: checking a Retell signature against parsed JSON, or a Twilio signature against the URL n8n sees behind a proxy.
How the n8n workflow works
- Twilio In / Retell In webhooks keep the raw body. Raw Body turns it into text, byte for byte.
- Plan Check rebuilds the exact string the provider signed and rejects early: no header, bad format, stale timestamp.
- HMAC uses the built-in Crypto node. The secret lives in an n8n credential, not in the workflow or the run log.
- Decide compares in constant time. No match, no secret, or any error means 403.
- Only Verified? true reaches Your Flow Goes Here, with the parsed payload.
No community nodes and no require('crypto'). Tested on self-hosted n8n 2.48.7.
Get it
Free n8n workflow on GitHub (MIT). The README has setup, and TESTING.md lists what was tested and what was not.