Storage

Connect a storage provider to keep your attachments and images in a service you manage. This hub explains how to connect a provider, how the storage choice affects attachment selection, and what to check when a connection cannot be used.

Storage integrations fall into two groups. Object-storage services use a bucket, credentials, and an optional key prefix. OAuth services authorize Drip Drop against a connected account and ask for no credentials. Choose the provider that matches where your team already keeps files; every connected provider is listed under Related Docs with its setup guide.

Each stored file stays associated with the integration it came from, so switching the attachment destination does not move or re-import existing files.

Choose a storage provider in the New Integration wizard.
  1. Open Integrations → Storage.
  2. Select New Integration and choose a provider.
  3. Enter a Name and the provider-specific credentials or authorization details, then select Save & Continue.

You need permission to create integrations; without it, the New Integration control is not shown.

New integrations are created as Active, and the status field is not editable while creating. You can change the status later by editing the integration.

  1. Review the connection checks on the Verify step.
  2. Resolve any warnings, then select Done.
  3. Confirm that the integration appears as Active and is available under Storage location.

Under Storage location, choose Platform storage or one of your connected integrations. The selected location receives new uploads; files already stored elsewhere stay where they are and remain available.

Use the Attachments section to search the account-wide library and filter the Storage column by location. In message templates, select attachments from Your files or Connected storage. In the drag-and-drop email builder, select Choose an image, then use Your images, Connected storage, From URL, or Upload. Every option except From URL creates or reuses a public copy at the selected Email image location so the image can load in inboxes. Email image location is separate from Storage location. Changing it affects only newly published images; existing published images stay at their original location.

With an external integration selected, Fall back to platform storage decides what happens when that service is unreachable. Leave it enabled to keep uploads working; disable it and uploads fail instead of being stored on the platform.

Choose where new attachments are stored and whether uploads fall back to Platform Storage.
Manage connected storage integrations and files stored in Platform Storage and Amazon S3.

Before deleting or unpublishing a file, check how it is used. Removing a linked cloud file deletes only the Drip Drop reference and any public copy; the original remains. Removing an app-uploaded file from connected cloud storage also removes the cloud file; OneDrive may place it in the recycle bin, and cleanup can take a short time. Unpublishing removes the public copy, so templates and previously sent emails that embed it show a broken image.

Google Drive and OneDrive use Disconnect instead of Delete. If either is the active storage location, switch to Platform storage or another active integration first. Disconnecting preserves cloud files and attachment references, but the files remain unavailable until you Reconnect; dependent flows are paused. Other storage integrations use Delete and cannot be deleted while selected or while they still hold attachments. Switch storage and remove those attachments first.

An integration that is not Active cannot be chosen as the storage location. Fix or reconnect it first.

Amazon S3, Cloudflare R2, DigitalOcean Spaces, Backblaze B2, Wasabi Hot Cloud, Telnyx Storage, and S3-Compatible Storage can serve public email images from a bucket you manage. Google Drive, OneDrive, and Dropbox cannot.

  1. Open the saved integration and expand Serve email images from this bucket.
  2. Enter the Public Base URL and a separate Public Folder. Keep the public folder separate from the attachment folder.
  3. Select Verify public access.
  4. After verification passes, enable Available as a public media location.
  5. Return to Storage. Under Email image location, choose the verified bucket.

Verification confirms that the Public Folder can be read without signing in. It also warns if the private attachment folder is public. If connection or public-media settings change, the verification becomes stale. Select Verify public access again before using the bucket.

Public copies stored in your bucket do not count against platform storage quota. If the selected bucket cannot be used when an image is published, publication fails. Fall back to platform storage applies to attachment uploads and does not switch public-image publication to Platform storage.

An integration cannot be selected as the storage location
  • Only an Active integration can receive uploads. Open the integration and fix or reconnect it first.
  • For an OAuth integration, reauthorize the same account that was connected originally.
An integration cannot be deleted
  • An integration that is the selected storage location cannot be deleted. Choose a different location first.
  • An integration that still holds attachments cannot be deleted. Remove those attachments, then delete it again.
  • Deleting an integration does not delete the files. They stay in the storage service, and Drip Drop loses access to them.
A file is not visible in the attachment library
  • Confirm you are looking at the integration the file was uploaded to; files stay associated with the integration that stored them.
  • For object storage, confirm the file is in the configured bucket and beneath the configured Key Prefix. Changing the prefix changes what Drip Drop can list; it does not move existing files.
  • For OAuth storage, confirm the connected account can still open the file.
An upload fails
  • If an external integration is selected and Fall back to platform storage is disabled, uploads fail whenever that service is unreachable. Enable the fallback, or restore access to the service.
  • Check the integration’s own page for connection requirements and recovery steps.
A bucket cannot be selected as the email image location
  • Open the saved integration and confirm it is Active.
  • Expand Serve email images from this bucket and confirm the Public Base URL and Public Folder.
  • Select Verify public access. After Publicly readable appears, enable Available as a public media location.
  • Return to Storage and choose the bucket under Email image location.
Public-access verification became stale
  • Connection or public-media settings changed after the last successful verification.
  • Open the integration, expand Serve email images from this bucket, and select Verify public access again.
  • After Publicly readable appears, confirm Available as a public media location is enabled.
The private attachment folder is publicly accessible
  • Verification found that files in the private attachment folder can be read without signing in.
  • Limit the bucket or CDN policy so anonymous access applies only to the Public Folder. Keep the attachment Key Prefix private.
  • Select Verify public access again and proceed after the warning clears.
A public image cannot be published
  • Confirm the selected integration is Active, remains enabled as a public-media location, and its Public Folder is still publicly readable.
  • Public-image publication has no automatic platform fallback. Restore and reverify the selected bucket, or select Platform storage under Email image location.
  • Fall back to platform storage applies only to attachment uploads.
  • Amazon S3 — store attachments and images in an AWS bucket you manage.
  • Cloudflare R2 — connect an R2 bucket using an Account ID and the auto region.
  • Backblaze B2 — connect a B2 bucket through its S3-compatible API.
  • DigitalOcean Spaces — connect a Space using its datacenter region.
  • Wasabi Hot Cloud — connect a Wasabi bucket using its storage region.
  • Telnyx Storage — connect a Telnyx Cloud Storage bucket with a single API key.
  • S3-Compatible Storage — connect any other service that provides an S3-compatible API.
  • Google Drive — authorize a Google account and choose files through the Google Picker.
  • OneDrive — authorize a Microsoft account to store and select files.
  • Dropbox — authorize a Dropbox account; uploads go to a dedicated app folder.
  • Message Templates — create email content and use stored files as attachments or images in email templates.