Resources · Make integration

Contractbook Make integrationAutomate Contractbook with Make.

Can a signed deal turn into a ready-to-sign contract without copy and paste? The Contractbook Make integration gives you 7 modules: 5 actions and 2 searches. This guide shows how to link your account, then walks you through a first scenario, step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Contractbook Make integration do?

The integration lets Make create, update, send and retrieve Contractbook documents on your behalf. You build a scenario, the automation you assemble in Make, out of modules: each module is one brick, here an action or a search on your Contractbook account. Another app feeds the data, Contractbook produces the contract.

A contract that drafts itself. When a deal closes in your CRM, Create Document from Template builds the agreement from your standard template, and Send Document for Signature puts it in front of the client. Sales reps stop retyping names and amounts.

A contract copy in the right folder. Get a PDF Copy of a Document pulls the file so a storage app can keep it next to the client record, for example a base built with the Airtable Make integration.

A cleanup pass on drafts. List Documents finds contracts by title or ID, and Update Document corrects them before anyone signs.

Know the limits before you start. Contractbook has no trigger in Make, so a scenario starts from another app or from a schedule. Make also says its documentation for this app is limited, so plan a test run for every new module. When something breaks, the Make troubleshooting guide is a good first stop.

Weighing tools? The n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect Contractbook to Make?

  1. 01

    Add a Contractbook module

    In your scenario, search for Contractbook, pick any of its modules, then click Create a connection. A connection is your Contractbook account linked to Make once, then reused by every Contractbook module you add later.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the workspace or team pays off the day you run two accounts side by side. Make shows that name in every module, so you always know which account a scenario writes to.

  3. 03

    Authorize and save

    Depending on what Contractbook asks for, you either approve Make on the Contractbook page or paste the key Contractbook gives you. Then click Save. The module now lists what it can read from your account.

First scenario

Your first scenario with Contractbook

GoalWhen a deal is marked as won in your CRM, Make creates the contract from your template in Contractbook and sends it for signature.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where deals close, your CRM for instance, as the first module, since Contractbook has no trigger.

  2. 02

    Add Create Document from Template

    Click the + to the right of the CRM module and choose Create Document from Template. Link your account, then pick the template Make lists once the connection exists.

  3. 03

    Map the deal data

    Fill the module with values from the CRM module: client name, amount, anything your template expects. Each deal travels as a bundle, one item passed from module to module.

  4. 04

    Send it for signature

    Add Send Document for Signature and map the document ID returned by the previous module. This module works on documents in a draft state, so point it at the contract you just created.

  5. 05

    Test with Run once

    Click Run once and open each module to read the bundles it received. Check the contract in Contractbook before any real client sees one.

  6. 06

    Schedule and switch on

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

Modules

What each Contractbook module does

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

Contractbook1

Create Document from Template

Action

In MakeCreates a new document from a template.

You get a fresh contract built from one of your Contractbook templates, filled with data from earlier modules. No more duplicating a document by hand for each new client.

When to use it
right after a deal, a signup or a form answer, when the contract always follows the same model.
Watch out
creating the document does not send it anywhere, so add Send Document for Signature when the client should receive it.
Contractbook2

Get a PDF Copy of a Document

Action

In MakeGets a PDF copy of a document by ID.

This module hands you a PDF version of a Contractbook document, ready to attach to an email or store in a drive. It works from the document ID, so the contract must already exist.

When to use it
once a contract is final and your team wants a copy stored outside Contractbook.
Watch out
files on the Free plan are capped at 5 MB, so check your largest contracts first.
Contractbook3

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

With this module you reach any endpoint of the Contractbook API while reusing the connection you already set up. It covers whatever the six other modules leave out.

When to use it
when no listed module does what you need and the Contractbook API does.
Watch out
you write the request yourself, so keep the Contractbook API reference open and test with Run once before going live.
Contractbook4

Send Document for Signature

Action

In MakeSends a document in a draft state specified by ID.

Here the contract leaves your desk: the module sends a draft document, picked by its ID, out for signing. The client receives it without anyone opening Contractbook.

When to use it
straight after Create Document from Template, or after a review step that approves the draft.
Watch out
it expects a document in a draft state, so map the ID of a draft rather than an older contract.
Contractbook5

Update Document

Action

In MakeUpdates a document.

Update Document changes an existing Contractbook document so corrections from another app land on the contract itself. You avoid recreating a whole agreement for one wrong detail.

When to use it
a client record changes in your CRM while its contract is still being prepared.
Watch out
you need the document ID, so place List Documents before it when you only know the title.
Contractbook6

List Documents

Search

In MakeLists a paginated and filtered list of documents. The module can be used to get all the documents or to filter them by ID or title.

This search returns your Contractbook documents, all of them or only those matching an ID or a title. Every document found becomes a separate bundle for the next module.

When to use it
to find the contract that belongs to a client before updating it or pulling its PDF.
Watch out
a search can return zero, one or many documents, so a loose title filter can trigger the next module several times.
Contractbook7

List Templates

Search

In MakeLists templates. The templates can be filtered by title.

You get the templates stored in your Contractbook account, optionally narrowed down by title. That lets a scenario choose the right model instead of hard-coding one.

When to use it
when the template depends on the deal, such as a different agreement per offer or per country.
Watch out
templates with similar titles all come back, so name them distinctly in Contractbook before you filter.
Need help

Need help automating Contractbook with Make?

A person reads every message.

FAQ

Contractbook and Make: common questions

01Is the Contractbook Make integration free?
Yes, on the Make side. Contractbook is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your Contractbook subscription is a separate matter that this page does not cover.
02What do you need to connect Contractbook to Make?
A Contractbook account and a Make account. The Make documentation lists no other prerequisite. In any Contractbook module, click Create a connection, give it a name if you like, then either approve Make on the Contractbook page or paste the key Contractbook provides, and click Save. The connection is then shared by all seven Contractbook modules in your scenarios, so you only do this once per account. If the authorization fails, create the connection again from any module.
03Does the Contractbook Make integration react in real time?
No, because Contractbook has no trigger module in Make. A scenario therefore starts elsewhere. Either another app opens it, such as a CRM that notices a won deal, or Make runs it on its own schedule, every 15 minutes by default. A webhook from Make can also start the scenario when another tool calls it. From there, the Contractbook modules create, send or fetch documents as soon as the scenario reaches them.
04What if a Contractbook module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Contractbook API with the same connection, so you are not limited to the 5 actions and 2 searches in the list. Keep in mind that Make describes its documentation for Contractbook as limited, which means fewer ready answers when something behaves oddly. Test each request with Run once and read the returned bundle before relying on it in production.
05Should you use Make or n8n for Contractbook?
It depends on your criteria, not on a winner. On Make, Contractbook comes with 7 ready modules, Make an API Call included, and it runs from the Free plan. Before choosing n8n, check whether it offers a Contractbook node that covers your use case, since this page only documents the Make side. Compare the editor you prefer, where your other apps already live and what your team can maintain over time.