Resources · Make integration

Signable Make integrationAutomate Signable with Make.

What if every signed contract updated the rest of your tools on its own? The Signable Make integration gives you 31 modules, including 9 instant triggers. This guide is for sales and ops teams: connect your account, then build a first scenario step by step.

Try the Signable integration on MakeSee the 31 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Signable Make integration do for you?

The Signable Make integration links your Signable 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 reads something. Once linked, envelopes, contacts, users and partners in Signable can move to and from your other apps without copy and paste.

Send contracts without opening Signable. A new row in a spreadsheet or a deal in your CRM can feed Create an Envelope from Template, so the signer gets the document with the right names already filled in. Create an Envelope does the same when there is no template behind the document.

Know the moment a deal is signed. Watch Envelope Completed alerts Make as soon as the envelope is done, and the next module can post a message to your team or update the deal. Watch Envelope Rejected and Watch Envelope Opened cover the other outcomes, so a stalled signature does not go unnoticed.

Keep your address book in step. Create a Contact, Update a Contact and List Contacts let a CRM or a form stay the single place where client details are typed.

What the listed modules do not cover can often be reached with Make an API Call, which uses the same connection. Signable's own documentation page on Make says its text is AI-generated and may contain mistakes, so check any detail that matters with Signable. If you are still weighing tools, read the n8n vs Make comparison or the Make review, and the Make training is there if you want to go further.

Connect

How do you connect Signable to Make?

  1. 01

    Create an API key in Signable

    In Signable, click your account icon in the top right, open Company Settings, then the API and Webhooks tab. Click Add an API Key, name it, save, then click Show and copy the key.

  2. 02

    Add a Signable module in Make

    In your scenario, add any Signable module and click Create a connection. A connection is your Signable account linked to Make once, then reused by every Signable module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from Signable and confirm. Make now reads your Signable account, so the next modules you add can pick from what it finds there instead of asking you to type identifiers.

First scenario

Your first scenario: send a contract from a template

GoalWhen a new client lands in the app you already use, Make sends them a Signable envelope built from your template.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. The first module you place decides when the whole scenario starts.

  2. 02

    Pick your source app

    Search the app where new clients appear, such as your CRM or form tool, choose its trigger and connect it. Each new client will reach Make as a bundle, meaning one item passed to the next module.

  3. 03

    Add Create an Envelope from Template

    Click the + on the right of the first module, search Signable and pick Create an Envelope from Template. Connect your account with the API key, then map the client's details from the previous module.

  4. 04

    Test with Run once

    Click Run once, then add a test client in your source app. Open the bubble above each module to read the bundles it received and check that the envelope went to the right person.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default, unless your source app calls Make instantly) and switch the scenario on. On the Free plan you can keep 2 scenarios active.

Triggers

What can start a Signable scenario?

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

Signable1Watch Contact Created

Watch Contact Created

Instant trigger

In Make“Triggers when a new contact is created.”

Every time someone adds a contact in Signable, this trigger hands the new record to your scenario, so a second tool never has to be updated by hand.

How it fires
instant. Signable calls Make through a webhook as soon as the contact exists, so the scenario does not wait for a schedule.
When to use it
your team sometimes creates signers straight in Signable and you want those people to show up in your CRM or mailing list as well.
Watch out
if your scenario also creates contacts in Signable from the CRM, you can end up sending the same person back and forth; add a filter before the next module.
Signable2Watch Envelope Cancelled

Watch Envelope Cancelled

Instant trigger

In Make“Triggers when an envelope is cancelled.”

A cancelled envelope usually means a deal changed. This trigger tells your scenario about it right away, so the people who follow the deal hear it from the system rather than by accident.

How it fires
instant. Signable calls Make through a webhook as soon as the envelope is cancelled.
When to use it
you want a cancelled contract to reopen a task, flag the deal in your CRM or post a note in the sales channel.
Watch out
if a scenario of yours uses Cancel an Envelope, check with Run once whether those cancellations reach this trigger too.
Signable3Watch Envelope Completed

Watch Envelope Completed

Instant trigger

In Make“Triggers when an envelope is completed.”

This is the trigger most teams start with: it tells Make that an envelope is finished, which is the signal to move the deal forward, bill the client or file the document.

How it fires
instant. Signable calls Make through a webhook as soon as the envelope is completed.
When to use it
the next step in your process should only begin once the whole envelope is done, not after a single signature.
Watch out
Make lists both Completed and Signed as separate triggers; test each with Run once on a real envelope before you decide which one your process needs.
Signable4Watch Envelope Created

Watch Envelope Created

Instant trigger

In Make“Triggers when a new envelope is created.”

Tracking what leaves your company for signature gets easier with this trigger: each new envelope is passed to Make the moment it is created, whoever made it.

How it fires
instant. Signable calls Make through a webhook as soon as the envelope is created.
When to use it
you keep a log of every contract sent, in a sheet or a database, and want it filled without anyone remembering to do it.
Watch out
check with Run once whether envelopes created by your own Make scenarios reach it too, before you chain more actions after it.
Signable5Watch Envelope Opened

Watch Envelope Opened

Instant trigger

In Make“Triggers when an envelope is opened.”

Knowing that a client has opened the contract tells your sales rep the timing is right for a follow-up call. This trigger brings that moment into Make.

How it fires
instant. Signable calls Make through a webhook as soon as the envelope is opened.
When to use it
you want the account owner pinged, or a CRM activity logged, when the signer first looks at the document.
Watch out
an opened envelope is not a signed one; keep the actions that follow light, like a notification rather than a status change.
Signable6Watch Envelope Rejected

Watch Envelope Rejected

Instant trigger

In Make“Triggers when an envelope is rejected.”

A refusal is the event you least want to miss. With this trigger, a rejected envelope reaches Make straight away, so someone can react while the conversation is still warm.

How it fires
instant. Signable calls Make through a webhook as soon as the envelope is rejected.
When to use it
a rejected quote or contract should create a task for the account owner or move the deal to a review stage.
Watch out
resending automatically is rarely wise; route the rejection to a person first.
Signable7Watch Envelope Signed

Watch Envelope Signed

Instant trigger

In Make“Triggers when an envelope is signed.”

Signature progress becomes visible outside Signable with this trigger, which passes a signed envelope to your scenario as soon as Signable reports it.

How it fires
instant. Signable calls Make through a webhook as soon as the envelope is signed.
When to use it
you want to react to a signature event itself, for example to thank the signer or update a progress field in your CRM.
Watch out
the directory does not spell out how this event differs from Watch Envelope Completed on envelopes with several signers; check with Run once before relying on it.
Signable8Watch Template Created

Watch Template Created

Instant trigger

In Make“Triggers when a new template is created.”

New templates are easy to lose track of in a growing team. This trigger reports each one to Make, so the people who send contracts know a fresh version exists.

How it fires
instant. Signable calls Make through a webhook as soon as the template is created.
When to use it
you keep a shared list of approved templates, or you want legal to be notified whenever someone adds one.
Watch out
scenarios that use Create an Envelope from Template will not switch to the new template on their own; update the module when you want it used.
Signable9Watch User Created

Watch User Created

Instant trigger

In Make“Triggers when a new user is created.”

Access reviews get simpler when every new Signable seat is recorded. This trigger passes each new user to Make as soon as the account is added.

How it fires
instant. Signable calls Make through a webhook as soon as the user is created.
When to use it
IT or operations keeps a register of who can send contracts, or wants a welcome message sent to the new colleague.
Watch out
if another scenario uses Create a User, test whether those accounts reach this trigger as well, and add a filter if they do.
Modules

What can Make do in Signable?

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

Signable1

Cancel an Envelope

Action

In Make“Cancels an existing envelope.”

Stops an envelope that is already out, so the signer can no longer act on an outdated contract.

When to use it
a deal is marked lost in your CRM and the pending contract should be withdrawn at once.
Watch out
it needs the envelope's identifier, usually from a trigger or from Get an Envelope earlier in the scenario.
Signable2

Create a Contact

Action

In Make“Creates a new contact.”

Adds a person to your Signable contacts, so they are ready the day you send them something to sign.

When to use it
a new client is entered in your CRM or a form, and you want Signable to know them before the first contract.
Watch out
run List Contacts first if the same person could already exist, to avoid duplicates.
Signable3

Create an Envelope

Action

In Make“Creates a new envelope without a template and sends it to the user.”

Builds a new envelope without any template and sends it straight to the signer, which suits one-off documents.

When to use it
each contract is different, for example a custom proposal produced by another tool, and no saved template fits.
Watch out
the envelope goes out as soon as the module runs, so test with Run once on your own address first.
Signable4

Create an Envelope from Template

Action

In Make“Creates a new envelope from the template and sends it to the user.”

Starts from a template you already set up in Signable, creates the envelope and sends it, which keeps every contract in the same approved shape.

When to use it
you send the same agreement to many clients, like terms of service or an onboarding form, and only the names change.
Watch out
the envelope is sent at once, so a mapping mistake reaches a real client; test carefully.
Signable5

Create a Partner

Action

In Make“Creates a new partner.”

Adds a partner record in Signable from your scenario, so partner accounts are set up the same way every time instead of by hand.

When to use it
a partner agreement is approved elsewhere and the partner should appear in Signable right after.
Watch out
Make's documentation does not say what a partner record holds, so open the module and read what Signable asks for.
Signable6

Create a User

Action

In Make“Creates a new user.”

Gives a new colleague a Signable user account from Make, as part of the same onboarding flow as their other tools.

When to use it
HR or IT adds an employee and you want contract-sending access created without a separate ticket.
Watch out
test it first with a dummy colleague, since the new account appears in Signable as soon as the module runs.
Signable7

Delete a Contact

Action

In Make“Deletes an existing contact.”

Removes a contact from Signable, which helps when a client asks to be forgotten or a record was created by mistake.

When to use it
a deletion request is logged in your CRM and Signable should follow.
Watch out
there is no undo in the scenario; put a filter before it so only the intended contact is removed.
Signable8

Delete an Envelope

Action

In Make“Deletes an existing envelope.”

Erases an envelope from Signable, a stronger move than cancelling it, meant for clearing out tests or mistakes.

When to use it
you ran test envelopes while building a scenario and want them gone.
Watch out
deletion cannot be reversed from Make; if the document might matter later, prefer Cancel an Envelope.
Signable9

Delete a Partner

Action

In Make“Deletes an existing partner.”

Takes a partner out of Signable once the relationship has ended, keeping your list of partners current.

When to use it
a partnership is closed in your CRM and the matching Signable record should disappear with it.
Watch out
nothing brings the record back afterwards; confirm the partner first with Get a Partner.
Signable10

Delete a User

Action

In Make“Deletes an existing user.”

Closes a colleague's Signable account from your offboarding scenario, so a departure does not leave access open.

When to use it
an employee leaves and your HR tool triggers the removal of all their accounts.
Watch out
the action is final from Make's side; check which user you are targeting with Get a User or List Users.
Signable11

Get a Contact

Action

In Make“Retrieves an existing contact.”

Fetches one contact's details from Signable when you already know which contact you need.

When to use it
a trigger gives you a contact reference and the next module needs the full record, such as the email address to write to.
Watch out
it reads a single contact; when you only have a name or an email, List Contacts is the better start.
Signable12

Get an Envelope

Action

In Make“Retrieves an existing envelope.”

Reads the full record of one envelope, so later modules can map its details even when the scenario only started with an identifier.

When to use it
right after Watch Envelope Completed, to pull what you want to store in your CRM or spreadsheet.
Watch out
each call costs one operation, the unit Make counts on your plan, so check with Run once whether the trigger bundle already holds what you need.
Signable13

Get a Partner

Action

In Make“Retrieves an existing partner.”

Looks up one partner in Signable and returns its record for the rest of the scenario to use.

When to use it
before updating or deleting a partner, to confirm you have the right one and see its current values.
Watch out
you need the partner's identifier; List Partners helps you find it when you do not have it yet.
Signable14

Get a User

Action

In Make“Retrieves an existing user.”

Pulls the details of a single Signable user, handy when a scenario must know who a sender is.

When to use it
Watch User Created fires and you want the complete user record before writing it into your HR or IT register.
Watch out
it returns one user only; to check every account at once, use List Users.
Signable15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Signable API with the connection you already set up, for the cases the other listed modules do not cover.

When to use it
you need an operation of the Signable API that has no dedicated module in Make.
Watch out
you describe the request yourself, so keep Signable's API documentation open while you build it.
Signable16

Send a Reminder for an Envelope

Action

In Make“Sends a reminder for an existing envelope.”

Nudges the signer of a pending envelope without anyone on your side writing a chaser.

When to use it
a deal owner clicks a button or changes a status in your CRM, and the reminder should leave from Signable.
Watch out
reminders sent too often annoy clients; tie this module to a clear event rather than to every run.
Signable17

Update a Contact

Action

In Make“Updates an existing contact.”

Changes an existing Signable contact so that the details used on the next envelope match your CRM.

When to use it
a client changes email or company name and the correction should spread to Signable too.
Watch out
map only the fields that really changed, or an empty value from the source can overwrite good data.
Signable18

Update a Partner

Action

In Make“Updates an existing partner.”

Edits a partner record in Signable, keeping it aligned with the tool where partner information is actually maintained.

When to use it
a partner's details change in your CRM or partner portal and Signable should reflect it.
Watch out
fetch the current record with Get a Partner first if you are not sure which values the source provides.
Signable19

Update a User

Action

In Make“Updates an existing user.”

Modifies an existing Signable user, for example after a change of role or name in your company.

When to use it
your HR system records a change for an employee who sends contracts, and Signable should stay in step.
Watch out
run it on the right account only; Get a User lets you check before writing.
Signable20

List Contacts

Search

In Make“Retrieves a list of contacts.”

Returns contacts from your Signable address book so the scenario can check, compare or export them.

When to use it
before creating a contact, to see whether that person is already there.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which multiplies operations.
Signable21

List Partners

Search

In Make“Retrieves a list of partners.”

Gathers the partner records held in Signable, useful for a report or a reconciliation with your CRM.

When to use it
you want a sheet listing every partner, or you need to find one partner's identifier.
Watch out
a search can return zero, one or several bundles, so decide what the scenario should do when no partner comes back.
Signable22

List Users

Search

In Make“Retrieves a list of users.”

Brings back the users of your Signable account, the starting point for any access check.

When to use it
an audit asks who can send contracts, and you want the answer written into a spreadsheet by the scenario.
Watch out
each user comes out as its own bundle, so an action placed after it runs once per user.
Need help

Need help automating Signable with Make?

A person reads every message.

FAQ

Signable and Make: common questions

01Is the Signable Make integration free?
Yes, on the Make side. Signable is a standard app, so it works on the Free plan, which 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 drop the interval to 1 minute and lift the limit on active scenarios. You still need an active Signable account, and its subscription is set by Signable, not by Make.
02What do you need to connect Signable to Make?
An active Signable account and an API key. In Signable, open Company Settings from your account icon, go to the API and Webhooks tab, click Add an API Key, name it and save, then click Show to copy it. In Make, add a Signable module, click Create a connection and paste the key. On a trigger, click Create a webhook before Create a connection, because every Signable trigger is instant.
03Do Signable triggers in Make fire in real time?
Yes. All nine Signable triggers are instant: Signable calls Make through a webhook as soon as the event happens, whether that is a contact created, an envelope opened, signed, completed, rejected or cancelled, a template created or a user added. None of them waits for the scenario's schedule. The 15-minute default only matters if your scenario starts from a scheduled module of another app. To see it for yourself, trigger an event in Signable while the scenario is running Run once.
04What if a Signable module is missing in Make?
It depends on what you need. The Signable app includes Make an API Call, which can reach any endpoint of the Signable API with the connection you already created, so an operation without its own module is usually still possible. You write the request yourself, with Signable's API documentation beside you. Keep in mind that Signable's Make documentation says it is AI-generated and may contain mistakes, so verify anything important with Signable directly.
05Make or n8n for Signable?
It depends on the criteria that matter to your team. In Make, Signable comes with 31 ready modules, 9 instant triggers and Make an API Call, and a visual editor where you test each run with Run once. The same app often has an n8n node too, so check what that node covers before you choose. Compare the two tools on how your team builds, tests and maintains automations rather than on this one app.
Same platform

Other docs you might need on this stack.

Browse all integrations