Resources · Make integration

DocuSeal Make integrationAutomate DocuSeal with Make.

Can Make send a document for signature and react the moment it is signed? It can: the DocuSeal Make integration offers 7 modules, 2 instant triggers and 5 actions. This page shows how to link your account and build a first scenario, with no code involved.

Try the DocuSeal integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DocuSeal Make integration do for you?

The DocuSeal Make integration links your DocuSeal account to Make so that signature requests leave on their own and signed documents kick off whatever comes next. You assemble it as a scenario, the automation you build in Make, out of modules: small bricks that either watch for an event or perform one action.

Know when a deal is really closed. Watch Submission Completed starts a scenario only once every party has signed, which is the right cue to update a sales pipeline or alert the account manager in another app.

Send agreements without opening DocuSeal. Create Signature Request from PDF takes a file produced by an earlier module and turns it into a request for the recipients you choose. Teams that write documents in Word can reach for Create Signature Request from DOCX, and those who generate text on the fly have Create Signature Request from HTML.

Follow each signer, one at a time. Watch Signing Form Completed fires for every individual who finishes the form, so a procurement team can see which supplier contact has signed while the others are still reading.

Make flags its own DocuSeal documentation as limited, for lack of public information about the app. The page therefore sticks to what each module does, and Run once stays the way to discover the fields. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and Make training helps when scenarios are new to you.

Connect

How do you connect DocuSeal to Make?

  1. 01

    Add a DocuSeal module

    In a scenario, add any DocuSeal module, Watch Submission Completed for instance, then click Create a connection. A connection is your DocuSeal account linked to Make once and reused by every DocuSeal module afterwards.

  2. 02

    Name and authorize it

    Give the connection a name if you work with more than one DocuSeal account; this part is optional. Then do what DocuSeal asks of you: authorize Make on its page, or paste the key DocuSeal gives you.

  3. 03

    Save the connection

    Click Save. Back in the module, your connection now sits in the list, and Make can offer the choices it reads from your DocuSeal account while you fill in the fields.

First scenario

Your first scenario: turn a PDF into a DocuSeal signature request

GoalWhen a PDF is ready in another app, Make turns it into a DocuSeal signature request for the right recipients.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Each module in the chain handles one job and passes its result along.

  2. 02

    Pick the source of the PDF

    Search the app that holds your document by name and choose its module. It hands the file over as a bundle, the single item that travels from one module to the next.

  3. 03

    Add the DocuSeal action

    Click the + on the right, search DocuSeal and pick Create Signature Request from PDF. Link your account with Create a connection, then map the file coming from the first module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bundles each module received and check that the PDF and the recipients arrived where you expected.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Then switch the scenario on.

Triggers

Which DocuSeal triggers can start a scenario?

2 modules start a scenario when something happens in DocuSeal. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by DocuSeal as soon as it happens.

DocuSeal1Watch Signing Form Completed

Watch Signing Form Completed

Instant trigger

In Make“Triggers when a signing form is completed by an individual signer. If there are multiple signers, the trigger will fire separately for each signer as they complete the form.”

Watch Signing Form Completed tells Make each time one person finishes their part of a DocuSeal form, so your scenario can react signer by signer instead of waiting for the whole document.

How it fires
instant: DocuSeal calls Make through a webhook as soon as a signer completes the form, and the module shows the lightning badge in the editor.
When to use it
a procurement team logging which supplier contact has already signed while the other parties are still reviewing.
Watch out
with several signers the trigger fires separately for each of them, so one document can start your scenario several times; pick Watch Submission Completed if only the final result matters.
DocuSeal2Watch Submission Completed

Watch Submission Completed

Instant trigger

In Make“Triggers when a submission is fully completed by all parties. This occurs once all signers have signed the document.”

Watch Submission Completed holds back until every party has signed and only then starts your scenario, which makes it the natural entry point for anything that needs the finished document.

How it fires
instant: DocuSeal calls Make through a webhook as soon as the last signature lands.
When to use it
an HR team moving a new hire to the next onboarding step once the employment contract carries all its signatures.
Watch out
it fires once per submission, not once per person; to follow each signer along the way, Watch Signing Form Completed is the module to use.
Modules

Which DocuSeal actions can you run in Make?

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

DocuSeal1

Create Signature Request

Action

In Make“Initiates a signature request, allowing you to send a document for signing to specified recipients.”

Create Signature Request sends a document out for signing to the recipients you name, without anyone opening DocuSeal.

When to use it
a deal marked as won in your CRM should put the agreement in front of the client without a manual step.
Watch out
the three variants below are described as one-off requests built from a PDF, HTML or DOCX; this one is not, so if your document is created inside the scenario, pick the matching variant and check its fields with Run once.
DocuSeal2

Create Signature Request from HTML

Action

In Make“Initiates a one-off submission request using the provided HTML content, allowing you to send a document for signing to specified recipients.”

Create Signature Request from HTML builds a one-off request out of HTML content you supply, useful when an earlier module assembles the text of the document rather than storing it as a file.

When to use it
a rental agency producing a lease whose clauses change for each tenant.
Watch out
the request is built for this send only; if you ship the same document again and again, the plain Create Signature Request module deserves a look.
DocuSeal3

Create Signature Request from PDF

Action

In Make“Initiates a one-off submission request from a PDF file, allowing you to send a document for signing to specified recipients.”

Create Signature Request from PDF takes a PDF file handed over by another module and turns it into a one-off signature request for the recipients you pick.

When to use it
an accounting firm whose engagement letters are already exported as PDF by another tool and only need signatures.
Watch out
on the Free plan Make handles files up to 5 MB, so a heavy scanned PDF may call for a paid plan or a lighter export.
DocuSeal4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the DocuSeal API from your scenario while reusing the connection you already created, so you are not boxed in by the listed modules.

When to use it
you need a DocuSeal operation that none of the other four actions covers.
Watch out
you describe the request yourself, and Make's documentation for this app stays thin, so test each call with Run once.
DocuSeal5

Create Signature Request from DOCX

ActionIn the docs only

Create Signature Request from DOCX starts a signature request from a Word file, as its name says; Make's documentation offers no description of this module yet.

When to use it
a legal team drafting its contracts in Word that would rather not convert them to PDF first.
Watch out
with no official description to lean on, run the scenario with Run once on a sample file and read the bundle it returns before trusting it with real contracts.
Need help

Need help automating DocuSeal with Make?

A person reads every message.

FAQ

DocuSeal and Make: frequent questions

01Is the DocuSeal Make integration free?
Yes. DocuSeal is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, allow a 1-minute interval and count usage in credits each month, one operation being one run of one module on one bundle. No price for DocuSeal itself is covered here.
02What does it take to connect DocuSeal to Make?
You need a DocuSeal account and a Make account, nothing more. Make's documentation lists no prerequisite for this app, so the generic flow applies: add a DocuSeal module, click Create a connection, optionally name it, then authorize Make on DocuSeal's page or paste the key DocuSeal provides, and click Save. The connection is created once and every DocuSeal module can reuse it afterwards, in this scenario and in the next ones you build.
03Do the DocuSeal triggers in Make react in real time?
Yes. Both DocuSeal triggers are instant: DocuSeal calls Make through a webhook as soon as the event happens, rather than Make checking on a schedule. Watch Signing Form Completed fires for each signer who finishes the form, so a document with several signers starts the scenario several times. Watch Submission Completed fires once, when every party has signed. Pick the second one when only the finished document matters to the rest of your scenario.
04What if a DocuSeal module is missing in Make?
Use Make an API Call. It exists for DocuSeal and lets your scenario call any endpoint of the DocuSeal API with the same connection as the other modules, which covers what the 5 listed actions leave out. Keep in mind that Make describes its DocuSeal documentation as limited, for lack of public information about the app, so run each new call with Run once and read the bundle it returns before you rely on it.
05Should you use Make or n8n for DocuSeal?
It depends on what you already use. On Make, DocuSeal comes with 7 ready modules: 2 instant triggers and 5 actions, including Make an API Call for the rest. The same app often has a node on n8n too, so the practical test is to check which operations each side covers for your case. The n8n vs Make comparison on this site lists the criteria without declaring a winner, and the team can help if the choice stays unclear.
Same platform

Other docs you might need on this stack.

Browse all integrations