Resources · Make integration

SignRequest Make integrationAutomate SignRequest with Make.

Can signature requests run on their own while you work? The SignRequest Make integration gives you 23 modules, one instant trigger among them, for documents, SignRequests, templates and teams. This page explains each one simply and walks you through a first scenario.

Try the SignRequest integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SignRequest Make integration automate?

The SignRequest Make integration links your SignRequest account to Make, a tool where you build a scenario (the automation itself, a chain of modules) without writing code. Each module is one brick: a trigger that starts the flow, an action that sends or cancels a request, or a search that pulls a list of items.

Contracts that leave on their own. A sales tool marks a deal as won, and Create Quick SignRequest builds the document and sends it for signature in one step. Nobody has to open SignRequest and upload the file by hand.

A signed file that lands where your team works. Watch Events tells Make as soon as something happens on a SignRequest, then Get a Document retrieves the file so the next module can store it or post it elsewhere.

Follow-ups without a spreadsheet. List SignRequests pulls every request in the account, a filter keeps the ones still waiting, and Resend a SignRequest nudges the signer again.

Keep one limit in mind: SignRequest asks you to pay the vendor for API use, so check your SignRequest plan before you build. The same app often exists as an n8n node as well; n8n vs Make lays out how to pick between the two tools. For what each Make plan includes, read Make pricing, and if you want a guided path through the editor, Make training covers it step by step.

Connect

How do you connect SignRequest to Make?

  1. 01

    Open the connection window

    Add any SignRequest module to a scenario and click Create a connection. A connection is your SignRequest account linked to Make once; every SignRequest module in your scenarios reuses it afterwards.

  2. 02

    Name it and give your subdomain

    Type a label you will recognize in Connection name. In Subdomain, enter the first part of your account address: if you log in at https://www.xyz.signrequest.com, the subdomain is xyz.

  3. 03

    Approve the access

    Click Continue. SignRequest opens its own screen and asks you to confirm that Make may act on your account. Click Authorize, and the connection shows up in the module, ready to use.

First scenario

Your first scenario with SignRequest and Make

GoalWhen SignRequest reports an event on one of your requests, Make fetches the related document so you can pass it on.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for SignRequest and pick Watch Events.

  2. 02

    Link your account

    Click Create a connection, enter your connection name and subdomain, then approve with Authorize. The trigger now listens to your SignRequest account through a webhook.

  3. 03

    Add Get a Document

    Click the + on the right of the trigger, choose SignRequest again and select Get a Document. Map the document from the data Watch Events received, so Make knows which file to retrieve.

  4. 04

    Test with Run once

    Click Run once, then trigger an event in SignRequest, for instance by sending a test request to yourself. Open the bubble above each module to read the bundle, the item it received.

  5. 05

    Switch it on

    When the output looks right, turn the scenario on. Since Watch Events is instant, it runs whenever SignRequest calls Make. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts a SignRequest scenario

1 module starts a scenario when something happens in SignRequest. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SignRequest as soon as it happens.

SignRequest1Watch Events

Watch Events

Instant trigger

In Make“Watches SignRequest events.”

This trigger starts your scenario the moment SignRequest records an event on your account, so the follow-up happens without anyone checking the dashboard. It is the only trigger this app offers, which makes it the natural first module for anything reactive.

How it fires
instant, the app calls Make through a webhook as soon as it happens. You will see the lightning badge on the module.
When to use it
when a change on a request should set off work elsewhere, such as saving a file or alerting a colleague.
Watch out
an instant scenario only receives events while it is switched on, so turn it on once your test with Run once looks right.
Modules

What SignRequest can do in Make

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

SignRequest1

Cancel a SignRequest

Action

In Make“Cancels a SignRequest.”

Stops a signature request that is still open, so the signer can no longer act on an outdated version. The request stays in your history, marked as cancelled rather than signed.

When to use it
a deal falls through in your CRM and the pending contract has to be withdrawn.
Watch out
none of the listed modules reopens a cancelled request, so to ask again you create a new SignRequest.
SignRequest2

Create a Document

Action

In Make“Creates a document.”

Puts a file into your SignRequest account without sending it to anyone yet. You end up with a document you can attach files to or send later with a separate module.

When to use it
when the file is ready before the list of signers is, or when a reviewer must look at it first.
Watch out
on the Free plan of Make, files above 5 MB will not pass.
SignRequest3

Create a Document Attachment

Action

In Make“Creates an attachment for a document.”

Adds a supporting file to an existing document, so the signer sees the terms, an appendix or a price list next to the main contract.

When to use it
right after Create a Document, when every agreement ships with the same annex.
Watch out
the document has to exist first; map its reference from the module that created or found it, otherwise the attachment has nowhere to go.
SignRequest4

Create a SignRequest

Action

In Make“Creates a SignRequest.”

Sends a document already stored in SignRequest out for signature. This is the step that turns a file into a request someone receives and signs.

When to use it
after Create a Document, or on a document found with Search Documents, when you want the upload and the sending kept apart.
Watch out
if you have no document yet, Create Quick SignRequest handles both steps and saves you a module.
SignRequest5

Create Quick SignRequest

Action

In Make“Creates a document and SignRequest in one call.”

Builds the document and the signature request in a single module, which keeps a scenario short and easy to read for a beginner.

When to use it
a form or a won deal should produce a contract that leaves at once, with no review in between.
Watch out
because everything happens in one module, there is no pause to check the file; add a filter before it if some records should never be sent.
SignRequest6

Delete a Document

Action

In Make“Deletes a document.”

Removes a document from your SignRequest account for good, which keeps the workspace free of test files and drafts nobody needs anymore.

When to use it
cleaning up the documents a test scenario created while you were building it.
Watch out
a delete cannot be undone from Make. Run it on one known document with Run once before letting it loop over a search result.
SignRequest7

Get a Document

Action

In Make“Retrieves a document.”

Fetches one document you already know, so the modules after it can read its details or pass the file on to storage, email or chat.

When to use it
right after Watch Events, to turn a bare event into the actual document it concerns.
Watch out
it needs a precise reference. If you only have a name or a keyword, start with Search Documents instead.
SignRequest8

Get a Document Attachment

Action

In Make“Retrieves a document attachment.”

Retrieves one attachment tied to a document, so an annex you uploaded earlier can travel to the next module.

When to use it
archiving a specific appendix with the signed contract in your file storage.
Watch out
this module expects the attachment's reference. Missing it? Run List a Document's Attachments first, then pick the one you want from the bundles it returns.
SignRequest9

Get an Event

Action

In Make“Retrieves an event.”

Reads the full record of one event in SignRequest, which helps when you want more context than the scenario already carries.

When to use it
inside a scenario that starts from a search or from another app and holds only an event reference.
Watch out
Watch Events already delivers the event it caught, so fetching it again after that trigger usually adds an operation for nothing.
SignRequest10

Get a SignRequest

Action

In Make“Retrieves a SignRequest.”

Pulls up one signature request by its reference so the next module knows its current state and the details that come with it.

When to use it
before sending a reminder, to confirm the request is still open rather than signed or cancelled.
Watch out
this reads one request only; to review many at once, List SignRequests returns them all.
SignRequest11

Get a Team Member

Action

In Make“Retrieves a team member.”

Returns the profile of one person in a SignRequest team, handy when a scenario needs to know who owns a request or who to notify.

When to use it
routing an alert to the colleague responsible for a contract rather than to a shared inbox.
Watch out
it expects a member reference; List Team Members is the way to find one if you only have a name.
SignRequest12

Get a Template

Action

In Make“Retrieves a template.”

Loads one saved template from SignRequest, so a scenario can start from a layout your team has already approved instead of a blank file.

When to use it
a standard agreement, like an NDA, that goes out with the same structure every time a new partner signs up.
Watch out
you need the template's reference, which List Templates gives you if you do not have it at hand.
SignRequest13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the SignRequest API with the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it
you need an operation none of the other ready-made modules offers.
Watch out
you write the request yourself, so keep the SignRequest API reference open; this module is for readers already comfortable with how an API works.
SignRequest14

Resend a SignRequest

Action

In Make“Resends a SignRequest.”

Sends the same signature request again to its signers, a polite nudge that does not require building a new request.

When to use it
a request found with List SignRequests is still waiting and your sales team wants it back quickly.
Watch out
filter out signed or cancelled requests first, otherwise people who already signed get a pointless reminder.
SignRequest15

List a Document's Attachments

Search

In Make“Retrieves a document's attachments.”

Returns every attachment of one document, each as its own bundle, so you can process them one after another in the next modules.

When to use it
copying all the annexes of a signed contract into a client folder in one pass.
Watch out
a search can return zero, one or many items, and each item costs an operation in the modules that follow.
SignRequest16

List Documents

Search

In Make“Retrieves all documents.”

Pulls every document in your SignRequest account, which gives you a full picture when you want to review or export them.

When to use it
building a register of all contracts in a spreadsheet, or checking what exists before a cleanup.
Watch out
with a large account this sends many bundles downstream; if you only need a few, Search Documents narrows the result.
SignRequest17

List Events

Search

In Make“Retrieves all events.”

Retrieves the events recorded in your account as a batch, useful when you want history rather than a reaction to a new event.

When to use it
catching up on what happened before your Watch Events scenario was switched on.
Watch out
for new events, rely on Watch Events; running List Events on a schedule repeats the same items unless you filter them.
SignRequest18

List SignRequests

Search

In Make“Retrieves all SignRequests.”

Gathers all signature requests of the account, each one a bundle you can filter and then act on in a later module.

When to use it
finding requests still waiting for a signature so Resend a SignRequest can chase them.
Watch out
it returns everything, signed ones included; add a filter right after it so only the requests you care about go further.
SignRequest19

List Team Members

Search

In Make“Retrieves all team members.”

Shows everyone who belongs to a team in SignRequest, one bundle per person, which is the starting point for any member lookup.

When to use it
syncing your SignRequest users with an HR sheet to spot who still has access after leaving.
Watch out
every person comes out as a bundle, so the modules after it run once per member.
SignRequest20

List Teams

Search

In Make“Retrieves all teams.”

Returns the teams set up in your SignRequest account, so a scenario can loop over each of them instead of relying on a single hard-coded one.

When to use it
an agency running separate teams per client that wants one scenario to audit all of them.
Watch out
each team becomes a bundle, and every module after it runs once per team, which adds operations.
SignRequest21

List Templates

Search

In Make“Retrieves all templates.”

Brings back the templates saved in SignRequest, which helps you find the right one before sending a contract built on it.

When to use it
picking a template by name in a scenario, then loading it with Get a Template.
Watch out
when you already know the exact template, skip the list and use Get a Template directly to spare operations.
SignRequest22

Search Documents

Search

In Make“Searches for documents using general or specific queries.”

Finds documents that match a query, broad or precise, so you reach the file you need without pulling the whole account.

When to use it
a client emails about their contract and you want to locate it by a detail from that message.
Watch out
the result may hold zero, one or several documents; plan what the scenario does when nothing matches.
Need help

Need help automating SignRequest with Make?

A person reads every message.

FAQ

Questions about the SignRequest Make integration

01Is the SignRequest Make integration free?
On the Make side, yes: SignRequest is a standard app available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 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 allow 40 minutes of execution. On the SignRequest side, the vendor asks you to pay for using its API, so the integration depends on your SignRequest plan too.
02What do you need to connect SignRequest to Make?
A SignRequest account and its subdomain. In the Create a connection window, give the connection a name, enter your subdomain, which is the short part of your account address such as xyz for xyz.signrequest.com, then click Continue and confirm with Authorize. The documentation lists no other prerequisite, but API use is billed by SignRequest, so make sure your plan covers it before the first test. Once the connection exists, every SignRequest module in your scenarios reuses it.
03Does the SignRequest trigger in Make react in real time?
Yes. Watch Events is an instant trigger: SignRequest calls Make through a webhook as soon as an event happens, instead of Make checking on a timer. The module carries the lightning badge in the editor. The scenario has to be switched on to receive those calls, so after your Run once test, activate it. Every other SignRequest module runs when the scenario reaches it, so the whole flow follows the pace of the events SignRequest sends.
04What if a SignRequest module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SignRequest API with the connection you already created, so you are not limited to the ready-made modules. You write the request yourself, which calls for the SignRequest API reference. The documentation lists one limit worth repeating: API access is paid to SignRequest, and that applies to this module as it does to every other one. Test the call with Run once before switching the scenario on.
05Should you use Make or n8n for SignRequest?
It depends on how you like to build. On Make, SignRequest comes with 23 modules, including an instant trigger and a generic API module, all usable in a visual editor where you drag modules and map data without code. The same app often exists as an n8n node too, so check that the operations you need are covered there before choosing. Neither tool is ranked above the other here; compare the modules each one offers for your contracts.
Same platform

Other docs you might need on this stack.

Browse all integrations