Resources · Make integration

Scrive eSign Make integrationAutomate Scrive eSign with Make.

What if your contracts went out for signature as soon as the deal data was ready, without anyone retyping it? The Scrive eSign Make integration gives you 5 action modules to create a document, attach its PDF and start signing. This guide walks sales and legal teams from the first connection to a working scenario.

Try the Scrive eSign integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Scrive eSign Make integration do for you?

The Scrive eSign Make integration links your Scrive account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single step of one app. Here every module is an action, so Scrive does the work once another app or a schedule hands it the data.

Contracts that leave on their own. A new customer lands in your CRM, Create a Document prepares the Scrive document, Set the Main File for the Document attaches the PDF your template tool produced, and Start the Signing Process sends it on its way. Nobody copies a name or an address by hand.

A signing record your team can read. Put Get a Document after the signing step and push the details it returns into a spreadsheet or a project board, so account managers see the document without opening Scrive.

Room for the rest of the API. When the four named modules stop short, Make an API Call reaches any endpoint of the Scrive API with the connection you already set up.

One limit to plan for: the app has no trigger module, so Scrive cannot wake a scenario by itself. The run starts from another app or from the scenario schedule. Weighing platforms first? The n8n vs Make comparison lays out the criteria, and the Make review covers the editor itself. If you would rather hand the build over, see the Make agency page.

Connect

How do you connect Scrive eSign to Make?

  1. 01

    Open a Scrive eSign module

    Log in to Make, add any Scrive eSign module to your scenario and click Create a connection. A connection is your Scrive account linked to Make once, then reused by every Scrive module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label such as the Scrive workspace or the team using it saves confusion when several accounts end up in the same Make organization.

  3. 03

    Paste your Scrive credentials

    Enter the credentials you copied from your Scrive eSign account, OAuth or personal access, or follow the instructions Make shows on screen. Once saved, the module fields unlock and you can start filling them.

First scenario

Build your first scenario with Scrive eSign

GoalWhen a deal is marked as won in another app, Make creates the Scrive document and starts the signing process.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module comes from the app that holds your deal or customer data, since Scrive eSign has no trigger.

  2. 02

    Add Create a Document

    Click the + on the right of that first module, search for Scrive eSign and pick Create a Document. Choose your connection or create it, then map the customer data into the fields Make displays.

  3. 03

    Chain Start the Signing Process

    Add Start the Signing Process after it and map the document coming out of the previous module. Each item passing between modules is a bundle, here one document per deal.

  4. 04

    Test with Run once

    Click Run once and open the bubble above each module to read the bundles it received. A test that goes through is a real document, so try it with your own details first.

  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.

Modules

What the Scrive eSign modules do

Scrive eSign gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Scrive eSign1

Create a Document

Action

In Make“Creates a new document.”

This action opens a fresh document in Scrive from data another app sends, so a contract exists as soon as the deal is ready and nobody has to start it by hand.

When to use it
as the first Scrive step of any flow, right after the module that brings in the client or the order.
Watch out
every run produces a new document, so test with your own details before you point it at live customers.
Scrive eSign2

Get a Document

Action

In Make“Returns information about the selected document.”

You get back the information Scrive holds on a document you pick, ready to map into a later module such as a spreadsheet row or a CRM note.

When to use it
after the signing step, when account managers need the document details somewhere they already work.
Watch out
it reads a single selected document; it does not search across your Scrive account.
Scrive eSign3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you call any endpoint of the Scrive API from your scenario, using the same connection, which covers the jobs the four named modules leave out.

When to use it
once you know which Scrive endpoint answers your need and no listed module does.
Watch out
you write the request yourself, so keep the Scrive API documentation open while you set it up.
Scrive eSign4

Set the Main File for the Document

Action

In Make“Sets or replaces the main PDF file for a document.”

Here the PDF that people will actually sign gets attached to a Scrive document, or swapped for a newer version if the first one changed.

When to use it
between Create a Document and the signing step, when a template or storage app hands you the contract file.
Watch out
it sets or replaces the main PDF, so running it twice on the same document keeps only the last file.
Scrive eSign5

Start the Signing Process

Action

In Make“Starts the signing process.”

With this module the prepared document moves from draft to signing, which is the moment your scenario stops preparing and the contract really goes out.

When to use it
as the closing step, once the document exists and its PDF is in place.
Watch out
place it last and test the whole chain with Run once, because this is the step that reaches real people.
Need help

Need help automating Scrive eSign with Make?

A person reads every message.

FAQ

Scrive eSign and Make: common questions

01Is the Scrive eSign Make integration free?
Yes, on the Make side. Scrive eSign is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs them 15 minutes apart at the shortest, and caps each run at 5 minutes. Paid plans bring the interval down to 1 minute and remove the cap on active scenarios. You still need an active Scrive subscription, which Scrive bills separately; check the Scrive eSign pricing page for that part.
02What does the Scrive eSign Make integration need to connect?
An active Scrive account and a set of credentials: either OAuth credentials or personal access credentials. In Make, add a Scrive eSign module, click Create a connection, optionally give it a name, then paste the credentials or follow the on-screen instructions. The connection is then reused by every Scrive module in your scenarios, so this setup happens once per account. If the window refuses the credentials, check them in Scrive before you try again.
03Does the Scrive eSign Make integration react in real time?
No, because it has no trigger module at all. Scrive cannot start a scenario on its own. Two options remain. You can open the scenario with a trigger from another app, for example the CRM or form tool where the deal is recorded, and let Scrive act right after. Or you can run the scenario on its schedule, every 15 minutes by default, and let the first module fetch whatever is new.
04What if a Scrive eSign module is missing in Make?
Use Make an API Call. The integration includes it, and it can call any endpoint of the Scrive API with the connection you already have, so you are not limited to the four named modules. You will need the Scrive API documentation to build the request. If the problem is the missing trigger rather than a missing action, start the scenario from another app or from the schedule instead. The call runs like any other module and counts as one operation.
05Is Make or n8n better for Scrive eSign?
It depends on where the rest of your stack already runs. On Make, Scrive eSign offers 5 action modules, including Make an API Call, and no trigger, so each scenario starts from another app or a schedule. The same app often has an n8n node as well. Compare the modules each side offers for your exact job, check which tool your team already knows, and pick the one where your whole signing flow fits.
Same platform

Other docs you might need on this stack.

Browse all integrations