Google Drive, Dropbox, Box and S3-Compatible Storage
DocSpring can now save the PDFs it generates to a folder in Google Drive, Dropbox or Box. The S3 integration also works with S3-compatible storage now: Cloudflare R2, Google Cloud Storage, Backblaze B2, Wasabi, DigitalOcean Spaces and MinIO.
Google Drive, Dropbox and Box
Open Integrations in DocSpring, click Manage Google Drive connections, Manage Dropbox connections or Manage Box connections, and connect your account. Then choose the folder for your PDFs:
- Google Drive: a folder in your Drive or in a shared drive, chosen in Google's file picker. DocSpring can only see that folder and the files it creates there.
- Dropbox: any folder in your Dropbox, including team folders.
- Box: any folder the connected Box user can upload to.
Each PDF is uploaded as soon as it's generated, including combined PDFs. File paths are Liquid templates with the same variables as the S3 integration, such as the template name, the submission ID, the date and your metadata, and a / in a path creates subfolders. You can upload only live or only test submissions, or only the PDFs generated with certain API tokens.
Each upload is listed in the submission's actions array in the API, as a google_drive_upload, dropbox_upload or box_upload action with the file's path and ID.
Read more in the Google Drive, Dropbox and Box docs.
S3-compatible storage
When you create an S3 integration, choose your provider under Storage Provider, then enter its endpoint URL, an access key and your bucket name. The S3 integration docs show the settings for each provider.
Failure alerts
When an integration's uploads start failing, DocSpring now emails your account's billing user with the last error and the last submission that failed to upload. If the uploads keep failing for 3 days, DocSpring disables the integration and emails you again. This includes your existing S3 integrations. To stop the emails for an integration, turn off Email failure alerts in its settings.
Read more in When an integration fails.