Resources · Make integration

Click and Sign Make integrationAutomate Click and Sign with Make.

Can a signature request leave on its own when a deal is ready? The Click and Sign Make integration gives you 4 action modules to start signatures, check their status and fetch the signed files. This page shows how to link your account and build a first scenario.

Try the Click and Sign integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Click and Sign Make integration do for you?

The Click and Sign Make integration links your Click and Sign account to Make, a no-code tool where you chain apps into a scenario, the automation you build. Each brick of that chain is a module. Here you get 4 of them, all actions: they do something in Click and Sign when an earlier step asks for it.

Signatures that start themselves. A sales team marks a quote as accepted in its CRM, and Start a Signature sends the contract to the signatories without anyone opening Click and Sign.

A clear view of pending files. An HR assistant keeps a sheet of employment contracts; Get a Signature Status reads where each process stands so the sheet stays accurate.

Signed copies filed in the right place. Once a process is complete, Get a Document pulls the signed files and the signature evidence, ready to be stored in your drive by the next module.

Make's own documentation for this app is limited: it says there is not enough public information to describe it in full. When a listed module falls short, Make an API Call reaches the rest of the Click and Sign API with the same connection. The same app may also exist in n8n; the n8n vs Make page lays out how the two tools differ. To learn the editor step by step, see Make training, and check Make pricing before you scale up.

Connect

How do you connect Click and Sign to Make?

  1. 01

    Add a Click and Sign module

    In your scenario, add any Click and Sign module, for example Start a Signature, then click Create a connection. A connection is your Click and Sign account linked to Make once, then reused by every module of the app.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when you manage several accounts. Then authorize Make on the Click and Sign page that opens, or paste the key Click and Sign gives you, depending on what the window asks for.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the list of every Click and Sign module, so the next ones you add in this scenario or another are ready without a second login.

First scenario

Your first scenario with Click and Sign

GoalWhen a deal is marked as won in another app, Make starts a Click and Sign signature with the signatories.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Click and Sign has no trigger, so this first module comes from the app that holds your deals.

  2. 02

    Pick the starting app

    Search your CRM or form app by name, choose the module that watches for new records, and connect its account. Each record it sends on is a bundle, one item flowing to the next module.

  3. 03

    Add Start a Signature

    Click the + to the right of the first module, search Click and Sign and pick Start a Signature. Create the connection, then map the signer details and the file from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received, and check in Click and Sign that the signature process really started.

  5. 05

    Schedule and switch on

    On the first module, set the schedule: a new scenario runs every 15 minutes by default. Then switch the scenario on, and each new won deal will send its contract out for signature.

Modules

What each Click and Sign module does

Click and Sign gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Click and Sign1

Get a Document

Action

In Make“Retrieves any file associated with the signature process, the documents to be signed on the web or attached to any of the emails, and the signature evidence resulting from the process or the documents signed.”

Pulls a file out of a signature process into your scenario: the documents to sign, the attachments sent by email, the signed copies or the evidence that proves the signature. You can then pass it to a storage or email module.

When to use it
right after a process is finished, to archive the signed contract and its evidence in the client folder.
Watch out
check the status first with Get a Signature Status, so you do not archive a file that nobody has signed yet.
Click and Sign2

Get a Signature Status

Action

In Make“The Get Signature Status retrieves the status of a specific signature process.”

Tells your scenario where one signature process stands, so the next modules can react to it instead of you checking by hand. Each call reads a single process.

When to use it
to update a tracking sheet or a CRM field before you decide whether to send a reminder or fetch the signed files.
Watch out
each status check costs one operation, the execution of a module that Make counts on your plan, so keep the list of processes you read short.
Click and Sign3

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call”

Opens the rest of the Click and Sign API to your scenario, using the connection you already created. It is the way out when none of the three other modules covers what you need.

When to use it
when the task you have in mind is missing from the list, which can happen since Make's own documentation for this app is limited.
Watch out
you describe the request yourself, so you need the Click and Sign API reference at hand before you build it.
Click and Sign4

Start a Signature

Action

In Make“Initiates a signature process with the signatories. The maximum number of files at a time is 20. The maximum total size of file attachments allowed cannot exceed 25MB.”

Launches a signature process with your signatories straight from Make, so a contract goes out the moment the previous step has the data ready. This is the module most scenarios with this app are built around.

When to use it
when a quote is accepted, a new hire is confirmed or a form is completed and the paperwork should follow.
Watch out
one process takes up to 20 files and 25 MB of attachments in total, so split larger bundles of documents.
Need help

Need help automating Click and Sign with Make?

A person reads every message.

FAQ

Questions about the Click and Sign Make integration

01Is the Click and Sign Make integration free?
Yes, on the Make side. Click and Sign is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Click and Sign subscription is a separate matter, not covered here.
02What do you need to connect Click and Sign to Make?
A Click and Sign account and a Make account. Make's documentation lists no specific prerequisite for this app. You add a Click and Sign module, click Create a connection, optionally name it, then authorize Make on the Click and Sign page or paste the key the app provides, and click Save. The connection is created once and reused by all 4 modules, in this scenario and in any later one.
03Does the Click and Sign Make integration have a real-time trigger?
No. Click and Sign has no trigger module in Make, only 4 actions. A scenario therefore starts from something else: a trigger from another app, such as a new row or a new deal, or Make's own schedule on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval. Paid plans can go down to 1 minute between two runs.
04What if a Click and Sign module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Click and Sign API from your scenario with the same connection, which covers what Start a Signature, Get a Signature Status and Get a Document do not. Keep the Click and Sign API reference close, because you write the request yourself. Also note that Make describes its documentation for this app as limited, and that Start a Signature accepts up to 20 files and 25 MB of attachments per process.
05Should you use Make or n8n for Click and Sign?
It depends on the tool your team already works in. On Make, Click and Sign offers 4 action modules, including Make an API Call for the rest of its API, and runs from the Free plan. The same app often has an n8n node too, so check that side against your needs. Compare on the modules each tool offers for the tasks you have in mind, and on which editor your team is comfortable maintaining over time.
Same platform

Other docs you might need on this stack.

Browse all integrations