Resources · Zapier integration

Clicksign Zapier integrationAutomate Clicksign with Zapier.

The Clicksign Zapier integration gives you 1 instant trigger and 19 actions, and no search step. Enough to create documents from a template, attach signers, chase signatures by email, SMS or WhatsApp, and clean up finished files without opening Clicksign.

See the 20 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Clicksign Zapier integration actually does for you

Clicksign is an electronic signature platform built around Brazilian legal requirements (integrity, authenticity, non-repudiation). Plugged into Zapier, it lets an event in Clicksign start a chain of steps, and lets other steps create, send or tidy up documents in Clicksign for you. No code, no copy-paste between tabs.

Three results people usually build first. A contract that drafts itself: a Clicksign event fires, Create Document From Template fills in your model, and Add Signer to Document puts the right person on it. A signature chase that never forgets: Notifications Email, Notifications SMS or Notifications WhatsApp nudges the signer through the channel you picked. A clean archive: Duplicate Document copies a finalized file, and Delete Document removes one that is finished or canceled.

Now the part the app page skips. Clicksign has no search step on Zapier, so a Zap cannot look up a document or a signer by name: you need the key, either carried by an earlier step or pulled with List Documents or List Templates. There is a single trigger, and it reacts to the events you pick in its settings. Nothing more granular.

If you are still weighing tools, the same app is covered on our Clicksign Make integration page, and the Make vs Zapier comparison lays out the criteria side by side.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it and does nothing until it shows up.
Action
What the Zap does after it starts: the step that creates, sends or removes something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts nothing else.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and quietly stops it otherwise.
Multi-step Zap
Any Zap with more than one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What a Clicksign Zap really costs

Clicksign is not a premium app, so it runs on the free plan. The bill is counted in tasks, and only successful actions count.

  • TriggerFree, never billed
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

The trigger costs nothing, and an action that fails is not billed. Every action that goes through costs one task on its own, so a three-action contract Zap uses three times what a single-action Zap does. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a second action or a filter and you are on a multi-step Zap, which needs a paid plan. The interval grid below concerns polling triggers only. The Clicksign trigger is instant, so it never waits for it.

Connect

Connect your Clicksign account in three steps

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. A connection is your Clicksign account linked to Zapier once, then reused by every step that touches Clicksign.

  2. 02

    Find Clicksign and confirm

    Type Clicksign in the search box of the dialog, pick it, then click Add connection. You need an existing Clicksign account, plus access to any document you do not own yourself and want the Zap to handle.

  3. 03

    Sign in and grant access

    A new tab opens on Clicksign. Sign in with the account the Zaps should act for, then grant Zapier access. Pick that account carefully: every document the Zap creates will live there.

First Zap

Your first Zap: a ready-to-sign document after each Clicksign event

GoalWhen Clicksign reports the event you track, create a document from your template, create the signer and attach that signer to the new document.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Clicksign as the app and Triggers Event When a Event Occur. as the event. Select the event, or the list of events, that should start it.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so you map the next steps on real data instead of guessing.

  3. 03

    Add the template action

    Add Create Document From Template. Fill the model key, then a path that starts with a slash and ends with .docx. Missing folders are created on the fly.

  4. 04

    Create and attach the signer

    Add Create Signer with its authentication method, then Add Signer to Document. Map the document key and signer key from the two previous steps, and set how the person signs.

  5. 05

    Test, then publish

    Test each action once and read what came back. When the document shows up in Clicksign with its signer, click Publish to switch the Zap on. Four steps means a paid plan.

Triggers

The Clicksign trigger

1 event starts a Zap when something happens in Clicksign, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Triggers Event When a Event Occur.

Instant trigger

In Zapier“Triggers when a event or a list of events occur.”

This is the only door into a Clicksign Zap. You choose one event, or a whole list of them, and the Zap wakes up each time Clicksign records one of those. Everything else on this page hangs off that choice, so it pays to pick the narrowest set of events that covers your need.

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 the next contract drafted the second Clicksign reports the event they track, not after someone remembers to check.
Watch out
picking a long list of events makes every one of them start the same steps; split them into separate Zaps when they need different follow-ups.
Actions

The 19 Clicksign actions, grouped by what you want done

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

1

Add Signer to Document

Action

In Zapier“Request to add a signatory to a document at Clicksign. This is a POST request for / api / v1 / lists. In the body, the key attributes of the document, key of the signatory and how the signatory will sign the document must be sent.”

Puts an existing signer on an existing document, and says in which capacity they sign. Three keys are mandatory: the document key, the signer key and Sign As.

When to use it
right after a document is created, to attach the client and the account manager in the same Zap.
Watch out
on a document with Sequence Enabled, you also have to define which group the signer belongs to.
2

Batches

Action

In Zapier“Request to batch creation of documents in Clicksign.”

Groups several documents into one batch for a single signer, from the document keys and that person's key.

When to use it
onboarding a new hire who has to sign a contract, a policy and a data form on day one.
Watch out
the optional Summary shows the batch documents as a collapsed list at signing time.
3

Cancel Document

Action

In Zapier“Request for canceling documents at Clicksign.”

Cancels a document from its key. It is the clean way to pull a document that should no longer be signed.

When to use it
a deal is lost and the quote waiting for a signature has to be pulled before the client signs by mistake.
Watch out
a canceled document becomes eligible for Delete Document, so do not chain the two unless you mean it.
4

Create Document From Template

Action

In Zapier“Request for creating documents at Clicksign via template.”

Builds a new document from one of your Clicksign models, identified by its key, and drops it at the path you set.

When to use it
a standard service agreement that only changes names and dates from one client to the next.
Watch out
the path must start with a slash and end with .docx. Folders that do not exist yet are created automatically, so a typo creates a stray folder.
5

Create Document

Action

In Zapier“Request for creating documents at Clicksign via upload”

Uploads a file into Clicksign and turns it into a document ready for signers. You give it a path inside Clicksign, file name included, and the file itself as a URL or a file from an earlier step.

When to use it
a proposal PDF produced elsewhere needs to land in Clicksign without anyone dragging it in.
Watch out
the path is a Clicksign folder, not a path on your server. Auto Close is on by default and Sequence Enabled is off.
6

Create Signer

Action

In Zapier“Request for the creation of signatories at Clicksign.”

Creates the person who will sign, with the way they authenticate: a token by email, by SMS, by WhatsApp, or a signature through the API. Only one method per signer.

When to use it
a new customer comes from your form and has to become a signer before any document reaches them.
Watch out
optional checks (selfie, handwritten signature, photo of an official ID) are off by default. Has Documentation is on, which skips the CPF and birth date at signing.
7

Delete Document

Action

In Zapier“Request to delete a document that has already been finalized or canceled at Clicksign. The result is permanent removal of the document from the account.”

Removes a document from the account for good. It only accepts a document that is already finalized or canceled.

When to use it
a housekeeping Zap that clears test documents once a project has been canceled.
Watch out
the removal is permanent. Test it on a throwaway document first, and never map the key from a step you have not checked.
8

Delete Signer

Action

In Zapier“Request to permanently delete a signatory”

Permanently deletes a signer from Clicksign, from the signer key. The person disappears from the account, not only from one document.

When to use it
a contact asks to be removed from your records and you want Clicksign to follow.
Watch out
if the goal is only to take someone off one contract, Remove Signer From Document is the gentler tool.
9

Duplicate Document

Action

In Zapier“Request to duplicate a document that has already been finalized at Clicksign.”

Makes a copy of a document from its key. Handy when the same signed contract has to start a second round with fresh signers.

When to use it
a yearly renewal that reuses last year's signed version as the starting point.
Watch out
only a document that is already finalized can be duplicated, so keep this step away from documents still out for signature.
10

List Documents

Action

In Zapier“Request to view part of the metadata of documents in Clicksign.”

Returns part of the metadata for a page of your documents. You must give a page number, so it reads the account one page at a time.

When to use it
a reporting Zap that copies document data into a spreadsheet for the finance team.
Watch out
one run covers one page. Reading the whole account means several runs, each billed as a task.
11

List Templates

Action

In Zapier“Request to view list of templates in Clicksign.”

Fetches the list of templates in your Clicksign account. Useful to find the model key that Create Document From Template asks for.

When to use it
a team that adds new models often and wants the keys available to the next step instead of copied by hand.
Watch out
it lists, it does not pick. You still choose which template the following step should use.
12

List Webhooks

Action

In Zapier“After registering the Webhook, it can be consulted.”

Shows the webhooks registered on your Clicksign account. A webhook is the call Clicksign makes to another tool when an event happens.

When to use it
an admin wants a record of which webhooks are registered, after setting up a few Zaps.
Watch out
this is a read-only, advanced step. It does not create or remove any webhook.
13

Notifications Email

Action

In Zapier“Request to send an e-mail message to a signatory requesting to sign a document or batch.”

Emails a signer to ask for a signature on a document or a batch. It is the polite reminder, sent by the Zap at the moment you decide.

When to use it
a client added to a contract should hear about it straight away, without anyone writing the reminder by hand.
Watch out
the signer has to be on the document or batch first, so place this action after Add Signer to Document.
14

Notifications SMS

Action

In Zapier“Request to send an e-mail message to a signatory requesting to sign a document or batch.”

Sends the signature request to the signer by text message, for a document or a batch. Same purpose as the email version, through the phone.

When to use it
field staff or drivers who rarely read email but always check their phone.
Watch out
keep it consistent with how the signer authenticates, or the person gets a message for a flow they cannot complete.
15

Notifications WhatsApp

Action

In Zapier“Key available in the document's JSON used in notification requests and in the Embedded Widget. Note: It is mandatory that the signer authentication is whatsapp.”

Pushes the signature request through WhatsApp, using the key available in the document's data. Same request, a third channel.

When to use it
retail or real estate clients who live on WhatsApp and ignore emails from unknown senders.
Watch out
it is mandatory for the signer's authentication to be whatsapp. Set that in Create Signer, otherwise this step has nothing to work with.
16

Remove Signer From Document

Action

In Zapier“Request to remove a signatory from a document at Clicksign.”

Takes a signer off a document without deleting the signer itself. It works from the list key, the link between that person and that document.

When to use it
a client swaps the person in charge, and the old contact must not sign anymore.
Watch out
the list key is not the signer key. It sits in the document's data, so map it from a step that returned the document.
17

View Document

Action

In Zapier“Request to view the metadata of documents in Clicksign.”

Reads the metadata of one document from its key and hands it to the next steps. Nothing changes in Clicksign.

When to use it
you need the list key of a signer before removing them, and only the document key is at hand.
Watch out
it counts as an action, so it uses a task each time it succeeds, even though it only reads.
18

View Signer

Action

In Zapier“Request to view the metadata of the signatories at Clicksign.”

Pulls the details Clicksign keeps on one signer, from the signer key, so later steps can use them.

When to use it
before a reminder, to check which authentication the signer has and route to the right notification.
Watch out
it needs the signer key, not an email address. Clicksign has no search step here to find a signer by name.
19

Update Document

Action

In Zapier“Request to change document settings at Clicksign.”

Changes the settings of a document you already have, from its key. The two switches that matter are Auto Close and Sequence Enabled.

When to use it
a contract that suddenly needs signatures in a strict order, legal first and then the client.
Watch out
Auto Close, on by default, finalizes the document after the last signature. Switch it off if more signers may join later.
When it breaks

When a Clicksign Zap breaks

Zapier attaches no help article to Clicksign. What follows are the general limits that apply here.

Four cases worth knowing before you publish, all tied to the timing of the Zap or to a loop you did not see coming.

  • Nothing from before the switch-on

    A Zap only reacts to events that happen after you publish it. Documents already signed or created before that are ignored, and moving them is a separate job.

  • A Zap that triggers itself

    If an action creates the very kind of event the trigger listens for, the Zap sets itself off again and again, and burns through your tasks fast.

  • A sudden flood of events

    A bulk import or a migration on the Clicksign side can send a huge batch at once. Zapier's flood protection may hold those runs back.

  • A failed step is not billed

    An action that does not go through costs no task. The flip side: the document was not created, so check the Zap history after the first runs.
Need help

Need help automating Clicksign with Zapier?

A person reads every message.

FAQ

Clicksign Zapier integration: frequent questions

01Is the Clicksign Zapier integration free?
Yes, it works on the free plan, because Clicksign is not a premium app on Zapier. The free plan gives 100 tasks a month and unlimited Zaps, with polling checks every 15 minutes. The catch is the shape of those Zaps: one trigger and one action, nothing more. A contract Zap that creates a document and then attaches a signer has two actions, so it is a multi-step Zap and needs a paid plan.
02How many tasks does a Clicksign Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap with Create Document From Template, Create Signer and Add Signer to Document uses three tasks per run when all three work. An action that fails is not counted. Read-only steps such as View Document or List Documents still count as actions, so they use a task each time they go through. Plan your volume on the number of actions, not on the number of documents.
03Does the Clicksign trigger work in real time?
Yes. The Clicksign trigger is instant: Clicksign tells Zapier the moment the event happens, and the Zap starts straight away. The interval grid of the plans, from 15 minutes on Free down to 1 minute on Team and Enterprise, only concerns polling triggers, which Zapier checks on a timer. None of that applies here. A free account gets the same speed as an Enterprise one on this trigger, which is the most useful thing to know before paying for a faster plan.
04What does it take to connect Clicksign to Zapier?
A Clicksign account, plus access to any document you do not own yourself and want the Zap to touch. On the Zapier side, open Apps, click + Add connection, pick Clicksign, then sign in on the tab that opens and grant access. The connection is then reused by every Clicksign step in every Zap. Pick the account carefully, since the documents your Zaps create will live there and every Zap built on that connection acts for it.
05Why does Notifications WhatsApp fail for some signers?
Because that action requires the signer's authentication to be whatsapp. When Create Signer sets the Auths field to email, SMS or API, the signer has no WhatsApp channel and the request cannot go out. Only one authentication method is allowed per signer, so choose it from the channel you plan to chase on. For signers already created with another method, use Notifications Email or Notifications SMS instead, matching what they were set up with.
06What if the Clicksign operation you need does not exist?
Then the Zap cannot do it directly, and the honest move is to check the 19 actions again under another name. View Document, View Signer and the List actions often cover what looks missing, as long as you have the key. There is no search step on Clicksign, so finding a document by name is out. Past that point, our Zapier team can tell you whether another route exists, or whether the flow is better split into two Zaps that share a key.
07Zapier, Make or n8n for Clicksign?
It depends on your criteria, not on a winner. Three questions settle it. Does the tool expose the Clicksign operations your flow needs? On Zapier, that means 1 instant trigger and 19 actions, with no search step. How is it billed against your volume? Zapier counts one task per successful action. And who on your team will build and maintain the Zaps? Answer those for each tool, with the same contract flow in mind, and the choice usually makes itself.
Same platform

Other docs you might need on this stack.

Browse all integrations