Telnyx Storage

Connect Telnyx Storage to store and reuse Drip Drop attachments and images in a Telnyx Cloud Storage bucket you manage. This guide explains the required credentials, connection settings, and verification steps.

  • You already use Telnyx for messaging or email and want storage on the same account.
  • You want one Telnyx API key to cover your Telnyx integrations rather than separate credentials per service.
  • You want an S3-compatible bucket without managing an AWS access key pair.
  • Confirm you have a Telnyx Cloud Storage bucket and know its home Region.
  • Have an active Telnyx API Key for the account that can access the bucket.
  • Confirm the key allows the bucket operations Drip Drop needs: upload, read, delete, and list.
  • Confirm your role can create integrations. Without that permission, New Integration is not shown.
  • Optionally decide on a Key Prefix to confine Drip Drop to a dedicated path in the bucket.

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. Open Integrations → Storage.
  2. Select New Integration and choose Telnyx Storage.
Choose Telnyx Storage in the New Integration wizard.
  1. Enter a Name for the integration.
  2. If a reusable Telnyx credential is available, choose it. Otherwise, select Enter new credentials and enter your API Key.
  3. Enter the Bucket Name.
  4. Confirm the Region. It defaults to us-east-1; enter the bucket’s home region if it differs.
  5. Optionally enter a Key Prefix. Drip Drop can access only objects beneath it.
  6. Select Save & Continue.

Drip Drop derives the Telnyx Cloud Storage endpoint from the Region value, so the form does not show Endpoint URL, Addressing Style, or Encryption.

Telnyx Storage connection form with the name, API key, bucket, region, and optional key prefix fields.
  1. On Verify, select Check credentials. Drip Drop checks the bucket and writes, reads, and deletes a temporary object.
  2. After the check succeeds, select Done.
  3. On the Storage page, confirm the integration you named appears as Active.
  4. Open a message template, find Attachments, then select Browse files → Connected storage.
  5. Choose the integration and an object beneath the Key Prefix, if configured, then select Attach.

Telnyx public buckets require Level 2 verification and are available only in supported regions. Apply a bucket policy that grants anonymous read access only to the Public Folder, not the private attachment Key Prefix. Use https://<region>.telnyxcloudstorage.com/<bucket-name> as the Public Base URL.

Images embedded in emails must remain publicly readable without signing in. Keep public access limited to a folder that is separate from the private attachment prefix.

  1. Open the saved integration and expand Serve email images from this bucket.
  2. Enter the Public Base URL and a separate Public Folder.
  3. Configure your storage service to allow anonymous read access to the Public Folder.
  4. Select Verify public access.
  5. After Publicly readable appears, enable Available as a public media location.
  6. Return to Storage. Under Email image location, choose the verified bucket.

If connection or public-media settings change, verification becomes stale. Select Verify public access again before using the bucket.

Changing Email image location affects only newly published images. Existing published images stay at their original location.

Invalid credentials
  • Confirm the API Key is active and belongs to the Telnyx account that owns or can access the bucket.
  • Create a fresh key in Telnyx if the existing key may be invalid, then save the connection again.
Wrong region or signature error
  • Confirm the selected Region is the bucket’s home region.
  • Drip Drop derives the regional endpoint from this value, so a mismatch can cause signing or object-operation failures.
Bucket access fails
  • Confirm the Bucket Name is correct.
  • Check that the API Key can inspect the bucket and upload, read, and delete objects beneath the configured Key Prefix.
  • If you use a prefix, confirm it is the intended object-key boundary.
Listing works but object actions fail
  • Recheck the bucket Region and the permissions for object operations.
  • Drip Drop’s connection validation tests object access rather than only checking that the bucket exists.
  • Storage: choose and manage storage for Drip Drop attachments and images.
  • Message Templates: add stored files as attachments or use them as images in email designs.