Resources · Make integration

VeriDoc Sign Make integrationAutomate VeriDoc Sign with Make.

What happens to a VeriDoc Sign envelope once it leaves your hands? The VeriDoc Sign Make integration gives you 8 modules: 5 triggers that watch envelopes and 3 actions. This guide shows what each one does, how to link your account, and how to build a first working scenario.

Try the VeriDoc Sign integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the VeriDoc Sign Make integration do for you?

The VeriDoc Sign Make integration links your VeriDoc Sign account to Make, a no-code tool where you build a scenario, meaning an automation made of modules chained together. VeriDoc Sign brings 8 of those modules: 5 watch your envelopes as they are created, updated, signed, cancelled or blockchained, and 3 act on them.

Follow-up on signed paperwork. Put Watch signed envelope at the start of a scenario and add a module from another app after it: your CRM, a spreadsheet or a team chat learns about the signature without anyone copying it by hand.

Envelopes that leave on their own. Reverse the flow. Let an event in another app open the scenario, then use Create an envelope from a template so the same standard document goes out each time, filled with data Make maps from the earlier module.

A clean log of what went wrong. Watch cancelled envelope feeds a list of cancelled requests, so a sales rep can call back before the deal goes cold. Get an envelope’s status answers the question "where is that envelope now?" inside a larger scenario.

Know the limit before you start: Make states that its documentation for VeriDoc Sign is incomplete, because too little public information exists about the app. Test every module with Run once and read what comes back. If something breaks, the Make troubleshooting guide helps, and Make pricing explains how operations are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect VeriDoc Sign to Make?

  1. 01

    Add a VeriDoc Sign module

    In a new scenario, click the + and search for VeriDoc Sign. Pick any of its modules, then click Create a connection. A connection is your VeriDoc Sign account linked to Make once and reused by every VeriDoc Sign module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as your team or workspace saves confusion later, especially when a colleague opens the scenario or when two VeriDoc Sign accounts end up in the same Make organization.

  3. 03

    Authorize and save

    Depending on what VeriDoc Sign offers, you either approve Make on the VeriDoc Sign page that opens or paste the key the app gives you. Then click Save. The connection now appears in the module, ready for the next one.

First scenario

Your first scenario with VeriDoc Sign

GoalWhen a deal is marked as won in another app, Make sends a VeriDoc Sign envelope built from your template.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. That first module is the trigger from your other app, for example the one that notices a won deal.

  2. 02

    Set up the starting app

    Pick that app, click Create a connection and fill its fields. Once the connection exists, Make lists the objects it can read, so you choose instead of typing.

  3. 03

    Add the envelope module

    Click the + on the right, search for VeriDoc Sign and choose Create an envelope from a template. Connect your account, then map data from the first module into the fields Make shows, so each envelope carries the right deal.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received; a bundle is one item passed along, here one deal. Check that the envelope really left.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Then switch the scenario on.

Triggers

What can start a VeriDoc Sign scenario?

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

VeriDoc Sign1Watch cancelled envelope

Watch cancelled envelope

triggerIn the docs only

This trigger hands your scenario every envelope that has been cancelled, so a withdrawn signature request stops being a silent dead end and becomes a task someone can act on.

How it fires
scheduled. Make checks VeriDoc Sign on the scenario's schedule, every 15 minutes by default, and picks up what changed since the last check.
When to use it
a sales or HR team wants to know which requests fell through, to call the person back or log the reason.
Watch out
Make's documentation for this app is incomplete, so run it once on a real cancelled envelope and read the bundle before mapping anything.
VeriDoc Sign2Watch created envelope

Watch created envelope

triggerIn the docs only

Every new envelope in your VeriDoc Sign account becomes a bundle in Make, which lets you keep a register of what was sent without exporting anything.

How it fires
scheduled. Make asks VeriDoc Sign for new envelopes each time the scenario runs, on the schedule you set on this first module.
When to use it
an office manager wants every outgoing envelope listed in a tracking sheet without typing it in.
Watch out
if your scenario also creates envelopes, this trigger will see them too; keep the two in separate scenarios so one does not feed the other.
VeriDoc Sign3Watch new blockchained envelope

Watch new blockchained envelope

triggerIn the docs only

The name says it: going by its name, this trigger returns envelopes that VeriDoc Sign has newly recorded on a blockchain. Make gives no more detail than that.

How it fires
scheduled. Make polls VeriDoc Sign at the scenario's interval, so the envelope arrives at the next run rather than the instant it is recorded.
When to use it
a compliance or legal team that archives only fully sealed documents can start its filing scenario here.
Watch out
the name is all there is to go on, so confirm with Run once which envelopes it returns before building on it.
VeriDoc Sign4Watch signed envelope

Watch signed envelope

triggerIn the docs only

Here is the trigger most scenarios start with: it gives you each envelope once it is signed, so whatever comes after the signature can happen without a manual nudge.

How it fires
scheduled. Make checks VeriDoc Sign on the scenario's schedule; on the Free plan the shortest gap is 15 minutes, on paid plans 1 minute.
When to use it
a signed quote should update the CRM, alert the account manager or open the onboarding in another tool.
Watch out
each checked envelope costs an operation, Make's unit of usage, so keep later modules lean.
VeriDoc Sign5Watch updated envelope

Watch updated envelope

triggerIn the docs only

Use this one when you care about any change to an envelope, not a single stage: it passes along envelopes that were modified, whatever the change was.

How it fires
scheduled. Make looks for updated envelopes at each scheduled run of the scenario, not the moment the change happens.
When to use it
you mirror envelopes in a spreadsheet or a database and want every row to stay current.
Watch out
it is broader than the signed or cancelled triggers, so it can send far more bundles; when only signatures or cancellations matter, pick the matching trigger instead.
Modules

What can Make do in VeriDoc Sign?

VeriDoc Sign gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

VeriDoc Sign1

Create an envelope from a template

ActionIn the docs only

You get a ready-to-send envelope built from a template you already prepared in VeriDoc Sign, with the details filled from earlier modules.

When to use it
the same agreement goes out after a form, a won deal or a new hire, and only the names change.
Watch out
do not start this scenario with Watch created envelope, or each new envelope would trigger another one.
VeriDoc Sign2

Get an envelope’s status

ActionIn the docs only

Ask VeriDoc Sign where a given envelope stands and receive the answer as data the next modules can test, so a scenario can branch on whether it is done.

When to use it
you stored an envelope reference earlier, in a sheet or a CRM record, and want to check it later inside another scenario.
Watch out
Make publishes no field list for this module, so run it once to see what it returns.
VeriDoc Sign3

Make an API Call

ActionIn the docs only

This module reaches any endpoint of the VeriDoc Sign API with the connection you already have, covering what the other seven modules leave out.

When to use it
you need an action VeriDoc Sign offers in its API but that has no ready module in Make.
Watch out
you will need the VeriDoc Sign API reference, which this page cannot give, to know which endpoint and body to send.
Need help

Need help automating VeriDoc Sign with Make?

A person reads every message.

FAQ

VeriDoc Sign and Make: frequent questions

01Is the VeriDoc Sign Make integration free?
Yes, VeriDoc Sign is a standard app, so its modules work on the Make 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, Enterprise) lower the interval to 1 minute and lift the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. Your VeriDoc Sign subscription is a separate matter this page does not cover.
02What is needed to connect VeriDoc Sign to Make?
A VeriDoc Sign account and a Make account are enough to begin. Make's documentation for VeriDoc Sign lists no prerequisites and no specific connection steps, so you follow the generic route: add a VeriDoc Sign module, click Create a connection, optionally give it a name, then either authorize Make on the VeriDoc Sign page or paste the key the app gives you, and click Save. The connection is then reused by all 8 modules, so you only do this once per account.
03Does the VeriDoc Sign trigger work in real time?
No. Make's documentation lists the 5 VeriDoc Sign triggers without detail, and going by their Watch names they are scheduled, which means Make checks the app each time the scenario runs instead of being notified the moment something happens. A new scenario runs every 15 minutes by default. On the Free plan you cannot go below 15 minutes; on paid plans the shortest interval is 1 minute. None of the triggers is instant, so if a signature must be acted on within seconds, plan for that delay or look at the VeriDoc Sign API through Make an API Call.
04What if a VeriDoc Sign module is missing in Make?
Use Make an API Call. It sends any request the VeriDoc Sign API accepts, with the connection you already set up, so you are not limited to the 3 actions and 5 triggers. You will need VeriDoc Sign's own API reference to build the request, because Make says its documentation for this app is incomplete. Test the call with Run once, read the bundle it returns, and only then map its output into the rest of the scenario.
05Make or n8n for VeriDoc Sign: which fits better?
It depends on the tool your team already works in. On Make, VeriDoc Sign comes with 8 modules and runs on the Free plan, which is enough to test the idea with a real envelope. Many apps also have an n8n node, but nothing here confirms one for VeriDoc Sign, so check the n8n node list before comparing. Pick the platform where your other apps and your colleagues already are, rather than switching for a single integration.
Same platform

Other docs you might need on this stack.

Browse all integrations