Telnyx

Use Telnyx when you want Drip Drop to send SMS messages, receive inbound SMS, and optionally place phone calls 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.
  • You may also want to place calls through Telnyx, depending on your phone setup.
  • 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.
  • Have the API key and public key ready.
  • Use a safe test number for the first send and inbound test.
  1. Open Dashboard → Admin → Integrations.
  2. Click New Integration and choose Telnyx.
  3. Enter the API key and Public Key.
  4. Save the provider, then open the Webhook section.
  5. Select the messaging profile Drip Drop should use.

After the credentials are saved, Drip Drop can list messaging profiles from Telnyx and help configure the webhook for the selected profile.

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.
  • If auto-configure is available, Drip Drop can update the webhook URL on the selected messaging profile.
  • If auto-configure is not available, set the webhook URL manually in Telnyx Mission Control.
  • Outbound SMS is sent through Telnyx and Drip Drop stores the Telnyx message id after success.
  • Inbound messages are webhook-driven and tied to the selected messaging profile.
  • Status and inbound traffic depend on the webhook URL configured on that messaging profile.
  • Telnyx can also place calls; keep voice expectations high-level unless your team maintains separate voice setup docs.

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.

  • If the public key is wrong or missing, webhook validation can fail even if the webhook URL itself is correct.
  • This security model is different from Twilio because it is based on Telnyx signature headers and the saved public key.
  1. Open the relevant messaging profile in Telnyx Mission Control.
  2. Set the webhook URL to the Drip Drop endpoint for the selected profile.
  3. Save the profile and return to Drip Drop to verify the configured state.
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 matches the Telnyx account sending the webhook.
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.
  • See Integrations for the shared provider setup flow and provider management basics.
  • Compare Twilio if you want a similar phone and SMS workflow organized around Twilio phone numbers instead of Telnyx messaging profiles.