Integrations Overview

Connect DocSpring to your apps and automation workflows to generate PDFs and Word documents, collect signatures, and store completed documents.

Getting started

For third-party apps, create a DocSpring API token and enter its token ID and secret in the app’s connection settings. Cloud storage (AWS S3 and S3-compatible storage, Google Drive, Dropbox and Box) and email actions are configured in DocSpring, under Integrations. AI assistants connect to DocSpring’s MCP server and sign in to DocSpring instead of using an API token.

On the free Developer plan, an account can have 2 active integrations: storage destinations, webhooks (including the ones Zapier, Make and n8n create for their triggers) and Slack notifications. Paid plans have no limit. API tokens and AI assistants aren’t integrations themselves, but the webhooks an assistant creates count.

Manage integrations (US)Open the integration catalog and manage your storage connections

Manage integrations (EU)Open the integration catalog and manage storage connections for your EU account

API token setupCreate credentials for connecting an app to your DocSpring account

Available integrations

AWS S3Automatically upload generated PDFs and Word documents to your own Amazon S3 bucket

S3-compatible storageUpload to Cloudflare R2, Google Cloud Storage, Backblaze B2, Wasabi, DigitalOcean Spaces or MinIO

Google DriveSave generated PDFs and Word documents to a folder in your Google Drive or a shared drive

DropboxSave generated PDFs and Word documents to a folder in your Dropbox, including team folders

BoxSave generated PDFs and Word documents to a folder in your Box account

BubbleInstall the DocSpring plugin to fill PDF templates and collect signatures from your Bubble app

ZapierAccept the beta invite to generate PDFs and start signing workflows from your Zaps

MakeInstall the DocSpring app to generate PDFs and start signing workflows from your Make scenarios

n8nInstall the DocSpring community node to generate PDFs and automate signing in n8n

Node-REDAdd PDF generation and signing actions to your Node-RED flows

ParabolaUse the Send to DocSpring step to turn rows of data into filled PDFs

OttoKitGenerate PDFs, collect signatures and start workflows from DocSpring events in OttoKit

EmailEmail each new PDF to the people who filled in the form, or to your team, for every template or the ones you choose

SlackPost a message to a Slack channel whenever a template generates a PDF or a Word document

AI assistants

These assistants connect to DocSpring’s MCP server. Each card goes to its setup steps.

ClaudeSet up templates, fill them in and create signature requests from Claude.ai, Claude Desktop and Claude's mobile apps

ChatGPTFill PDF templates and create signature requests from ChatGPT in Business, Enterprise and Edu workspaces

Claude CodeSet up templates, generate types for their data and make test PDFs while Claude Code writes your integration

CodexSet up templates, generate types for their data and make test PDFs while Codex builds your integration

CursorAdd DocSpring to Cursor in one click and give its agent DocSpring's tools

VS CodeAdd DocSpring to VS Code in one click and give its agent DocSpring's tools

When an integration fails

AWS S3, Google Drive, Dropbox and Box integrations upload each PDF in the background. When an upload fails, the submission’s actions array shows the upload with state: "failed" and an error_message, and the integration’s page in DocSpring shows it as failing, with the last error.

An upload that fails because of a problem on DocSpring’s side, or a timeout or an error at Amazon S3 itself, shows state: "error" instead. DocSpring retries it, and it doesn’t count as a failure of your integration.

• Retries: uploads that fail for a reason that can go away by itself (a timeout, a rate limit, an error at the storage provider, or an S3 bucket policy that denies access) are retried automatically. Others, such as a wrong access key or a deleted folder, aren’t retried.
• Emails: DocSpring emails the account’s billing user when an integration starts failing: on the first failure that needs you to fix something, or on the second failure in a row otherwise (at most one of these emails a day). If uploads are still failing a day later, you get a second email. Each email shows the last error and the last submission that failed to upload. To stop these emails for an integration, turn off Email failure alerts in its settings.
• Automatic disabling: if an integration’s uploads have been failing continuously for 3 days, DocSpring disables it and emails you. Saving the integration’s settings or reconnecting it starts the count again. While it’s disabled, PDFs aren’t uploaded, and they aren’t uploaded later when you turn it back on. Disabling sends an account_integration.updated webhook event.
• Turning it back on: fix the problem, then open the integration’s settings, turn on Enabled and save. Any successful upload clears the failing state.

Build your own integration

Use the REST API or an official client library to generate PDFs and Word documents from your application. Webhooks notify your app when documents finish processing or signing events occur.

API client librariesUse Ruby, Python, JavaScript, TypeScript, PHP, C#, Java, Go, Elixir, or Rust

WebhooksReceive notifications from DocSpring in your own application