Register the Telnyx webhook and troubleshoot calls
How to register your Telnyx channel's Webhook URL in Mission Control and diagnose why a call isn't showing up in the Inbox.
What this is and when you need it
The Telnyx (Programmable Voice) channel connects your Telnyx number to Omnifox so you can place and receive calls right inside the Inbox. For every call event (initiated, answered, hung up, recording) to show up in the conversation, Telnyx has to notify Omnifox through a webhook. If the webhook isn't registered correctly, calls happen but never appear in the inbox — or they never reach you at all.
This is an intermediate guide: you've already created the channel and now need to register the webhook in Telnyx and diagnose why a call isn't coming through.
Requirements
- A Telnyx channel already created under Channels → Connect channel → Telnyx.
- Access to the Telnyx Mission Control portal.
- On hand: your API Key, your Connection ID, and (optional but recommended) the Connection's Signing Key (the Ed25519 public key).
Steps to register the webhook
- In Omnifox open Channels, open your Telnyx channel and copy the read-only Webhook URL field. It looks like
https://omnifox.io/api/webhooks/telnyx. - In Telnyx go to Voice API → Connections and open the Connection you use for this number. Its id is the Connection ID you pasted into Omnifox.
- On the Connection's Webhook tab, paste the Omnifox Webhook URL into Webhook URL and select HTTP POST.
- Copy the Signing Key Telnyx shows in that same section and paste it into the channel's Public Key field in Omnifox. With it, Omnifox verifies the Ed25519 signature on every event. Leave it empty and Omnifox accepts events without verifying the signature (less secure).
- Confirm the channel's Connection ID and API Key in Omnifox match the portal's, then save.
Verification
- Place a real test call to the number. In the contact's conversation you should see, in order: Incoming call, Call answered and Call ended with the duration.
- When a recording exists, a Recording available line appears with a link to the MP3.
- Omnifox routes each event by matching the Connection ID in the payload, so the channel's id must be exactly the one of the Connection that fires the call.
If it doesn't work
- No events at all: the Webhook URL isn't pasted into the right Connection, or the Connection receiving the call isn't the one whose Connection ID you set in Omnifox.
- You get a 403 / invalid signature: the Signing Key pasted into Public Key doesn't belong to that Connection. Copy it again from Connection → Webhook → Signing Key, or clear the field temporarily to confirm the rest of the flow works.
- "no channel route": the event's
connection_idmatches no channel. Make sure the Connection ID in Omnifox has no stray spaces. - Outbound calls fail: usually the from number (Default From) is missing. Set it on the channel or pass it from the call screen.
Tips
- Always keep the Signing Key configured in production — it's the only way to guarantee events truly come from Telnyx.
- If you rotate the API Key in Telnyx, update it in Omnifox too (see the edit-credentials article) or outbound calls stop being created.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.