Resources · Make integration

Docusign Make integrationAutomate Docusign with Make.

What if every signed envelope filed itself the moment the last person signed? The Docusign Make integration gives you 52 modules, 27 of them triggers, to send, track and download agreements without code. This guide walks ops and sales teams through the connection and a first working scenario.

Try the Docusign integration on MakeSee the 52 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Docusign Make integration do for you?

The Docusign Make integration links your Docusign account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Docusign events start the scenario, and Docusign actions send, void or download envelopes for you.

Signed contract, filed without anyone touching it. Watch Envelope Completed spots the envelope once every recipient has finished, and Download a Document pulls the signed file so the next module can store it wherever your team keeps contracts.

Quotes that leave for signature on their own. When a deal is won in your CRM, Send a Document from Template to Sign builds the envelope from a saved template. For one agreement going to a long list of people, Create Bulk Send List, Add to Bulk Send List and Bulk Send Envelope from Template do the heavy lifting.

Stalled signatures flagged early. Watch Recipient Auto Responded warns you when the invitation email bounced, and Watch Envelope Declined tells sales which deal needs a call.

Some limits come straight from the doc. Watch Docusign Connect Event hands its data over as XML, so a Parse XML module has to follow it. Get an Envelope Form Data needs an option switched on in Docusign first. The doc also reserves part of this setup to the Business Pro eSignature plan and higher. When a listed module falls short, Make an API Call reaches the rest of the Docusign API. Docusign may also exist as an n8n node; the n8n vs Make comparison lays out the criteria. New to the editor? Start with the Make training, or read the Make review before you commit.

Connect

How do you connect Docusign to Make?

  1. 01

    Add a Docusign module

    In your scenario, pick any Docusign module and click Create a connection. A connection is your Docusign account linked to Make once, then reused by every Docusign module you add later.

  2. 02

    Name it and authorize Make

    Give the connection a clear name, handy if you juggle a test account and a live one. Then sign in on the Docusign page that opens and allow Make to act on your account.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now list the envelopes and templates it reads from your account, so you pick them instead of typing IDs by hand.

First scenario

Your first scenario: save every completed contract

GoalWhen an envelope is completed in Docusign, Make downloads the signed document so the next step can store it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Docusign and choose Watch Envelope Completed, the scheduled version with the clock badge.

  2. 02

    Link your account

    Click Create a connection, sign in to Docusign and allow access. Make stores the connection, so the download module will reuse it without asking again.

  3. 03

    Add the download

    Click the + to the right of the trigger and add Download a Document. Map the envelope from the trigger's output so Make knows which envelope to open.

  4. 04

    Test with Run once

    Finish a test envelope in Docusign, then click Run once. Open the bubbles above each module to read the bundle it received: one envelope in, one file out.

  5. 05

    Schedule and switch on

    On the first module, set the schedule; a new scenario checks every 15 minutes by default. Switch the scenario on, then add the module of the tool where your contracts should land.

Triggers

Docusign triggers: what starts your scenario

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

Docusign1Watch Click Agreed

Watch Click Agreed

Instant trigger

In Make“Sent after a recipient accepts an elastic template.”

Starts your scenario as soon as someone accepts an elastic template, one of the agreement formats Docusign offers. You get a record of the acceptance without opening Docusign.

How it fires
instant, Docusign calls Make through a webhook as soon as it happens.
When to use it
a customer ticks your terms on a sign-up page and the account should be unlocked right away in your CRM.
Watch out
this only covers elastic templates, not classic envelopes; those have their own triggers below.
Docusign2Watch Click Declined

Watch Click Declined

Instant trigger

In Make“Sent after a recipient declines an elastic template.”

Fires when a person refuses an elastic template, so a declined set of terms never goes unnoticed. The scenario receives the refusal as a bundle, one item passed from module to module.

How it fires
instant, Docusign pings Make by webhook the moment the refusal happens.
When to use it
alert account managers when a partner rejects the updated terms, so someone follows up before access is cut.
Watch out
pair it with Watch Click Agreed if you want both outcomes tracked in one place.
Docusign3Watch Docusign Connect Event

Watch Docusign Connect Event

Instant trigger

In Make“Triggers when one of the selected events are fired in Docusign”

Listens to the events you tick in Docusign Connect, so one trigger can cover several envelope changes at once instead of one module per event.

How it fires
instant, through a webhook. The doc explains that you generate the webhook URL in Make and add it to the integration settings in Docusign.
When to use it
one scenario that routes sent, signed and voided envelopes to different branches.
Watch out
the data arrives as XML, so add the XML Parse XML module right after it before mapping anything.
Docusign4Watch Envelope Completed

Watch Envelope Completed

Scheduled trigger

In Make“Triggers when an envelope has been completed.”

Picks up envelopes that every recipient has finished, and it is the only Docusign trigger here that Make polls rather than receives. That makes it the easiest one to set up for a first try.

How it fires
scheduled, Make checks Docusign on the scenario's schedule, every 15 minutes by default.
When to use it
archiving signed contracts where a short wait does not matter.
Watch out
on the Free plan, the gap between two checks cannot go below 15 minutes.
Docusign5Watch Envelope Completed

Watch Envelope Completed

Instant trigger

In Make“The envelope has been completed by all the recipients.”

This instant twin of the previous trigger tells Make the moment the last recipient finishes the envelope, so the signed deal moves on without waiting for a polling round.

How it fires
instant, Docusign calls Make through a webhook as soon as it happens.
When to use it
kick off onboarding, invoicing or a welcome email the minute a contract is fully signed.
Watch out
both modules share the same name in Make; look for the lightning badge to be sure you picked this one and not the scheduled version.
Docusign6Watch Envelope Corrected

Watch Envelope Corrected

Instant trigger

In Make“Sent when the envelope is correctedcorrected, opens in new window within the UI or via any of the Envelopes/EnvelopesRecipients API calls.”

Reacts when a sender corrects an envelope that is already out, whether the change was made in the Docusign interface or through the API. Your records stay in line with the version recipients now see.

How it fires
instant, a webhook from Docusign reaches Make as soon as the correction is saved.
When to use it
update the contract line in your CRM when legal fixes a clause or swaps a recipient.
Watch out
it fires on corrections only; a plain resend goes through Watch Envelope Resent instead.
Docusign7Watch Envelope Created

Watch Envelope Created

Instant trigger

In Make“This event is sent when an envelope is created through the DocuSign eSignature UI or when an envelope's status is set to "created" after an Envelopes:create API call.”

Catches a new envelope as soon as it exists, whether someone built it in Docusign or an API call set its status to created. Handy for seeing drafts before they go out.

How it fires
instant, Docusign calls Make by webhook as soon as the envelope is created.
When to use it
log every agreement in a tracking sheet from day one, including ones that sales prepared by hand.
Watch out
created does not mean sent, so wait for Watch Envelope Sent before notifying the client side.
Docusign8Watch Envelope Declined

Watch Envelope Declined

Instant trigger

In Make“The envelope has been declined by one of the recipients.”

Tells you that one recipient refused to sign, which stops the whole envelope. You learn about a lost or blocked deal without refreshing Docusign.

How it fires
instant, the app calls Make through a webhook as soon as the refusal is recorded.
When to use it
post a message to the account owner and move the deal back to negotiation in your pipeline.
Watch out
this is envelope level; if you need to know which person declined, Watch Recipient Declined is the closer fit.
Docusign9Watch Envelope Deleted

Watch Envelope Deleted

Instant trigger

In Make“This event is sent after an already-sent envelope is deleted, opens in new window.”

Signals that an envelope already sent has been deleted, so your own records do not keep pointing at something that is gone from the inbox of the sender.

How it fires
instant, Docusign notifies Make by webhook once the deletion happens.
When to use it
mark the matching row as removed in your contract register and keep an audit trail outside Docusign.
Watch out
drafts removed before sending go through Watch Envelope Discard instead, so plan both if you track everything.
Docusign10Watch Envelope Delivered

Watch Envelope Delivered

Instant trigger

In Make“This event is sent when all recipients have opened the envelope through the DocuSign signing website. This does not signify an email delivery of an envelope.”

Fires once every recipient has opened the envelope on the Docusign signing site. It is the proof that everyone at least looked at the document.

How it fires
instant, the app calls Make through a webhook as soon as the last recipient opens it.
When to use it
hold off a reminder email while people are still reading, then trigger the follow-up once they have all seen it.
Watch out
delivered here has nothing to do with the email landing in an inbox; it means the envelope was opened.
Docusign11Watch Envelope Discard

Watch Envelope Discard

Instant trigger

In Make“Sent when an envelope in created or draft state is deleted or discarded within the tagging UI.”

Spots envelopes thrown away while still in created or draft state, from the tagging screen where fields get placed. Useful to clean up anything your scenario logged too early.

How it fires
instant, Docusign sends a webhook to Make as soon as the draft is discarded.
When to use it
remove the placeholder line a previous scenario added when the envelope was created.
Watch out
sent envelopes that get deleted do not show up here; Watch Envelope Deleted covers them.
Docusign12Watch Envelope Purged

Watch Envelope Purged

Instant trigger

In Make“Sent when the envelope is queued to be purged, opens in new window or via the Envelopes:update API call.”

Warns you when an envelope is queued for purge, whether from the interface or an update through the API. It is the last moment to keep a copy of the documents elsewhere.

How it fires
instant, Docusign calls Make by webhook as soon as the purge is queued.
When to use it
chain Download a Document so a copy lands in your archive before Docusign clears the files.
Watch out
the trigger only helps if the scenario is switched on when the purge is queued.
Docusign13Watch Envelope Resent

Watch Envelope Resent

Instant trigger

In Make“Sent when the envelope is resent, opens in new window within the UI or via the Envelopes:update API call.”

Lets you know that a sender pushed an envelope out again, from the interface or through the API. It shows which agreements needed a second nudge.

How it fires
instant, the app notifies Make through a webhook as soon as the resend happens.
When to use it
count resends per deal in a sheet to see which clients drag their feet before signing.
Watch out
this is about the whole envelope; a resend to a single person is caught by Watch Recipient Resent.
Docusign14Watch Envelope Sent

Watch Envelope Sent

Instant trigger

In Make“This event is sent when the email notification, with a link to the envelope, is sent to at least one recipient or when it is a recipient's turn to sign during embedded signing. The envelope remains in this state until all recipients have viewed the envelope.”

Triggers when the notification email goes to at least one recipient, or when an embedded signer's turn comes up. The envelope stays sent until everyone has viewed it.

How it fires
instant, Docusign calls Make through a webhook as soon as the first notification leaves.
When to use it
move a deal to the awaiting signature stage in your CRM without asking the rep to do it.
Watch out
sent is not signed; wait for Watch Envelope Completed before treating the deal as closed.
Docusign15Watch Envelope Voided

Watch Envelope Voided

Instant trigger

In Make“The envelope has been voided by the sender or has expired. The void reason indicates whether the envelope was manually voided or expired.”

Reports envelopes that were cancelled by the sender or simply expired. The void reason in the data tells you which of the two happened.

How it fires
instant, Docusign calls Make by webhook as soon as the envelope is voided.
When to use it
reopen the task for the rep when an offer expired unsigned, but archive it quietly when it was cancelled on purpose.
Watch out
add a filter on the void reason, otherwise expired and cancelled envelopes land in the same branch.
Docusign16Watch Recipient Auto Responded

Watch Recipient Auto Responded

Instant trigger

In Make“Sent when DocuSign gets notification that an email delivery has failed. The delivery failure could be for a number of reasons, such as a bad email address or that the recipient’s email system auto-responds to the email from DocuSign.”

Flags a failed email delivery to a recipient, caused by a wrong address or by a mailbox that answers automatically. You find the problem before the signer goes silent.

How it fires
instant, Docusign pings Make through a webhook as soon as it learns of the failure.
When to use it
ask the account owner to check the email address on file and correct the envelope.
Watch out
an out of office reply also lands here, so the address may be fine; read the data before correcting anything.
Docusign17Watch Recipient Completed

Watch Recipient Completed

Instant trigger

In Make“Sent when the recipient has completed their actions for the envelope, typically (but not always) by signing.”

Fires each time one recipient finishes their part of the envelope, usually by signing, though not always. You follow progress person by person.

How it fires
instant, the app calls Make through a webhook as soon as that recipient is done.
When to use it
in a contract that the client signs before your director, alert the director right after the client finishes.
Watch out
the doc says completion is typically, but not always, a signature, so do not log it as signed without checking.
Docusign18Watch Recipient Declined

Watch Recipient Declined

Instant trigger

In Make“Sent when the recipient declines to sign the document(s) in the envelope.”

Tells you exactly which person refused to sign the documents in an envelope. More precise than the envelope level alert when several people are involved.

How it fires
instant, Docusign calls Make by webhook as soon as that recipient declines.
When to use it
in a partnership agreement with three signers, route the alert to whoever owns the relationship with the one who said no.
Watch out
the envelope stops too, so avoid pairing it with Watch Envelope Declined in the same flow or you will get two alerts.
Docusign19Watch Recipient Delegate

Watch Recipient Delegate

Instant trigger

In Make“Sent after a Delegation rule is in place and when a delegated signer is sent an envelope within the UI or the API.”

Catches the moment a delegated signer receives an envelope because a delegation rule is set up in Docusign. You see who is really signing in place of the original contact.

How it fires
instant, the app calls Make through a webhook as soon as the delegate is sent the envelope.
When to use it
add the delegate to the client record so your team knows who to chase next time.
Watch out
nothing fires without a delegation rule in place on the Docusign side.
Docusign20Watch Recipient Delivered

Watch Recipient Delivered

Instant trigger

In Make“Sent when the recipient has viewed the document(s) in an envelope through the DocuSign signing web site. This does not signify an email delivery of an envelope.”

Fires when one recipient has viewed the documents on the Docusign signing site, before they sign or refuse. It is a reading receipt, person by person.

How it fires
instant, Docusign notifies Make through a webhook as soon as that person opens the envelope.
When to use it
give sales a heads up that the client is reading the proposal right now, a good moment for a call.
Watch out
it does not confirm that the email arrived; only that the envelope was opened on the signing site.
Docusign21Watch Recipient Marked Finish Later

Watch Recipient Marked Finish Later

Instant trigger

In Make“Sent when the recipient selects Finish Later on an envelope.”

Shows that a recipient started the envelope and clicked Finish Later. The deal is not lost, just paused, and you know about it.

How it fires
instant, the app calls Make by webhook as soon as the recipient chooses to finish later.
When to use it
schedule a gentle reminder task for the rep, tied to that client and envelope.
Watch out
the same person may come back and complete it soon after, so let the rep decide when to follow up rather than emailing automatically.
Docusign22Watch Recipient Reassign

Watch Recipient Reassign

Instant trigger

In Make“Sent when the envelope is reassigned by a recipient within the UI.”

Reacts when a recipient hands the envelope over to someone else from the Docusign interface. The new name enters the process without you hearing about it otherwise.

How it fires
instant, Docusign calls Make through a webhook as soon as the reassignment is made.
When to use it
a buyer passes the purchase order to their finance team; update the contact on the deal.
Watch out
this is the recipient's choice, unlike delegation, which follows a rule set in advance.
Docusign23Watch Recipient Resent

Watch Recipient Resent

Instant trigger

In Make“Triggered when an envelope is resent to a recipient within the web application or using the EnvelopeRecipients : update API call.”

Triggers when an envelope is sent again to one specific recipient, from the web app or through an API update. You see which person needed another reminder.

How it fires
instant, the app notifies Make through a webhook as soon as the resend goes out.
When to use it
log the reminder in the client timeline so everyone sees the history before calling.
Watch out
a resend of the whole envelope goes through Watch Envelope Resent, so choose the level you actually need.
Docusign24Watch Recipient Sent

Watch Recipient Sent

Instant trigger

In Make“This event is sent when an email notification is sent to the recipient signifying that it is their turn to sign an envelope.”

Fires when a recipient gets the email saying it is their turn to sign. In a signing order, you can follow the envelope as it moves from one person to the next.

How it fires
instant, Docusign calls Make by webhook as soon as that email is sent.
When to use it
send an internal chat message so the manager knows the contract is now waiting on them.
Watch out
an envelope with several signers can start the scenario more than once, so plan a filter.
Docusign25Watch Template Created

Watch Template Created

Instant trigger

In Make“Sent when a template is createdtemplate is created, opens in new window within the UI or via the Templates:create API call.”

Lets Make know when a new Docusign template appears, created in the interface or through the API. Your template library stays documented without extra work.

How it fires
instant, the app calls Make through a webhook as soon as the template is saved.
When to use it
add the template name and owner to a shared catalog so the whole team knows it exists.
Watch out
templates created through the API count too, so a template built by Create Template from Document may fire it; avoid loops.
Docusign26Watch Template Deleted

Watch Template Deleted

Instant trigger

In Make“Sent when a template is deleted within the UI or via the recycle bin API call recycle bin API call, opens in new window.”

Reports a template removed from the interface or through the recycle bin API. Any scenario still pointing at it would fail, so this is your early warning.

How it fires
instant, Docusign notifies Make by webhook as soon as the template is deleted.
When to use it
alert the person who maintains your sending scenarios so they swap in a new template.
Watch out
scenarios using Send a Document from Template to Sign with that template will stop working until you update them.
Docusign27Watch Template Modified

Watch Template Modified

Instant trigger

In Make“Sent when a template is modified within the UI or via the Templates:update API call.”

Fires when someone edits a template in the interface or through the API. Changes to a clause or a field no longer slip by unnoticed.

How it fires
instant, the app calls Make through a webhook as soon as the edit is saved.
When to use it
ask legal to review each change to your standard sales agreement before it goes out again.
Watch out
edits made through the API count too, so Update Template run from Make may trigger your own scenario in return.
Modules

Docusign modules: what Make can do in your account

Docusign gives you 25 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

You can have access to more resources related to this app on the following links

4 modules
Docusign1

Docusign topics on Make community

ActionIn the docs only

This entry is a link from the Make doc to community discussions about Docusign, not a module that runs in a scenario. It is where you read how other builders solved a similar setup.

When to use it
a scenario behaves oddly and you want to see whether someone already hit the same problem.
Watch out
it performs nothing and uses no operation; treat it as reading material.
Docusign2

Docusign website

ActionIn the docs only

A plain link to the Docusign website, listed by the Make doc among the resources for this app. Handy when you need to check your account settings or plan while building.

When to use it
you must switch on an option in Docusign, such as the form data download setting, before a module can work.
Watch out
this is not a module you can add to a scenario.
Docusign3

Docusign API documentation

ActionIn the docs only

Points to the Docusign API reference, the list of endpoints you can reach with Make an API Call. Think of it as the map for whatever the listed modules do not cover.

When to use it
you plan a custom call, for example the envelope search by date shown in the Make doc.
Watch out
it is documentation only; nothing runs and no operation is used.
Docusign4

Docusign page on make

ActionIn the docs only

Leads to the Docusign page in the Make app directory, which gathers the modules and templates published for this app. A quick way to double check a module name before searching in the editor.

When to use it
you want an overview of what exists before designing a scenario.
Watch out
it is a link, not something you place on the scenario canvas.

Other modules

21 modules
Docusign5

Add to Bulk Send List

Action

In Make“Adds a recipient to the bulk send list”

Adds one recipient to an existing bulk send list, so your mailing list for a mass signature grows as new contacts show up.

When to use it
each new member who registers in your form is added to the list for the annual membership agreement.
Watch out
build the list first with Create Bulk Send List, then point this module at it.
Docusign6

Bulk Send Envelope from Template

Action

In Make“Sends envelopes based on a template to multiple recipients using a bulk send list.”

Sends the same template to every recipient of a bulk send list in one go, each person getting their own envelope to sign.

When to use it
a policy update that all your franchisees must sign, prepared once and sent to the whole list.
Watch out
run Test Bulk Send List first; one bad entry is easier to fix before hundreds of envelopes leave.
Docusign7

Create Bulk Send List

Action

In Make“Creates a bulk send list”

Creates a new bulk send list in Docusign, the container that bulk sending needs before any recipient can be added.

When to use it
you start a campaign of agreements for a new event or a new batch of suppliers.
Watch out
running it inside a scenario that repeats creates a new list each time; build the list once, then use Add to Bulk Send List for the rest.
Docusign9

Create Short-lived Pre-filled Webform Link

Action

In Make“Creates a secure Session Link for the filled webform (more secure, shorter duration)”

Builds a secure session link to a pre-filled web form, valid for a shorter time. Safer than the long-lived link when the form holds personal details.

When to use it
send the link right after a call, while the client is ready to complete the form.
Watch out
the link expires, so generate it at the moment of sending rather than storing it for later.
Docusign10

Create Signing Groups

Action

In Make“Creates a signing group.”

Creates a signing group in Docusign, so an envelope can be addressed to a group rather than to one named person.

When to use it
a new office opens and its managers should be able to sign purchase orders for each other.
Watch out
check with List Signing Groups first to avoid creating a duplicate group.
Docusign11

Create Template from Document

Action

In Make“Creates a new template using a document.”

Turns a document into a new Docusign template, ready to be sent again and again without rebuilding it.

When to use it
legal drops a validated contract into a shared folder and you want it available as a template for sales.
Watch out
the new template may fire Watch Template Created; if that trigger feeds the same scenario, you risk a loop.
Docusign12

Download a Document

Action

In Make“Downloads a document from a specified envelope.”

Pulls one document out of an envelope as a file that the next module can store, attach or send on.

When to use it
right after Watch Envelope Completed, to copy the signed contract into your drive or into the client record.
Watch out
an envelope can hold several documents; run List Envelope Documents first when you need them all.
Docusign13

Get an Envelope Form Data

Action

In Make“Gets the content of an envelope form data”

Retrieves the values people typed into the fields of an envelope, in progress, completed or cancelled, from envelopes you sent or that are shared with you.

When to use it
copy the address a client entered into your billing tool.
Watch out
first go to Docusign Settings, then Sending Settings, and enable Allow sender to download form data, or Make returns a 400 permission error.
Docusign14

Get an Envelope Status

Action

In Make“Retrieves the overall status for the specified envelope.”

Returns the current overall status of one envelope, so a scenario can check where it stands before doing anything else.

When to use it
before sending a reminder from another tool, confirm the envelope is not already completed or voided.
Watch out
it reads one envelope you already know; to find envelopes by criteria, Search Envelopes is the right module.
Docusign15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Docusign API with the connection you already set up. It covers everything the listed modules leave out.

When to use it
the Make doc shows a call to /v2.1/accounts/{accountId}/envelopes/ with the from_date parameter to fetch envelopes changed since a date.
Watch out
you read the answer under Body in the output, so check the Docusign API documentation for the structure.
Docusign16

Send a Document from Template to Sign

Action

In Make“Creates and sends an envelope using a selected template.”

Creates and sends an envelope from a template you pick, so recipients get the standard agreement with the right layout and fields.

When to use it
a deal is marked won in your CRM and the client should receive your usual service agreement straight away.
Watch out
if the template is deleted in Docusign, this module fails; Watch Template Deleted can warn you.
Docusign17

Send a Document to Sign

Action

In Make“Sends an envelope with a document to be signed.”

Sends an envelope built around a document you provide, for contracts that change every time and do not fit a template.

When to use it
a quote document generated by another app in the scenario goes to the client for signature.
Watch out
the document usually comes from a previous module, so map the file from that step rather than typing anything.
Docusign18

Test Bulk Send List

Action

In Make“Tests a bulk send list”

Tests a bulk send list before anything is sent, so problems show up while they are still easy to fix.

When to use it
just before Bulk Send Envelope from Template, as a safety step in the same scenario.
Watch out
add a filter after it so the send only runs when the test passes.
Docusign19

Update Template

Action

In Make“Updates a template”

Changes an existing Docusign template from your scenario, so your templates follow the data kept in another tool.

When to use it
your pricing table changes in a spreadsheet and the matching template should reflect it.
Watch out
each update may fire Watch Template Modified; if that trigger starts the same scenario, filter it out to avoid a loop.
Docusign20

Void an Envelope

Action

In Make“Voids an envelope”

Cancels an envelope that is out for signature, so nobody can sign an offer that is no longer valid.

When to use it
a deal is lost or replaced in your CRM and the old proposal must stop being signable.
Watch out
treat it like a delete: add a filter so only envelopes tied to lost deals reach this module.
Docusign21

List Envelope Documents

Search

In Make“Lists all documents from an envelope”

Lists every document inside an envelope, each coming out as its own bundle, so the next module can handle them one by one.

When to use it
a signed envelope holds a contract plus annexes and all of them should be archived.
Watch out
each document then runs through the following modules, which uses one operation per document.
Docusign22

List Signing Groups

Search

In Make“Gets a list of the Signing Group in an account.”

Returns the signing groups defined in your Docusign account, zero, one or several, so you can pick the right one in a later step.

When to use it
before sending, look up the group for the region the client belongs to.
Watch out
when several groups come back, the modules after it run once per group unless you add a filter.
Docusign23

List Template Documents

Search

In Make“Lists template documents”

Lists the documents that make up a template, helpful to check what a recipient will actually receive.

When to use it
audit your templates and record in a sheet which files each one contains.
Watch out
it returns one bundle per document, so plan an aggregator if you want a single line per template.
Docusign24

List Templates

Search

In Make“Lists templates”

Returns the templates of your account so a scenario can find the one it needs instead of relying on a fixed ID.

When to use it
sync your template catalog into a shared table for the sales team.
Watch out
a search can bring back many templates at once, each one costing operations in the modules that follow.
Docusign25

Search Envelopes

Search

In Make“Searches for envelopes.”

Finds envelopes that match the filters you set, and hands them over one by one as separate bundles.

When to use it
rebuild a report of every envelope still waiting for a signature, then send it to the sales manager.
Watch out
no match means zero bundles and the rest of the scenario stays idle, which is normal and not an error.
Need help

Need help automating Docusign with Make?

A person reads every message.

FAQ

Docusign and Make: common questions

01Is the Docusign Make integration free?
Yes, Docusign is a standard app in Make, so its modules are available on the Free plan. That plan has limits: 2 active scenarios, at least 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) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. Your Docusign subscription is a separate matter handled with Docusign.
02What do you need to connect Docusign to Make?
A Docusign account and a Make account. You add a Docusign module, click Create a connection, sign in to Docusign and allow Make to access it, then save. If you work with your own Docusign app, the doc explains that its values go in the Integration Key (Client ID) and Client Secret fields. Two extra settings matter for some modules: the form data download option in Docusign for Get an Envelope Form Data, and the webhook URL from Make pasted into the Docusign integration settings for Watch Docusign Connect Event.
03Do the Docusign triggers react in real time?
Almost all of them do. Among the 27 Docusign triggers, 26 are instant: Docusign calls Make through a webhook as soon as the event happens, whether an envelope is sent, signed, declined or voided. The exception is the scheduled version of Watch Envelope Completed, which Make checks on the scenario schedule, every 15 minutes by default and never below 15 minutes on the Free plan. Both modules carry the same name, so look at the badge: lightning for instant, clock for scheduled.
04What if a Docusign module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Docusign API with the connection you already have, for example to search envelopes changed since a given date. Also check the known limits before building: Watch Docusign Connect Event sends XML that needs the Parse XML module, Get an Envelope Form Data returns a 400 error until form data download is enabled in Docusign, and the doc reserves part of the setup to the Business Pro eSignature plan and higher.
05Should you use Make or n8n for Docusign?
It depends on your team rather than on Docusign. In Make you get 52 ready modules, 26 of them instant triggers, plus Make an API Call for the rest, and the visual editor explained on this page. The same app often exists as an n8n node too, so compare the modules each tool offers for your exact case and pick the tool your team already knows or can maintain. No ranking here, just the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations