Resources · Make integration

eSignatures Make integrationAutomate eSignatures with Make.

What if every contract went out on its own and every signature told the rest of your stack? The eSignatures Make integration gives you 6 modules: 5 instant triggers and 1 action. This guide is for sales and ops teams, and it walks you from connection to a working scenario.

Try the eSignatures integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the eSignatures Make integration do for you?

The eSignatures Make integration links your eSignatures.io account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches for an event or does a task. With it, Make can send a contract for you and hear about every step of its signing.

Contracts that leave on their own. A deal closes in the tool where your sales team works, and the Create a Contract module sends the agreement by SMS or email to the signers. Nobody copies names by hand anymore.

A clean handoff once everyone has signed. Watch Contract Signed fires when the last signer is done. That is the moment to open the onboarding task, update the customer record or warn finance, without anyone checking the dashboard.

Problems you hear about early. Watch Webhook Error Notifications reports issues such as a delivery that failed, and Watch Mobile Number Update Requested by Signer flags a signer who needs a new number. Route both to the person who can fix them.

What Make does not offer here: there is no Make an API Call module for this app, so you work with the 6 modules listed below, and the documentation gives no numeric limits. If you are still choosing a platform, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains what each plan includes. For a hands-on path, Make training starts from zero.

Connect

How do you connect eSignatures to Make?

  1. 01

    Add an eSignatures module

    In your scenario, search for eSignatures and pick any of its modules. Then click Create a connection. A connection is your eSignatures.io account linked to Make once, then reused by every module of the app.

  2. 02

    Name the connection

    This part is optional, but a clear name helps when several accounts live in the same Make organization. Something like "eSignatures sales team" tells your colleagues which account signs the contracts.

  3. 03

    Authorize and save

    Follow what the window asks: either approve access on the eSignatures.io page, or paste the key the app gives you. Click Save, and Make can now reach your contracts.

First scenario

Your first scenario: send a contract when a deal closes

GoalWhen a deal is marked as won in the app your sales team uses, Make sends the contract through eSignatures.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This one belongs to the app where your deals live, such as your CRM or a spreadsheet.

  2. 02

    Pick the starting event

    Choose the module of that app that spots a won deal, connect the account, then fill its fields. Make lists what it can read once the connection exists, so you rarely type anything by hand.

  3. 03

    Add Create a Contract

    Click the + on the right of the first module, search for eSignatures and pick Create a Contract. Map the signer details from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one deal. Check that the right signer got the contract.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

Which eSignatures events can start a scenario?

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

eSignatures1Watch Contract Sent To Signer

Watch Contract Sent To Signer

Instant trigger

In Make“Triggers when the contract has been sent to a signer.”

You get a signal the moment a contract reaches a signer, so the rest of your tools know the document is out and waiting. It turns a silent send into an event you can log or share.

How it fires
instant, eSignatures calls Make through a webhook as soon as the contract is sent.
When to use it
write the send into your CRM so the account owner sees that the paperwork is on its way.
Watch out
it only confirms the send, not a signature, so never mark the deal as won from this event alone.
eSignatures2Watch Contract Signed

Watch Contract Signed

Instant trigger

In Make“Triggers when all signers have signed the contract.”

This trigger tells you a contract is complete: every signer has put their name on it. It is the cleanest point to hand the file over to delivery, billing or onboarding.

How it fires
instant, eSignatures notifies Make by webhook once the final signature lands.
When to use it
open the kickoff task and move the deal to closed, only when the agreement is fully binding.
Watch out
it waits for all signers; if you need to act after the first one, use Watch Contract Signed By A Signer instead.
eSignatures3Watch Contract Signed By A Signer

Watch Contract Signed By A Signer

Instant trigger

In Make“Triggers when a signer has signed the contract.”

Follow progress signer by signer and know who has already done their part before the whole contract is complete. That helps you nudge only the people still missing.

How it fires
instant, the app calls Make through a webhook each time one signer signs.
When to use it
a contract needs the client first and your director second, and you want to ping the director right after the client signs.
Watch out
this one fires several times on the same contract, so a filter keeps the step you care about from repeating.
eSignatures4Watch Mobile Number Update Requested by Signer

Watch Mobile Number Update Requested by Signer

Instant trigger

In Make“Triggers when a signer requests a mobile number update”

Catch the case where a signer asks to change the mobile number linked to a contract, and route it to someone who can check the request before anything else goes out.

How it fires
instant, eSignatures warns Make by webhook as soon as the signer makes the request.
When to use it
contracts go out by SMS and your account managers must confirm any new number with the client.
Watch out
treat it as a security signal; posting the request in a shared channel is safer than letting a scenario accept the change blindly.
eSignatures5Watch Webhook Error Notifications

Watch Webhook Error Notifications

Instant trigger

In Make“Triggers when an error has occurred (eg: delivery issue)”

Hear about failures instead of discovering them days later: this trigger reports an error on the eSignatures side, such as a delivery issue, so a stuck contract never goes unnoticed.

How it fires
instant, the app sends the error to Make through a webhook the moment it occurs.
When to use it
alert the contract owner by email or chat so they can check the signer's details and resend.
Watch out
keep this scenario separate and simple; an alert flow that breaks itself is hard to notice.
Modules

What can Make do in eSignatures?

eSignatures gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

eSignatures1

Create a Contract

Action

In Make“Sends a new contract via SMS or Email to signers.”

Send a new contract to your signers by SMS or email straight from a scenario, filled with data that another module has already collected. It is the only action of the app, and the one that starts every signing.

When to use it
a quote is accepted or a form is submitted and the agreement should leave right away.
Watch out
run a Run once test on your own address first, because a real contract goes out as soon as the module runs.
Need help

Need help automating eSignatures with Make?

A person reads every message.

FAQ

Questions about the eSignatures Make integration

01Is the eSignatures Make integration free?
Yes, eSignatures is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, 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 allow 40 minutes per execution. Usage is counted in credits, one operation each time a module processes a bundle. Your eSignatures.io subscription is a separate matter and is not covered here.
02What do you need to connect eSignatures to Make?
An eSignatures.io account and a Make account. The documentation lists no other prerequisite. Add any eSignatures module, click Create a connection, give it a name if you like, then approve access on the eSignatures.io page or paste the key the app provides, depending on what the window asks. Click Save and the connection is ready. It is shared by all 6 eSignatures modules, so you only do this once per account, even if you build several scenarios later on.
03Do eSignatures triggers in Make react in real time?
Yes. All 5 eSignatures triggers are instant: eSignatures calls Make through a webhook as soon as the event happens, whether a contract is sent, signed by one person, signed by everyone, a mobile number change is requested or an error occurs. In the editor they carry a lightning badge instead of the clock of scheduled triggers. The schedule of 15 minutes by default only matters when the scenario starts with a scheduled module from another app, as in the first scenario above.
04What if the eSignatures module you need is missing in Make?
It depends on what you want to do. This app has no Make an API Call module, so Make cannot reach eSignatures beyond its 6 listed modules: 5 triggers and Create a Contract. The documentation gives no numeric limit to work around. If an action is missing, check whether another app in your scenario can handle that step, or ask the team for help designing the flow. Mapping data from the triggers into your other tools often covers what looked like a missing feature.
05Should you use Make or n8n for eSignatures?
It depends on your criteria rather than on a winner. On Make, eSignatures comes with 6 ready modules, 5 instant triggers and 1 action, and it works from the Free plan. There is no Make an API Call module, so what you can do stays within those modules. The same app often has an n8n node too, so compare what each tool offers for your exact use case: the events you need, the action you need, and the platform your team already runs. The comparison page linked in this guide lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations