Resources · Make integration

DigiSign Make integrationAutomate DigiSign with Make.

Can Make handle your DigiSign envelopes for you? The DigiSign Make integration gives you 13 modules: 2 triggers and 11 actions. This page is for teams that send documents for signature, and it walks you from the connection to a first working scenario.

Try the DigiSign integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DigiSign Make integration do?

The DigiSign Make integration links your DigiSign account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or fetches something. With it, envelopes can be built, sent and collected without anyone clicking through DigiSign by hand.

Signed files that file themselves. Watch Completed Envelopes spots envelopes that reach the end of signing, and Download a Document pulls the file so the next module can store it wherever your team keeps contracts.

Envelopes built from your data. When a deal closes in another app, Create an Envelope, Add Document, Add Recipient and Send an Envelope can prepare and send the paperwork in one run, with Add Signing Tags to a document placing where each person signs.

A trail you can follow. Watch Events brings DigiSign activity into Make, and Get Envelope reads the current state of an envelope before you decide what happens next.

Be aware of one real limit: Make's own documentation for DigiSign is marked as limited, with no module descriptions and no connection guide. The notes below stay close to what each module name says, and Make an API Call covers what the listed modules miss. If you are weighing tools, the n8n vs Make comparison sets the criteria side by side, the Make pricing page explains plans, and the Make training helps when you start from zero.

Connect

How do you connect DigiSign to Make?

  1. 01

    Open the connection window

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

  2. 02

    Name it and authorize Make

    Give the connection a name if you manage several accounts, which is optional. Then either approve Make on the DigiSign page that opens or paste the key DigiSign gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Once the connection exists, Make can read your DigiSign data and propose values in the module fields, so a filled list is a good sign the link works.

First scenario

Build your first scenario with DigiSign

GoalWhen an envelope is completed in DigiSign, Make downloads the signed document and hands it to the next module.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add your first module. Search for DigiSign and choose Watch Completed Envelopes.

  2. 02

    Link your account

    Click Create a connection and follow the three connection steps above. The module then shows the fields it needs, with values Make can read from DigiSign.

  3. 03

    Add the download

    Click the + on the right of the trigger and pick Download a Document. Map the envelope data from the trigger into its fields so Make knows which file to fetch.

  4. 04

    Test with Run once

    Complete a test envelope in DigiSign, then click Run once. Open the bubble above each module to read the bundles it received, that is, the items passed from one module to the next.

  5. 05

    Schedule and switch on

    Click the clock on the trigger to set the schedule, every 15 minutes by default, then turn the scenario on. Add a storage module after the download whenever you are ready.

Triggers

What can start a DigiSign scenario?

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

DigiSign1Watch Completed Envelopes

Watch Completed Envelopes

triggerIn the docs only

This trigger hands your scenario the envelopes that have finished their signing round, so everything after it works on final paperwork only. Make's documentation lists it without a description, so its exact behavior comes from its name and should be confirmed with a test.

How it fires
it is a scheduled trigger, so Make checks DigiSign on the scenario's schedule rather than being told the moment an envelope closes.
When to use it
you want every signed contract downloaded, archived or reported without waiting for someone to notice it.
Watch out
each envelope it returns runs the rest of the scenario, and every module run counts as an operation on your Make plan.
DigiSign2Watch Events

Watch Events

triggerIn the docs only

Pick this one to feed DigiSign activity into Make rather than only finished envelopes, which opens the door to follow-ups while a signature is still pending. Which events it reports is not described in Make's documentation, so run it once and look at the bundles before you build on it.

How it fires
scheduled, meaning Make polls DigiSign at the interval set on the scenario's clock.
When to use it
a sales lead wants a message in the team chat as an envelope moves forward.
Watch out
a broad feed can produce many bundles, so add a filter before any costly module.
Modules

What can DigiSign do inside a scenario?

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

DigiSign1

Add Document

ActionIn the docs only

Attaches one file to an envelope, so the paper people must sign actually travels with it. It fits right after Create an Envelope, fed by a file from a drive or a form upload.

When to use it
a single contract or quote needs signing and the file already exists earlier in the scenario.
Watch out
the documentation gives no accepted formats or size limits, so test with a real file first.
DigiSign2

Add Multiple Documents

ActionIn the docs only

Saves you from repeating Add Document when an envelope holds a whole bundle of papers, such as a contract plus its annexes. Its name points to several files handled in one module run.

When to use it
an onboarding pack groups several documents that must be signed together.
Watch out
how it expects the list of files is not documented, so check the fields Make displays before mapping anything.
DigiSign3

Add Multiple Tags

ActionIn the docs only

Places several tags in one go, which keeps the scenario short when a document needs many marks. Make does not describe what a DigiSign tag covers here, so compare the fields with Add Tag in the editor.

When to use it
a template with many fields to place on every generated document.
Watch out
map carefully, since one wrong entry can misplace every tag of the run.
DigiSign4

Add Recipient

ActionIn the docs only

Puts a person on an envelope so DigiSign knows who should receive and sign it. Chain it once per signer, fed by contact details coming from your CRM or a form.

When to use it
a customer and an internal approver both have to sign the same agreement.
Watch out
add every recipient before Send an Envelope, since the documentation says nothing about changing recipients after sending.
DigiSign5

Add Signing Tags to a document

ActionIn the docs only

Marks where signers act on a document, so nobody has to open DigiSign and drag fields by hand. It belongs between Add Document and Send an Envelope.

When to use it
generated contracts always carry their signature spot in the same place.
Watch out
Make publishes no description for this module, so run it once on a test document and open the result in DigiSign to confirm the placement.
DigiSign6

Add Tag

ActionIn the docs only

Adds a single tag, the lighter option when only one mark matters, while Add Multiple Tags handles longer lists. Because the documentation does not define a tag for DigiSign, read the fields Make shows before relying on it.

When to use it
one extra mark added depending on a condition checked earlier in the scenario.
Watch out
each run costs one operation, so avoid looping it where Add Multiple Tags would do.
DigiSign7

Create an Envelope

ActionIn the docs only

Opens the container that later holds documents and recipients, the starting point of any automated sending. Everything else in the sending chain refers back to the envelope it creates.

When to use it
a deal marked as won in another app should turn into a signature request without manual work.
Watch out
creating is not sending; nothing reaches signers until Send an Envelope runs.
DigiSign8

Download a Document

ActionIn the docs only

Brings a file from DigiSign into your scenario, ready for a storage or email module to take over. Paired with Watch Completed Envelopes, it gets the signed copy out of DigiSign automatically.

When to use it
every signed agreement must land in the shared drive where finance looks for it.
Watch out
the Free plan of Make caps files at 5 MB, so a heavy signed file may need a paid plan.
DigiSign9

Get Envelope

ActionIn the docs only

Reads one envelope as it stands right now, so later modules can decide based on real information. Use it when a trigger or another app gives you an envelope reference but not its full details.

When to use it
before a reminder, confirming whether an envelope is still waiting for signatures.
Watch out
the returned data is not documented, so read the bundle after Run once before mapping.
DigiSign10

Make an API Call

ActionIn the docs only

Reaches any endpoint of the DigiSign API from your scenario, reusing the same connection, when none of the listed modules does the job. It is the fallback for the gaps a limited documentation leaves.

When to use it
you need an action DigiSign offers that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the DigiSign API reference open next to the module.
DigiSign11

Send an Envelope

ActionIn the docs only

Releases the prepared envelope to its recipients, the moment signers actually hear about it. Place it last, after documents, tags and recipients are in.

When to use it
closing a chain that builds the envelope from data collected in a form or a CRM.
Watch out
once people receive it, a test run is no longer silent, so try it on an envelope addressed to yourself first.
Need help

Need help automating DigiSign with Make?

A person reads every message.

FAQ

Questions about DigiSign and Make

01Is the DigiSign Make integration free?
Yes, DigiSign 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 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, remove the cap on active scenarios and count usage in credits each month. Your DigiSign subscription is a separate matter that Make does not cover.
02What do you need to connect DigiSign to Make?
A DigiSign account and a Make account are enough according to what Make publishes, since the documentation lists no specific prerequisite. You add a DigiSign module, click Create a connection, optionally name it, then authorize Make on the DigiSign page or paste the key DigiSign provides, and click Save. The connection is then shared by every DigiSign module in your scenarios, so you only do this once per account. If a module later shows empty lists, reopen the connection first.
03Do DigiSign triggers in Make fire in real time?
No. Make lists both DigiSign triggers, Watch Completed Envelopes and Watch Events, without a description, and their names point to scheduled triggers: Make checks DigiSign on the schedule set on the first module. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans go down to 1 minute. An envelope completed in between is picked up on the next check rather than the second it closes. Confirm the clock badge on the module.
04What if a DigiSign module is missing in Make?
It depends on the action, but Make an API Call is the first answer. It calls any endpoint of the DigiSign API with the connection you already have, so an operation DigiSign supports but Make does not list stays within reach. Keep in mind that Make marks its DigiSign documentation as limited, with no module descriptions, so testing each module with Run once before building on it is the safer habit.
05Should you use Make or n8n for DigiSign?
It depends on how you like to work. Make covers DigiSign with 13 modules, 2 of them scheduled triggers, and a visual editor where each step is a bubble you connect. DigiSign may also exist as an n8n node, so compare the actions each tool lists for DigiSign, how you prefer to build, and where your other apps already live. Neither tool is ranked here: the right choice is the one whose modules match the envelopes you actually send.
Same platform

Other docs you might need on this stack.

Browse all integrations