Resources · Zapier integration

DocuSeal Zapier integrationAutomate DocuSeal with Zapier.

The DocuSeal Zapier integration gives you 2 triggers and 5 actions. Both triggers are instant, so a signed contract starts your Zap right away, even on the free plan. The actions send signature requests from a template, a PDF, a DOCX or HTML, and update signers.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the DocuSeal Zapier integration does for your contracts

The DocuSeal Zapier integration connects your e-signature tool to the rest of your stack of apps, without code. DocuSeal tells Zapier the moment a document is signed, and Zapier can also create and send signature requests in DocuSeal when something happens in another app, like a deal closing in your CRM.

Three results teams typically build. A sales pipeline that updates itself: Submission Completed fires once every party has signed, and the Zap moves the deal to won in your CRM. Contracts sent without opening DocuSeal: Create Signature Request sends a ready-made template the moment a deal reaches the right stage. Documents built from your own data: Create Signature Request From DOCX or From HTML turns content generated elsewhere into something to sign.

What Zapier does not do here: there is no search step, so a Zap cannot look up an existing request or signer by email before acting. To update a signer, you need their Signer ID, which has to come from an earlier step. And nothing deletes or archives a document from Zapier.

The good news sits in the triggers. Both are instant, so the free plan's 15-minute wait does not apply to them. For another angle, see our DocuSeal Make integration page, or the Make vs Zapier comparison.

Vocabulary

Seven Zapier terms, explained once

Read these once; the rest of the page uses them without a reminder.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap, here a form or a whole submission being signed. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that creates, sends or updates something for you, like a signature request.
Task
What Zapier bills: one action your Zap completes successfully. Your plan's monthly allowance counts these.
Instant trigger
A trigger the app reports itself, the moment the event happens. Both DocuSeal triggers are instant, marked with a lightning bolt.
Polling trigger
The opposite: Zapier checks the app on a timer and keeps only what is new. The interval then depends on your plan.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
Cost

What a DocuSeal Zap costs you

Signatures arriving are free; every action that follows is a task.

  • Free plan100 tasks a month
  • Free plan Zaps2 steps: 1 trigger, 1 action
  • Premium appNo
  • Trigger typeInstant, both triggers

The DocuSeal triggers never cost a task. Each action that succeeds counts as one, so sending one signature request is one task, and a Zap with two actions spends two per run. Failed actions are not billed. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. DocuSeal is not a premium app, so it works on the free plan.

Connect

Connect DocuSeal to Zapier

  1. 01

    Open the Apps page

    In Zapier, open the Apps page of your account and click + Add connection. That page keeps every account you link to Zapier, so the DocuSeal login you add here serves all your Zaps.

  2. 02

    Choose DocuSeal

    Search for DocuSeal by name in the dialog, select it in the results, then click Add connection. A new tab opens where DocuSeal asks you to sign in to your account.

  3. 03

    Sign in and authorize

    Log in with the DocuSeal account that owns your templates, then grant Zapier access. The connection is saved, and every DocuSeal step of every Zap can reuse it.

First Zap

Your first DocuSeal Zap: a signed contract sends the next document

GoalWhen every party has signed a contract that meets your condition, send the follow-up document from a DocuSeal template.

  1. 01

    Build the trigger

    Start a new Zap, pick DocuSeal as the app that starts it and Submission Completed as the event, then select your DocuSeal connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent completed submissions, so you can map the fields of a real signed contract in the steps that follow.

  3. 03

    Add a filter

    Click the plus icon and choose Filter. Set the field, the rule and the value so the follow-up document itself, once signed, does not pass. Without that, the Zap feeds itself. It is now multi-step.

  4. 04

    Send the follow-up

    Add DocuSeal with Create Signature Request, pick the Template to send, choose Send Email, Send SMS or both, and map the signer details from the trigger. Test the step.

  5. 05

    Publish

    Click Publish. From now on, the moment the last signature lands, DocuSeal tells Zapier and the next document goes out without anyone touching it.

Triggers

The two DocuSeal triggers

2 events start a Zap when something happens in DocuSeal, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Signing Form Completed

Instant trigger

In Zapier“Triggers when a signing form is completed.”

Starts the Zap as soon as a signing form is completed, without waiting for every party to sign the whole submission. That wait is what the other trigger is for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your onboarding team wants a Slack ping each time a new client returns their part of the contract, to start setup without waiting for the countersignature.
Watch out
if the next step must only happen on a fully signed document, pick Submission Completed instead.
2

Submission Completed

Instant trigger

In Zapier“Triggers when a submission is completed by all parties. This means that all parties have signed the document.”

Waits until every party has signed, then starts the Zap once for the whole document. This is the trigger to use when the next step should only happen on a fully executed contract.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a SaaS sales team closes the deal in its CRM and tells finance only once both sides have signed.
Watch out
a document still waiting for one signer never fires it.
Actions

The five DocuSeal actions

DocuSeal gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Signature Request From DOCX

Action

In Zapier“Creates a signature request from a DOCX file with dynamic content variables.”

Builds the request from a DOCX file whose dynamic content variables get filled with data from your Zap, so each contract carries the right names and amounts.

When to use it
a legal team keeps its contract wording in Word and wants it personalized per client.
Watch out
the number of documents and of signers are required here too.
2

Create Signature Request From HTML

Action

In Zapier“Creates a signature request from HTML content.”

Creates a document to sign from HTML content, which suits text assembled by another app or a form, without preparing any file.

When to use it
a short consent form whose wording comes straight from a Typeform answer.
Watch out
like the PDF and DOCX versions, it asks for the number of documents and signers.
3

Create Signature Request From PDF

Action

In Zapier“Creates a signature request from a PDF document.”

Turns a PDF that arrived in an earlier step into a signature request. Flatten strips the PDF's own form fields, and Merge Documents joins several files into one.

When to use it
quotes generated as PDFs by your invoicing tool need a customer signature.
Watch out
you must set the number of documents and of signers.
4

Create Signature Request

Action

In Zapier“Creates a signature request.”

Sends a signature request built from one of your saved DocuSeal templates, by email, by SMS or both. It is the simplest way to send the same contract over and over.

When to use it
every new customer signed in Stripe gets your standard terms to sign.
Watch out
the Template field is required, so the template must exist first.
5

Update Signer

Action

In Zapier“Updates signer details, pre-fills or updates field values and re-sends emails.”

Changes a signer's details, pre-fills or updates their fields, and can re-send the email or SMS. It can also require a one-time code by phone or email before the documents open.

When to use it
a customer fixes a typo in their email in your CRM and the request must follow.
Watch out
Signer ID is required and has to come from an earlier step.
When it breaks

When a DocuSeal Zap breaks

Zapier ties no help article to DocuSeal, so these are the traps every Zap shares, seen through contracts.

A DocuSeal Zap that misfires almost always does so for one of these four reasons, three of them shared with every Zap.

  • Contracts signed before the Zap are ignored

    A Zap only reacts to signatures that happen after you publish it. Documents already completed in DocuSeal never come through; catching up on them is a separate job.

  • A request that triggers itself

    If a Zap started by a signature creates a new request that gets signed in turn, each signature starts the Zap again, and tasks drain fast.

  • A bulk send floods the trigger

    Sending a large batch of contracts at once can return a huge wave of completions. Zapier's flood protection may then hold the batch back.

  • A form done is not a contract done

    Signing Form Completed fires when a signing form is completed, not when all parties are done. If the next step must wait for every signature, use Submission Completed.
Need help

Need help automating DocuSeal with Zapier?

A person reads every message.

FAQ

DocuSeal Zapier integration: frequent questions

01Is the DocuSeal Zapier integration free?
Yes, it works on Zapier's free plan, because DocuSeal is not a premium app. The free plan gives you 100 tasks a month and two-step Zaps: one trigger and one action. That covers a signed contract that updates your CRM, or a new customer who receives a contract from a template. Add a filter or a second action and the Zap becomes multi-step, which requires a paid plan. No prices are listed here because Zapier changes its grids often.
02How many tasks does a DocuSeal Zap use?
One task per successful action, nothing for the trigger. A Zap that sends a signature request for each new customer uses one task per customer. If the same Zap also posts a message in Slack, it uses two per customer, because each successful action counts separately. A signature completing in DocuSeal costs nothing on its own. A failed action is not billed, so a broken step does not drain your monthly allowance.
03Do DocuSeal triggers work in real time?
Yes. Both DocuSeal triggers are instant: DocuSeal notifies Zapier the moment a signing form or a full submission is completed, and the Zap starts right away. That holds on every plan, including the free one, because the plan interval only applies to polling triggers. In the Zap editor, you can recognize these triggers by the lightning bolt next to them. The trigger type is set by the app and cannot be changed.
04What does it take to connect DocuSeal to Zapier?
A DocuSeal account, and access to the templates and documents your Zaps will use. From the Apps page in Zapier, click + Add connection, search for DocuSeal, sign in on the tab that opens and grant access. If you plan to use Create Signature Request, build the template in DocuSeal first with the same account. Once saved, that connection is reused by every DocuSeal step of every Zap you build. Test it on a real template.
05Why does Update Signer fail with a missing Signer ID?
Because the action needs the unique identifier of the signer, and Zapier cannot find it for you. There is no search step in the DocuSeal integration, so the Signer ID must come from an earlier step of the same Zap that carries it, or from a value you kept when the request was sent. Map that field explicitly, then test with a real signer before publishing and read what the step sends back.
06What if the DocuSeal operation you need is not listed?
Then the integration does not offer it today. It has two triggers and five actions, and no search, so you cannot look up a document or a signer, nor delete or archive anything from a Zap. Check first whether one of the five actions covers the need with a different field, for example Update Signer for re-sending an email. If not, compare what other automation tools offer for DocuSeal before you build around the gap.
07Zapier, Make or n8n for DocuSeal?
Choose by criteria, not by ranking. On Zapier, DocuSeal brings two instant triggers that run straight away even on the free plan, five actions and no search step. If you need to search for documents or signers, look at the operations each tool lists for DocuSeal before you decide. Also weigh the tool your team already runs and who will maintain the setup: rebuilding working automations elsewhere has a cost of its own.
Same platform

Other docs you might need on this stack.

Browse all integrations