Backblaze B2

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

  • You already keep objects in Backblaze B2 and want Drip Drop to read and write in a bucket you already run.
  • You want S3-compatible storage with an application key you can scope to a single bucket or prefix.
  • You want Drip Drop to derive the endpoint from your account region, with no endpoint or addressing style to maintain.
  • Confirm you have a Backblaze B2 bucket and know the account region shown in the bucket’s S3 endpoint.
  • Have an application key’s Access Key ID and Secret Access Key for the account that owns the bucket.
  • Confirm the application 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 keep Drip Drop’s attachments and images under a dedicated path.
  1. Open Integrations → Storage.
  2. Select New Integration and choose Backblaze B2.
Choose Backblaze B2 in the integration wizard.
  1. Review or change the Name.
  2. Enter your Access Key ID and Secret Access Key.
  3. Enter the Bucket Name.
  4. Select the account region shown in the bucket’s S3 endpoint.
  5. Optionally enter a Key Prefix to keep Drip Drop’s attachments and images under a dedicated path.
  6. Select Save & Continue. This saves the integration in Drip Drop but does not validate the bucket.

Drip Drop derives the B2 endpoint from the Region you select: https://s3.<region>.backblazeb2.com. The form does not ask for an Endpoint URL, Addressing Style, or Encryption setting. A Backblaze B2 account is pinned to a region when the account is created, so select the region shown in the bucket’s S3 endpoint. Using another region causes signing or object-operation failures. Drip Drop requests AES-256 server-side encryption on upload.

Enter the Backblaze B2 connection settings, then select Save & Continue. The EXAMPLE_INVALID_BUCKET name is deliberately nonfunctional, and docs-example-only is an illustrative key prefix.
  1. On Verify, Credentials stored initially confirms only that credentials are present. Select Check credentials to test the connection.
  2. After the check succeeds, select Done.
  3. Confirm that Backblaze B2 appears as Active on the Storage page.
  4. Open a message template, find the Attachments section, then select Browse files → Connected storage.
  5. Choose the integration you named, select an object beneath the configured Key Prefix, then select Attach.

When Drip Drop validates the connection, it confirms bucket access by creating, reading, and deleting a temporary object beneath the configured Key Prefix. A successful result means the credentials can reach the bucket and perform the operations Drip Drop needs.

Drip Drop reads and writes only beneath the configured Key Prefix, and uploaded files are stored there under automatically generated keys. Changing the prefix later does not move existing objects; it changes the boundary that Drip Drop can browse and attach from.

Set the bucket to Public, then use the Friendly URL shown on a file’s detail page, without the file path, as the Public Base URL. This URL includes the bucket name, for example https://f003.backblazeb2.com/file/<bucket-name>.

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.

Signature or endpoint error
  • Confirm the selected Region is the account region shown in the bucket’s S3 endpoint.
  • Drip Drop derives the endpoint as https://s3.<region>.backblazeb2.com. The account’s region is fixed when the account is created, so select the region shown in the bucket’s S3 endpoint and do not substitute an AWS region.
Access denied
  • Check that the application key is scoped to the correct bucket and allows the operation Drip Drop is performing.
  • Backblaze supports bucket and file-prefix restrictions, so an otherwise valid key can still be too narrow. A key restricted to a different prefix than Drip Drop’s Key Prefix will fail.
Upload rejected
  • Confirm the bucket and application key support the S3-compatible API and that the key has write access.
  • Drip Drop requests AES-256 server-side encryption on upload; a bucket or key that rejects the encryption header will refuse the write.
A file is not visible under the Key Prefix
  • Confirm the object is beneath the configured Key Prefix. Drip Drop cannot browse or attach anything outside it.
  • Changing the prefix does not move existing objects; files stored under an earlier prefix stop appearing.
  • 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.