Communication · Integration
Telnyx
Add Telnyx to your product for your customers, and give your AI agents governed access to it.
Telnyx's v2 API at api.telnyx.com authenticates with a bearer key, and outbound messaging is bound to a messaging profile: a number cannot send until it is assigned to one, which is the usual cause of a rejected first send. There is no listing endpoint for messages, so delivery outcomes arrive as webhooks configured on the profile rather than by polling, and the send response only confirms the message was accepted. Phone numbers, messaging profiles and connections are separate objects that all have to line up before SMS or voice traffic works at all. Numbers are also regulated, so several countries require an approved address or identity document on the account before an order will complete. fastn holds each customer's Telnyx key in its own tenant and keeps webhook handling and retries in one place.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Telnyx account so messages go out on their numbers and their bill
Send a notification from your product and record its delivery outcome from the webhook rather than the send response
Show a customer which of their numbers are attached to which messaging profile so failed sends are explicable
Place or receive calls against a customer's own connection so recordings and costs stay with them
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent send an approved message template to a verified number, with the message ID and recipient logged per tenant
Have an agent diagnose a failed send by checking whether the number is assigned to a messaging profile
Let an agent report delivery failures over a period and group them by error code
Example prompt
Why did our texts to UK numbers fail yesterday but the US ones went through?
Set up Telnyx in 4 steps
- 01Enable the Telnyx connector from your fastn dashboard.
- 02Have each customer authorise their own Telnyx account, so calls run under their credentials rather than a shared key.
- 03Decide which messages, conversations and participants your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Telnyx integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Telnyx integration without building it. Your customers connect their own Telnyx account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Telnyx update is not your on-call problem.
- One integration serves your product and your agents. The same governed Telnyx connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Slack
Microsoft Teams
TwilioOften used alongside
Tools the same teams tend to run next to Telnyx, across other categories.
Aircall
Calendly
Gong
Google CalendarTelnyx integration FAQ
How do I add a Telnyx integration to my product?
Enable the Telnyx connector in your fastn dashboard, then let each customer authenticate their own Telnyx account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Telnyx client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Telnyx account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Telnyx account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Telnyx integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent send an approved message template to a verified number, with the message ID and recipient logged per tenant
Who maintains the Telnyx integration?
fastn does. When Telnyx changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own Telnyx account?
Yes. Every customer authorises their own Telnyx account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Telnyx integration?
A common starting point: let a customer connect their own Telnyx account so messages go out on their numbers and their bill. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Telnyx integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Telnyx does not change your per-connector cost. You can start free with 3 connected accounts.
Add Telnyx to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.