Docs / Vendor onboarding

Connect Twilio webhooks to Relin

Relin receives Twilio webhooks, verifies signatures, stores payloads, and delivers them to your endpoints with retries, alerts, and replay.

Open the Twilio dashboard

Before you start

  • Create a Relin workspace and sign in.
  • Have admin access to the Twilio account where you'll configure the webhook.
  • Decide which events you want to capture, or start with "all events" if you're exploring.

Setup steps

  1. In Relin, open your workspace and click New source. Pick the Twilio tile.
  2. Copy the ingest URL Relin shows. This URL is shown once, so store it.
  3. Create the Relin source first.
  4. Send Twilio status callbacks to the Relin source URL.
  5. Add the auth token here when request validation is required.
  6. Save and send a test event from Twilio. Confirm Relin received it in your workspace.

Auth token: Optional for this source. Add it if your Twilio webhook uses request validation.

What Relin does next

  • Verifies the signature on every incoming event and records the status (verified, failed, unchecked).
  • Stores the payload so you can replay or inspect it later, bounded by your workspace retention window.
  • Delivers the event to every destination you've connected to this source, with retries and per-destination rate limits.
  • Surfaces lifecycle gaps (for vendors with known lifecycles) as anomalies you can triage from the dashboard.

Test it

The fastest check is the events view in your workspace. After you send a test event from Twilio, it appears within a second or two. Click into the event to see the raw payload, signature status, and the delivery attempts to your destinations.

You can also use the REST API or the MCP tools to inspect the stream programmatically.

Twilio-specific notes

  • Twilio signature verification is optional. If you paste your Twilio Auth Token into the signing-secret field, Relin verifies the X-Twilio-Signature header; otherwise signature status is reported as 'unchecked'.

Troubleshooting

  • Signature status is failed: the auth token doesn't match. Re-copy it from Twilio and update the Relin source.
  • Signature status is unchecked: no signing secret is configured on the source yet. Paste the secret on the source settings page.
  • No events arriving: check that the ingest URL in Twilio matches the URL Relin shows, including the token segment at the end.
  • Events arrive but destinations fail: open the delivery attempts tab on the event detail page. Each attempt shows the response body, status, and timing.

Next