- Home
- Resources
- Integrations
- Contractbook
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 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.
How do you connect Contractbook to Make?
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Create Document from Template
ActionIn Make“Creates 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.
Get a PDF Copy of a Document
ActionIn Make“Gets 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.
Make an API Call
ActionIn Make“Performs 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.
Send Document for Signature
ActionIn Make“Sends 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.
Update Document
ActionIn Make“Updates 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.
List Documents
SearchIn Make“Lists 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.
List Templates
SearchIn Make“Lists 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.
Need help automating Contractbook with Make?
A person reads every message.