Telnyx SMS & MMS

Connect Telnyx to send SMS and MMS messages and receive inbound SMS through a Telnyx messaging profile.

Note
Telnyx is a phone and messaging provider. It is not an email or mailbox integration.
  • You want Drip Drop to send text messages through a Telnyx messaging profile.
  • You want inbound SMS and status events to reach Drip Drop through a Telnyx webhook.
  • Confirm you have Telnyx account access and permission to view or edit messaging profiles.
  • Make sure the account has at least one usable messaging profile for the traffic you want to send.
  • If you are entering new credentials, have the API Key and Public Key ready.
  • Use a safe test number for the first send and inbound test.

Telnyx Credentials

Telnyx integrations can share one account-scoped credential, so you enter a Telnyx API key once instead of repeating it for every Telnyx integration you add.

Choosing a credential when you add a Telnyx integration

When you create a second or later Telnyx integration, you can:

  • Reuse an existing account-scoped Telnyx credential, or
  • Promote an eligible unlinked integration's inline key into a shared credential

The choice is made when the integration is created. Existing integrations cannot be linked, swapped, or unlinked afterward.

What sharing does and does not cover

A shared credential covers authentication only. Settings, status, webhooks, and senders stay separate for each integration.

The credential list shows only the credential name, vendor, and how many integrations use it. You cannot create, reveal, or edit a secret from that list.

Note

Before you rotate or delete a credential. Rotating the secret changes it for every integration linked to that credential. Confirm which integrations use it before rotating, and expect each linked integration to need attention afterward.

  1. From the dashboard, open Integrations → Text Message, then select New Integration.
  2. Choose Telnyx SMS. Drip Drop lists only providers that are not already configured for the account, so Telnyx SMS will not appear if a Telnyx integration already exists.
  1. Enter a clear Name. Under Credentials, reuse an existing account-scoped Telnyx credential, promote an eligible unlinked integration’s credential, or select Enter new credentials and provide the API Key and Public Key.
  2. Select Save & Continue to save the integration and move to Webhooks.
Enter a name and the Telnyx API Key and Public Key, then select Save & Continue.
  1. Select the Messaging Profile that should receive inbound messages and delivery events. Select Configure Webhook, review any conflict before choosing Overwrite Existing Webhook, then select Save Webhook. Select Skip for now to defer this step.
Select the Telnyx messaging profile, then configure or verify its webhook. Webhook and profile values are hidden for documentation.
  1. Add or sync at least one Telnyx phone number that flows can send from. Continue is enabled after a sender exists; Skip for now leaves the integration unable to send until a sender is added from its settings.
Add at least one Telnyx phone number for flows to send from, then select Continue.

Review the checklist for stored credentials, webhook readiness, and senders. Telnyx does not offer a live credential-check button on this step. Select Done when the checklist reflects the intended setup, or finish any warnings later from the integration settings.

Review stored credentials, webhook readiness, and senders before selecting Done.

Configure and Verify the Messaging-Profile Webhook

Telnyx webhook configuration is messaging-profile based. Drip Drop compares the selected profile webhook URL with its own expected endpoint and can help configure it.

  • If the selected messaging profile already points to a different webhook URL, Drip Drop can show a conflict instead of silently replacing it.
  • Select Configure Webhook to register the Drip Drop URL on the selected messaging profile. If another URL is already registered, use Overwrite Existing Webhook only after confirming that replacing it will not interrupt another integration.
  • To configure the webhook manually, copy the displayed webhook URL to the selected messaging profile in Telnyx Mission Control, then return to Drip Drop and select Verify Webhook.

Signed Webhook Validation

The Telnyx public key in the provider is used for signed webhook validation. Drip Drop uses the signed request headers from Telnyx to verify the webhook payload.

  • The Public Key is required for signed webhook validation. If it is missing or incorrect, Drip Drop rejects incoming Telnyx events even when the webhook URL is correct.
  • This security model is different from Twilio because it is based on Telnyx signature headers and the saved public key.

Outbound SMS and MMS

  • Outbound SMS and MMS are sent through Telnyx. An MMS can include up to 10 JPEG, PNG, or GIF images, up to 600 KB each and 1 MB total. Drip Drop refuses an MMS send when the selected sending number is known not to support MMS.

Inbound Messages

  • Inbound messages are webhook-driven and tied to the selected messaging profile.

Delivery-Status Events

  • Status and inbound traffic depend on the webhook URL configured on that messaging profile.
Credentials and Profile Problems
  • If the provider cannot connect, confirm the API key and public key are correct.
  • If no messaging profiles appear, make sure the Telnyx account has accessible profiles and that the API key can list them.
  • If the wrong profile was selected, switch to the one that should own inbound and outbound messaging for Drip Drop.
Webhook Problems
  • If Drip Drop reports a conflict, check whether the selected messaging profile already points to another webhook URL.
  • If inbound messages or status events do not appear, verify the webhook URL on the selected messaging profile in Telnyx.
  • If signed validation fails, confirm the saved Public Key is the Telnyx Ed25519 public key for the account sending the webhook. A missing or incorrect key causes incoming events to be rejected.
Inbound and Sending Problems
  • If messages send but replies do not appear, test the inbound webhook path with a real SMS through the selected profile.
  • If sending fails only on one profile, confirm that profile is configured for the numbers or traffic you expect.
  • If an MMS send is refused, sync the integration’s senders and confirm the selected number supports MMS. Use no more than 10 JPEG, PNG, or GIF images, up to 600 KB each and 1 MB total.
  • See Integrations for shared provider setup and management.
  • See Text Message for channel setup and provider selection.
  • Compare Sendblue for a line-based messaging workflow.
  • Compare Twilio for a phone-number-based SMS and MMS workflow.
  • See Troubleshooting for shared provider and workflow triage.