Resources · Make integration

Clicksign Make integrationAutomate Clicksign with Make.

What if every signed deal started without a single copy and paste? The Clicksign Make integration gives you 8 modules: 7 actions and 1 search. This guide is for sales and ops teams that send contracts, and it walks you from connecting your account to a live first scenario.

Try the Clicksign integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Clicksign Make integration do?

The Clicksign Make integration lets Make create documents in your Clicksign account, register the people who must sign them and read those documents back, without code. You build a scenario, the automation Make runs for you, out of modules, the bricks that each do one job in one app.

Contracts that prepare themselves. When a deal closes in another app, Create a Document Via Template fills your Clicksign template with the client data, and Add a Signatory to a Document puts the right person on it. Nobody retypes a name.

Signers kept in one place. Create a Signatory registers a new person once, so the same contact can be attached to the next document instead of being entered again.

A status check your team can trust. List Documents returns the documents of the account as separate bundles (one bundle is one item passing to the next module), and Get a Document reads one of them in detail before you update a spreadsheet or warn a manager.

Clicksign has no trigger in Make: nothing in Clicksign starts a scenario on its own, so the flow opens on another app or on a schedule. If you also look at n8n, the n8n vs Make comparison lays out the differences, and the Make pricing page explains what each plan includes. Stuck on an error? Make troubleshooting covers the usual fixes.

Connect

How do you connect Clicksign to Make?

  1. 01

    Generate your API token

    In Clicksign, open Settings in the side menu, go to the API tab and click Generate access token. Give the token a name, confirm, then copy the token shown on screen. You need an active Clicksign account with API access.

  2. 02

    Open a Clicksign module

    In your Make scenario, add any Clicksign module and click Create a connection. A connection is your Clicksign account linked to Make once; every Clicksign module of your scenarios reuses it.

  3. 03

    Paste the token and save

    Type a label in Connection name if you want to recognize it later, it is optional. Paste the token you copied from Clicksign, or follow the instructions Make shows on screen, and save the connection.

First scenario

Your first scenario with Clicksign

GoalWhen a deal is won in another app, Make creates the contract in Clicksign from a template and attaches the signer.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your deals live and its trigger, the module that starts the flow.

  2. 02

    Add the template module

    Click the + on the right, search for Clicksign and choose Create a Document Via Template. Select your connection or click Create a connection with your API token.

  3. 03

    Map the deal data

    Fill the module fields with the client data coming from the first module. Make lets you pick those values from the previous bundle instead of typing them.

  4. 04

    Attach the signer

    Add Add a Signatory to a Document after it, and map the document created by the previous module so the signer lands on the right contract.

  5. 05

    Test with Run once

    Click Run once and create a test deal. Open each module to read the bundle it received, and check the new document in Clicksign.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then turn the scenario on. Each module run costs one operation on your plan.

Modules

What Clicksign can do in Make

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

Clicksign1

Add a Signatory to a Document

Action

In Make“Adds a single signatory to a document.”

This module puts one person on a document as a signer, so the contract is ready to be signed without opening Clicksign.

When to use it
right after a module that created the document, when the signer is already known in Clicksign or was just created by Create a Signatory.
Watch out
it adds one signatory at a time, so a contract with two signers needs the module twice in the flow.
Clicksign2

Create a Document Via Template

Action

In Make“Creates a new document via template.”

You get a finished document built from a template you already keep in Clicksign, with the gaps filled by data from earlier modules.

When to use it
standard contracts, NDAs or service agreements where only the client details change from one deal to the next.
Watch out
the module starts from a template, so the template has to exist in your Clicksign account before the scenario runs.
Clicksign3

Create a Document Via Upload

Action

In Make“Creates a new document via upload.”

Here the document comes from a file you already have, so a PDF produced elsewhere becomes a Clicksign document ready for signers.

When to use it
when contracts are drafted by hand or generated by another tool, and you only need Clicksign for the signature step.
Watch out
map the file from the previous module; on the Free plan, Make handles files up to 5 MB.
Clicksign4

Create a Signatory

Action

In Make“Creates a new signatory.”

A new person is registered in your Clicksign account as someone who can sign, which saves your team from entering the same contact over and over.

When to use it
when a new client or supplier appears in your CRM and will receive documents later.
Watch out
to put this person on a contract, follow it with Add a Signatory to a Document in the same scenario.
Clicksign5

Get a Document

Action

In Make“Gets a single document.”

This one reads a single document from Clicksign and hands its details to the next module, so the rest of the scenario can work with them.

When to use it
when you already hold the document reference, for example stored in a spreadsheet row, and want its current state before updating your records.
Watch out
it reads one document per run; when you do not know which one, start with List Documents.
Clicksign6

Get a Signatory

Action

In Make“Gets a single signatory.”

You receive the details of one signer stored in Clicksign, handy when a reminder sent from another app needs that person's details.

When to use it
in a follow-up scenario, after Get a Document, when you need the signer data rather than the document itself.
Watch out
it reads one signatory at a time, so each call is one operation on your Make plan.
Clicksign7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach any endpoint of the Clicksign API through the same connection, which covers the jobs the seven other modules leave out.

When to use it
when you need an action that has no dedicated module, and you are comfortable reading the Clicksign API documentation.
Watch out
you write the request yourself, so test it with Run once before switching the scenario on.
Clicksign8

List Documents

Search

In Make“Lists all documents.”

This search brings back the documents of your Clicksign account, each one as its own bundle, so the rest of the scenario can process them one by one.

When to use it
to build a signature dashboard in a spreadsheet, or to find a document before reading it with Get a Document.
Watch out
every returned bundle triggers the next modules, which multiplies the operations counted on your plan.
Need help

Need help automating Clicksign with Make?

A person reads every message.

FAQ

Clicksign and Make: frequent questions

01Is the Clicksign Make integration free?
Yes, on the Make side. Clicksign is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the limit on active scenarios. Your Clicksign subscription is separate and depends on Clicksign itself.
02What do you need to connect Clicksign to Make?
An active Clicksign account with access to the API, and an API token. You generate the token in Clicksign under Settings, in the API tab, with the Generate access token button, then copy it. In Make, you click Create a connection on any Clicksign module, optionally name the connection, and paste the token before saving. If Make shows extra instructions on screen, follow them. The connection is then reused by every Clicksign module in your scenarios.
03Does the Clicksign Make integration work in real time?
No, because Clicksign has no trigger in Make: none of its 8 modules can start a scenario. You start the flow another way, either with a trigger from another app, such as a CRM or a form, or with the schedule on the first module, which runs every 15 minutes by default. On the Free plan the shortest interval is 15 minutes, and paid plans go down to 1 minute.
04What if a Clicksign module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Clicksign API with the same connection, so an action that has no dedicated module is still reachable. You write the request yourself, based on the Clicksign API documentation. The Make documentation for this app also carries a notice that parts of it were generated with AI, so verify important details with Clicksign directly before you rely on them in production.
05Should you use Make or n8n for Clicksign?
It depends on what your team already runs. In Make, Clicksign comes with 8 modules covering documents and signatories, plus Make an API Call for the rest, all built visually in scenarios. If your automations already live in n8n, check whether a Clicksign node exists there and covers your steps. Neither choice is better by default: pick the tool where your other workflows and your team's skills already are, then test one real case.
Same platform

Other docs you might need on this stack.

Browse all integrations