Cloud Storage Attachments for Email Templates

Cloud Storage Attachments is coming soon for email templates. The planned experience will connect supported storage providers so teams can upload eligible files, select existing files where supported, and include them with template-based emails.

Key Capabilities

Supported storage providers

Planned connectors include Amazon S3, Google Drive, Microsoft OneDrive, and Dropbox.

Direct upload

Upload an eligible file to the selected connected provider while adding it to an email template.

Existing-file selection

Browse and select eligible existing files from S3, OneDrive, or Dropbox.

Limited Google Drive access

Use an upload-only workflow designed around Google Drive’s limited file permission model.

Template-based attachments

Associate files with email templates for retrieval when the template is sent.

Storage fallback

Optionally fall back to platform storage after an external upload failure when quota is available.

Attachment safeguards

Validate file type, file size, attachment count, and combined attachment size.

Customer-owned S3 storage

Use a configured customer bucket and prefix for planned S3 attachment storage.

How It Works

1

Connect storage

Connect a supported storage provider through the provider settings experience.

2

Choose primary storage

Select an active connected provider for new attachment uploads and configure fallback behavior where available.

3

Add an attachment

Upload an eligible file while editing an email template.

4

Select an existing file

For supported browse-capable providers, choose an eligible file already stored there.

5

Validate the file

Check ownership, storage access, file type, file size, attachment count, and combined size.

6

Send the template

Retrieve the attachment from its storage location when the template-based email is sent.

7

Handle storage errors

Use configured fallback only when available, or stop the attachment from being used if retrieval fails.

Use Cases

Keep template-based proposals, brochures, forms, or reports in connected storage.
Use a dedicated Amazon S3 bucket and prefix under customer-managed AWS access policies.
Reuse eligible files from OneDrive, Dropbox, or S3 during email-template setup.
Upload Google Drive files through a limited-access workflow without broad Drive browsing.
Keep recurring email-template attachments associated with their external storage location.

Email attachments often need to stay alongside the systems and controls a team already uses. Cloud Storage Attachments is being developed to connect email-template attachments with supported external storage providers.

The planned provider set includes Amazon S3, Google Drive, Microsoft OneDrive, and Dropbox. Depending on the provider, teams will be able to upload a file while adding it to an email template or browse connected storage and select an eligible existing file.

Attachments will remain subject to validation and send-time retrieval. This capability is intended specifically for email-template attachments. It is not planned as a general file manager, a cloud-storage synchronization product, or an attachment system for every product surface. Provider availability and final behavior may change before release.

Why teams build on Drip Drop

Drip Drop is bring-your-own-account automation: you keep your own sending reputation, pricing, and data, and Drip Drop handles the flows, templates, contacts, and reporting on top — no marked-up credits, no lock-in.

Frequently Asked Questions

Is Cloud Storage Attachments available now?

No. The storage connectors are hidden and marked in development. This page describes planned functionality.

Which providers are planned?

Amazon S3, Google Drive, Microsoft OneDrive, and Dropbox. Final provider availability may change before release.

Can I browse my entire Google Drive?

No. The planned Google Drive connector uses a limited permission model and is designed as upload-only in the attachment interface.

Can I select existing files from connected storage?

The planned S3, OneDrive, and Dropbox workflows support browsing eligible existing files. Google Drive is designed differently.

Will files always be copied into Drip Drop?

The planned primary location is the selected external provider. An optional platform-storage fallback may be used only after an upload failure and when quota is available.

What file types and limits will be supported?

The implementation includes common document, spreadsheet, presentation, text, archive, calendar, JSON, and image formats, plus size and count limits. Final launch limits may change.