Telnyx Email

Use Telnyx Email when you want Drip Drop to send from domains managed in Telnyx. This guide follows the complete setup: Choose, Connect, Domains, Webhooks, Senders, and Verify. It explains credentials, DNS readiness, delivery and engagement events, optional inbound replies, sender addresses, and final verification.

  • You want domain-based email delivery through a Telnyx account.
  • You want delivery and engagement events from Telnyx in Drip Drop.
  • You want optional inbound replies through a Telnyx email domain.
  • Have a Telnyx API Key and Public Key ready. The API key authorizes Drip Drop’s Telnyx API requests. The public key verifies the Ed25519 signatures on incoming Telnyx webhooks. Both are required.
  • Have a sending domain ready. Add it on Domains and publish the DNS records shown. Telnyx must pass ownership and DKIM before the domain can send. SPF and DMARC are advisory, and MX is required only when you enable inbound replies.
  • If you need replies, choose one Telnyx domain for inbound email.
  1. Open Integrations → Email.
  2. Click New Integration and choose Telnyx Email.
Select Telnyx Email from the available Email providers.
  1. Enter a Name, then enter API Key and Public Key or choose Use credentials from an integration you've already connected.
  2. Select Save & Continue. This stores the credentials and creates the integration, but it does not prove that the credentials work. Use Check credentials on Verify to perform a live Telnyx validation.
Name the Telnyx Email integration and enter its API Key and Public Key.

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. On Domains, enter a domain you own, not an email address, and select Add domain. This creates the sending domain in Telnyx and returns the DNS records Telnyx expects.
  2. Publish the DNS records Drip Drop shows.
  3. Select Check DNS again to ask Telnyx to re-evaluate the domain’s DNS records. Continue when the domain can send, or finish setup and return later. Flows cannot send from this integration until Telnyx reports an eligible sending domain.
Add a sending domain and publish the required DNS records. The example.com values are illustrative and are not part of the verified integration shown later.

Tracking and Delivery Events

  • Enable Track Opens or Track Clicks before configuring the webhook. Drip Drop then applies that tracking to outgoing messages and asks Telnyx to deliver the corresponding open or click events. Delivery, bounce, failure, deferral, complaint, and unsubscribe events are included regardless.

Configure Webhook registers or updates Drip Drop’s URL on every Telnyx email domain you own without replacing unrelated webhooks. Telnyx shared domains are skipped. Run it again after adding a domain or changing the selected event options.

  • Select Save Webhook to store the settings and continue, or select Skip for now. Saving alone does not register or update anything in Telnyx. Configure Webhook performs that live provider action.
  • After Configure Webhook finishes, select Verify Webhook. Verification reads the current Telnyx configuration without changing it and succeeds only when every Telnyx email domain you own has a webhook with the current Drip Drop URL. Shared domains are excluded.

Inbound Replies

  • To receive replies, turn on Enable Inbound Parse and enter one email domain that you own in Telnyx. Configure Webhook then enables inbound receiving for that domain and subscribes Drip Drop to incoming email events.
  • Publish an MX record for the selected domain pointing to mx.telnyx.com before selecting Configure Webhook. Once inbound receiving is enabled, Telnyx requires that MX check for the domain to remain verified.
Review the complete Telnyx Email Webhooks step, including status, configuration controls, tracking, and inbound settings. The webhook URL and inbound domain are illustrative documentation values.
  1. On Senders, add at least one email address whose domain Telnyx reports as able to send, then select Save. Telnyx authorizes domains rather than individual addresses, so Drip Drop stores the address and uses the domain’s Telnyx status for its verification badge.
  2. Continue becomes available after at least one sender is saved. Select Skip for now to finish without one, but flows cannot send from this integration until a sender exists.
Add or review a sender address from a verified Telnyx domain. The [email protected] identity is illustrative and is not part of the verified integration shown later.
  1. On Verify, use Check credentials for live Telnyx authentication, Check again to refresh domain DNS status, and Verify webhook to compare the registered URLs with the current Drip Drop URL. Confirm that at least one sender is configured, then select Done.
Review credential, domain, webhook, and sender readiness before finishing setup. This verified staging fixture is separate from the illustrative example.com captures above.
  1. In an email block, select the saved integration under Integration and select an address under From Email.
  2. Send a test message only to a consented recipient. This sends a real email through Telnyx and may incur provider charges.
The API key or public key is rejected
  • Re-enter both keys and confirm the public key is the Telnyx webhook verification key.
No email domain is available
  • On the integration’s Domains step or tab, add the domain, publish the DNS records shown, and use Check DNS again. Telnyx authorizes email by domain.
Webhook verification is incomplete
  • Run Configure Webhook again and check each Telnyx email domain you own. Drip Drop reports the webhook verified only when every owned domain carries its URL; Telnyx shared domains are excluded.
Inbound email configuration fails
  • Confirm Enable Inbound Parse is on, Inbound Parse Domain exactly matches a Telnyx email domain, and that its MX record points to mx.telnyx.com. Then run Configure Webhook so Drip Drop enables inbound receiving for that domain.
Some Telnyx email events are missing
  • Turn on Enable Webhooks and choose Configure Webhook. Drip Drop registers the webhook separately for each Telnyx email domain you own.
  • Turn on Track Opens or Track Clicks before configuring the webhook when you need those engagement events.
  • If the provider reports a partial configuration, check each email domain in Telnyx and run Configure Webhook again. A domain without the Drip Drop webhook will not send its events.
  • Email — choose and connect an email provider.
  • Flow Editor — add Telnyx Email to an email flow.
  • History — review email delivery results and provider errors.