Resources · Zapier integration

Contractbook Zapier integrationAutomate Contractbook with Zapier.

The Contractbook Zapier integration gives you 10 triggers and 6 actions, with no search step. Eight of those triggers fire instantly, so a sent contract or a finished questionnaire can start work elsewhere right away, even on the free plan.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Contractbook Zapier integration actually does

It links Contractbook, a contract signing and management tool, to the rest of your workflow through Zapier. Something happens in Contractbook (a contract goes out, a draft changes, a questionnaire is filled in) and Zapier runs the steps you chose. Or the other way round: Zapier creates contracts, drafts and tasks in Contractbook for you.

Three results people actually build. Contracts that leave on their own: Create Contract picks a template and sends it, so a deal closed elsewhere turns into a document out for signature. Questionnaires that turn into drafts: Drafter Questionnaire Has Been Completed fires the moment someone finishes the intake form, and Create Draft starts the paperwork from it. Follow-up that nobody forgets: Contract Updated reacts each time a contract moves to a new state, which is the right moment for Create Task.

What Zapier does not do here: there is no search step, so a Zap cannot look up an existing contract, company or template on its own. Every value an action needs has to come from the trigger or be typed in once. There is no delete or archive action either; the six actions all create something.

If you are weighing tools, the Contractbook Make integration covers the same app on another platform, and the Make vs Zapier comparison sets out the criteria.

Vocabulary

Zapier vocabulary in one minute

Seven words you will meet in the editor. Each one is used on this page exactly as defined here.

Zap
The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it to happen.
Action
What the Zap does after it starts: the step that creates, sends or moves something in an app for you.
Task
The unit Zapier bills. One action that completes successfully is one task, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and stops it otherwise.
Connection
Your Contractbook account linked to Zapier once, then reused by every step that talks to Contractbook.
Cost

What a Contractbook Zap really costs

Contractbook is not a premium app: it works from the free plan.

  • Free plan100 tasks a month, unlimited Zaps, two-step Zaps only
  • Trigger and checksNever billed
  • Filter or second actionMulti-step Zap, paid plan

The trigger never costs a task, and neither does Zapier checking for new data. You pay per action that succeeds, and each one counts separately: a Zap that creates a draft and then a task uses two tasks per run. A failed action is not counted. The free plan stops at two steps, one trigger and one action, so adding a filter makes the Zap multi-step and moves it to a paid plan. On the free plan, that means one trigger and one Contractbook action, no more.

Connect

Connect your Contractbook account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an existing Contractbook account, plus access to any contract or template you do not own yourself.

  2. 02

    Pick Contractbook

    Type Contractbook in the search box of the dialog, select it, then click Add connection. Zapier opens a new tab where Contractbook asks you to sign in.

  3. 03

    Grant access

    Sign in with the account whose contracts the Zap should handle, then allow Zapier to use it. From then on, every Contractbook step in every Zap reuses this connection.

First Zap

Your first Zap: a finished questionnaire becomes a draft

GoalWhen someone completes a Drafter questionnaire, Contractbook prepares a draft from your template.

  1. 01

    Build: choose the trigger

    Create a Zap, pick Contractbook as the app and Drafter Questionnaire Has Been Completed as the event. Select your Contractbook connection.

  2. 02

    Set the questionnaire

    The trigger asks for the questionnaire slug, and it is required. Point it at the intake questionnaire your clients fill in, so other questionnaires leave this Zap alone.

  3. 03

    Test the trigger

    Click Test. Zapier brings back the three most recent completed questionnaires of the account, so pick a real one to map from. No completed answer yet means nothing to test with.

  4. 04

    Add Create Draft

    Add the action Create Draft, choose the template and the recipient type (both required), then map the answers you need from the trigger into the draft.

  5. 05

    Test, then Publish

    Run the action test once and open the draft in Contractbook to check it. Then Publish. Two steps, so this one runs on the free plan.

Triggers

Contractbook triggers

10 events start a Zap when something happens in Contractbook, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Contract

Instant trigger

In Zapier“Triggers when a new contract is sent.”

Starts your Zap as soon as a contract is sent out of Contractbook. It is the natural entry point for anything that should follow a signature request.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales team wants every contract that goes out logged as a follow-up task, without anyone opening a spreadsheet.
Watch out
it reacts to sending, not to signing; a later change of state belongs to Contract Updated.
2

Contract Updated

Instant trigger

In Zapier“Triggers when a contract transitions to a new state.”

Reacts each time a contract moves into a new state, so the Zap runs at every step of its life rather than once. That makes it the trigger for anything tied to progress.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an account manager needs a task only when a contract reaches one particular state.
Watch out
without a filter, every state change runs the Zap and every run's action costs a task; a filter makes the Zap multi-step, so a paid plan.
3

Get Companies

Polling trigger

In Zapier“Gets a list of companies.”

Reads the list of companies on your Contractbook account and hands each one Zapier has not seen before to your Zap. It is one of only two triggers here that work on a timer.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a team that runs several entities wants a step to run when a company is added.
Watch out
the first check only remembers what is already there; existing companies never start the Zap.
4

Get Questionnaires

Polling trigger

In Zapier“Gets a list of questionnaires”

Pulls the questionnaires of the account and passes along the ones Zapier has not met yet. It watches the questionnaires themselves, not the answers people give to them.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a legal ops lead who publishes new intake forms wants each one announced as a task.
Watch out
for completed answers, the instant trigger Drafter Questionnaire Has Been Completed is the right one.
5

Drafter Questionnaire Has Been Completed

Instant trigger

In Zapier“Triggers when a user has completed a questionnaire”

Fires when a person finishes a Drafter questionnaire, with the answers already collected. It is the natural start of an intake-to-contract Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a consultancy collects project details through a questionnaire and wants the draft ready before anyone calls the client back.
Watch out
the questionnaire slug is required, so one Zap watches one questionnaire.
6

New Draft

Instant trigger

In Zapier“Triggers when a new draft is created.”

Runs the Zap whenever a draft appears in Contractbook, before anything has been sent. It catches paperwork at its earliest stage, while it can still be reviewed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a manager wants a review task created for every new draft so nothing goes out unchecked.
Watch out
a Zap that uses Create Draft as its action and New Draft as its trigger sets itself off again and again.
7

Draft Edited

Instant trigger

In Zapier“Triggers when a draft is edited.”

Responds to changes made to an existing draft, so it runs on revisions rather than on creation. Every edit counts as an event.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
during a negotiation, the person in charge wants a task each time the draft is reworked.
Watch out
a busy draft can be edited many times in a row, and each run's action costs a task.
8

New Task

Instant trigger

In Zapier“Triggers when a new task is created.”

Reacts to every task created in Contractbook. A task there is tied to a document, since creating one needs a document id.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an operations team wants each task created in Contractbook to start a step in their own process.
Watch out
pairing it with Create Task in the same Zap creates a loop that eats your task count.
9

Task Updated

Instant trigger

In Zapier“Triggers when a task is updated.”

Starts the Zap when an existing task changes, which tracks the work after it has been assigned. It is the counterpart of New Task for anything that happens later.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a team lead wants to know when tasks on key contracts move, without checking Contractbook all day.
Watch out
add a filter if only some updates matter; it turns the Zap multi-step.
10

New Template

Instant trigger

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

Fires when someone adds a template to the account. Templates are the base of every contract and draft the actions create, so this trigger follows your library as it grows.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a head of legal wants a review task opened whenever a new template appears.
Watch out
a template added before the Zap is published never starts it.
Actions

Contractbook actions

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

1

Create Contract

Action

In Zapier“Creates and sends a new contract.”

Creates a contract from a template and sends it straight away. Unlike the draft actions, nobody gets a chance to review it before it leaves.

When to use it
a standard agreement, such as a routine order form, that never changes from one client to the next.
Watch out
template and recipient type are required, and a test run sends a real contract.
2

Create Contract With Custom Parties

Action

In Zapier“Creates and sends a new contract with advanced parties setup.”

Sends a contract with the advanced signers setup, for documents that need more than the default parties.

When to use it
a contract that a client, a guarantor and your own director must all sign.
Watch out
testing this step sends the contract for real, so test with an internal address.
3

Create Draft

Action

In Zapier“Creates a draft”

Prepares a draft from one of your templates without sending it, so someone can still review it first.

When to use it
a deal is agreed in principle and the paperwork should be ready before the final check.
Watch out
the template and the recipient type are both required.
4

Pre-Fill Questionnaire

Action

In Zapier“Pre-fills a questionnaire”

Fills part of a Drafter questionnaire in advance, so the person who opens it has less to type.

When to use it
the client details are already known and asking them twice slows the signature down.
Watch out
the company that owns the questionnaire and the questionnaire itself are both required.
5

Create Draft With Custom Parties

Action

In Zapier“Creates a new draft with advanced parties setup.”

Builds a draft with a more advanced setup of who signs, for agreements that go beyond one sender and one recipient.

When to use it
a partnership deal where several people on each side have to sign.
Watch out
the template and the signers field are required, so the Zap has to know who signs.
6

Create Task

Action

In Zapier“Creates and sends a new task.”

Creates a task in Contractbook and sends it, attached to a document that already exists.

When to use it
a reminder to chase a signature, or a review to do on a fresh draft.
Watch out
title, description and document id are all required, so the task has to belong to an existing document.
When it breaks

When a Contractbook Zap breaks

Zapier attaches no help article to Contractbook, so the traps below are the general ones, read for a contract tool.

None of them shows up as an error on day one. They show up as a missing task, a Zap that keeps restarting, or a task count that runs out early. When one of these hits, the Zapier troubleshooting page is the next stop.

  • Old contracts are ignored

    A Zap only reacts to what happens after you publish it. Contracts sent last month never start it, and moving them is a separate job.

  • A Zap that sets itself off

    New Draft with Create Draft, or New Task with Create Task: the Zap writes where its trigger watches, runs again, and burns through tasks.

  • A big batch held back

    After a bulk import, a trigger can suddenly return a large batch. Zapier's flood protection may hold it back instead of running everything.

  • Existing companies never fire

    Get Companies and Get Questionnaires remember what they have seen. An item that was there before the Zap went live does not start it, and none starts it twice.
Need help

Need help automating Contractbook with Zapier?

A person reads every message.

FAQ

Contractbook Zapier integration: questions

01Is the Contractbook Zapier integration free?
Yes, as far as Zapier is concerned. Contractbook is not a premium app, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: the free plan only builds two steps, one trigger and one action. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. A two-step Zap such as New Contract to Create Task fits the free plan.
02How many tasks does a Contractbook Zap use?
One task per action that succeeds, per run. The trigger costs nothing, and neither does Zapier checking for new data. A Zap that sends a contract uses one task each time; a Zap that creates a draft and then a task uses two. An action that fails is not counted. The cost to watch is a busy trigger like Draft Edited or Contract Updated, where every event runs the action again.
03Does the Contractbook integration run in real time?
Mostly, yes. Eight of the ten triggers are instant: Contractbook tells Zapier as soon as the event happens, and the plan interval does not apply, even on the free plan. The two exceptions are Get Companies and Get Questionnaires, which are polling triggers. Zapier checks them on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. An instant Zap shows a lightning bolt in the editor.
04What does it take to connect Contractbook to Zapier?
A Contractbook account and a Zapier account. You add the connection once from the Apps page with + Add connection, sign in to Contractbook in the tab that opens and allow access. Then plan for the required fields: five of the six actions need a template, and Pre-Fill Questionnaire needs an existing company and questionnaire. Anything you do not own yourself needs read or write access on the account. Then every Zap reuses it.
05Can a Contractbook Zap send a contract by mistake?
Yes, and it is the trap most specific to this app. Create Contract and Create Contract With Custom Parties create the contract and send it in one go. Testing the step in the editor runs it for real, so the recipient receives a real document. Test with an internal recipient, or start with Create Draft, check the result in Contractbook, and only switch to the sending action once the mapping is right.
06What if the Contractbook operation you need does not exist?
Then Zapier cannot do it with this app today. There is no search, no delete and no update action: the six actions all create contracts, drafts, tasks or pre-filled questionnaires. Work around it by starting from a trigger that already carries the data, or keep that step manual. If the gap is central to your process, compare the Contractbook operations each platform offers before building. On Zapier, a Zap only ever works with the ten triggers and six actions listed on this page.
07Zapier, Make or n8n for Contractbook?
Judge by criteria, not by brand. On Zapier, you get eight instant triggers, no search step and billing per successful action. Check which operations each platform offers for Contractbook, how each one bills a run, and whether you need a filter or more than one action, which on Zapier means a paid plan. Who will maintain the Zap matters as much as the price. On the free plan, Zapier stays at one trigger and one action per Zap.
Same platform

Other docs you might need on this stack.

Browse all integrations