Resources · Make integration

ZapSign Make integrationAutomate ZapSign with Make.

What if every signature in ZapSign started the next task by itself? The ZapSign Make integration gives you 6 modules: 3 instant triggers and 3 actions. This page shows how to link your account and build a first scenario around a signed document.

Try the ZapSign integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ZapSign Make integration do for you?

The ZapSign Make integration lets Make react when a document is created, deleted or signed in ZapSign, and lets it create documents with their signers for you. You build a scenario, the automation made of modules (each module is one brick: a trigger or an action), and Make runs it without any code.

Signed quote, contract on its way. Put Watch Document Signed first, then Create a Document via Template: the moment a client signs your quote, ZapSign prepares the contract from your model and adds its signers, with nobody copying names by hand.

A PDF from another tool, sent for signature. When another app in your scenario produces a PDF, Create a Document via Upload turns that file into a ZapSign document with its signers. A sales team can send an offer letter or a lease this way, straight from the tool that wrote it.

A clean trail of what changed. Watch Document Created and Watch Document Deleted tell Make about each new or removed document, so a tracking sheet or a team channel stays in step with ZapSign.

What the listed modules do not cover, such as another call of the ZapSign API, goes through Make an API Call with the same connection. The Make documentation for ZapSign lists no specific limit. If you also look at n8n, the n8n vs Make comparison lays out the criteria, and the Make review walks through the editor itself. To get your team trained on scenarios, see Make training.

Connect

How do you connect ZapSign to Make?

  1. 01

    Copy your API token in ZapSign

    You need an active ZapSign account. In ZapSign, open Settings, click Integrations, then ZAPSIGN API, and copy the API token shown on screen. Keep it at hand for the next step.

  2. 02

    Add a ZapSign module and create the connection

    In your Make scenario, add any ZapSign module and click Create a connection. A connection is your ZapSign account linked to Make once, then reused by every ZapSign module. You can give it a clear label in Connection name.

  3. 03

    Paste the token and save

    Paste the API token you copied, or follow the on-screen instructions, then save. From now on every ZapSign module in your scenarios can pick this connection from the list instead of asking for the token again.

First scenario

Your first scenario with ZapSign and Make

GoalWhen a client signs a quote in ZapSign, Make creates the contract from your template, with its signers already attached.

  1. 01

    Create an empty scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Search for ZapSign and pick Watch Document Signed.

  2. 02

    Set up the webhook and the connection

    Click Create a webhook, then Create a connection and paste your API token. From here, ZapSign calls Make through that webhook as soon as a document gets signed.

  3. 03

    Add the contract step

    Click the + on the right of the trigger and choose Create a Document via Template. Fill its fields and map the data received from the signed quote, so the contract picks up the right client.

  4. 04

    Test it with a real signature

    Click Run once, then sign a test document in ZapSign. Make shows the bundles, the items passed from one module to the next, that each module received. Check that the contract looks right.

  5. 05

    Switch the scenario on

    Save and switch the scenario on. Since the trigger is instant, there is no interval to set: each new signature runs the scenario, and every module that runs counts as one operation on your plan.

Triggers

What can start a ZapSign scenario?

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

ZapSign1Watch Document Created

Watch Document Created

Instant trigger

In Make“Triggers when a document is created.”

Hands your scenario each document the moment it appears in ZapSign, so the rest of your stack learns about it without anyone passing the news along. Every new document arrives as one bundle you can map into the next module.

How it fires
instant: ZapSign calls Make through a webhook as soon as the document is created.
When to use it
a legal or sales team wants a log line or a team message each time someone prepares a document for signature.
Watch out
each document sent through the scenario is one bundle, and every module that handles it afterward counts as one operation on your Make plan.
ZapSign2Watch Document Deleted

Watch Document Deleted

Instant trigger

In Make“Triggers when a document is deleted.”

Lets Make know when a document disappears from ZapSign, so a tracker, a CRM record or a shared sheet can be tidied up instead of pointing at something that no longer exists.

How it fires
instant: ZapSign calls Make through a webhook as soon as the document is deleted.
When to use it
an agreement was withdrawn before signature and the matching deal or row in another tool should be closed or flagged.
Watch out
when you add this module, click Create a webhook before Create a connection, otherwise the trigger has no address for ZapSign to call.
ZapSign3Watch Document Signed

Watch Document Signed

Instant trigger

In Make“Triggers when a document is signed.”

Starts your scenario the instant a document gets signed, which is usually the event that matters most: the deal is done, the paperwork can move on, and the next person can be told right away.

How it fires
instant: ZapSign calls Make through a webhook as soon as the document is signed.
When to use it
after a client signs, you want the contract drafted, the onboarding started or the finance team warned without checking ZapSign.
Watch out
test it with Run once and a real test signature, since the module has nothing to show until ZapSign actually sends an event.
Modules

What can Make do in ZapSign?

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

ZapSign1

Create a Document via Template

Action

In Make“Creates a document and its signers from a Template.”

Produces a ready-to-sign document from one of your ZapSign templates, with its signers attached, so recurring agreements come out consistent every time.

When to use it
your contract, NDA or onboarding form always follows the same model and only the client details change.
Watch out
the template has to exist in ZapSign first; if the wording changes for each client, Create a Document via Upload suits better.
ZapSign2

Create a Document via Upload

Action

In Make“Creates a document and its signers from a PDF.”

Takes a PDF made elsewhere and turns it into a ZapSign document with its signers, ready to be signed without opening ZapSign at all.

When to use it
another app in your scenario already writes the PDF, like a proposal tool or a document generator, and you only need the signature part.
Watch out
the file must reach this module from an earlier module; on the Free plan, Make handles files up to 5 MB.
ZapSign3

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

Reaches any endpoint of the ZapSign API from your scenario with the same connection, which covers everything the five other modules do not offer.

When to use it
you need a ZapSign operation that has no dedicated module and you are comfortable reading the ZapSign API documentation.
Watch out
Make will not build the request for you, so the path and body come from ZapSign's own API reference.
Need help

Need help automating ZapSign with Make?

A person reads every message.

FAQ

ZapSign and Make: common questions

01Is the ZapSign Make integration free?
Yes, on the Make side. ZapSign is a standard app, so it is available from the Free plan onward. That plan allows 2 active scenarios, a scheduled run at most every 15 minutes, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) remove the cap on active scenarios and count usage in credits each month. ZapSign itself needs its own active account and API token; its pricing page explains the subscription.
02What do you need to connect ZapSign to Make?
You need an active ZapSign account and its API token. In ZapSign, go to Settings, then Integrations, then ZAPSIGN API, and copy the token displayed. In Make, add a ZapSign module, click Create a connection, give it a name if you like and paste the token. For one of the three instant Watch modules, click Create a webhook first, then Create a connection. The connection is saved once and reused by every ZapSign module you add later.
03Does the ZapSign trigger in Make react in real time?
Yes. All three ZapSign triggers, Watch Document Created, Watch Document Deleted and Watch Document Signed, are instant: ZapSign calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. That is why each of them asks you to create a webhook before the connection. You do not set an interval for these triggers; you only switch the scenario on, and each event runs it once.
04What if the ZapSign module you need is missing in Make?
Use Make an API Call. It is part of the ZapSign app in Make and lets you call any endpoint of the ZapSign API with the connection you already set up, so you are not limited to the two document creation actions and the three triggers. You write the request yourself from the ZapSign API documentation. The Make documentation for ZapSign lists no specific limit to plan around, so the main thing to check is the ZapSign API reference.
05Should you use Make or n8n for ZapSign?
It depends on your criteria. In Make, ZapSign comes with 6 modules, three of them instant triggers, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node too, so check what that node covers for your use case before choosing. Compare the modules each tool offers for ZapSign, how you prefer to build, and which tool the rest of your automations already run on.
Same platform

Other docs you might need on this stack.

Browse all integrations