--- title: "Clicksign Integration" description: "Clicksign is a Brazilian electronic signature platform built around the envelope. Agents assemble documents, signers, and identity requirements in a draft, activate it to send everything at once, and manage templates, folders, and webhook subscriptions." url: https://flowrunner.ai/integrations/clicksign date_modified: 2026-09-04T14:07:24-07:00 --- # Clicksign [Documents](https://flowrunner.ai/integrations/category/documents-forms) Clicksign is a Brazilian electronic signature platform built around the envelope. Agents assemble documents, signers, and identity requirements in a draft, activate it to send everything at once, and manage templates, folders, and webhook subscriptions. 41 actions · API key · available [Clicksign website](https://www.clicksign.com/) · [Platform Documentation](https://www.clicksign.com) · Capability data verified 2026-08-13 1. A contract reaches signing stage in the CRM 2. Create Envelope opens a draft with its deadline, its reminder interval, and what happens when time runs out 3. Create Document From Template renders the contract, filling the template variables from the record 4. Create Signer adds each party with the channel they answer on and whether they may refuse 5. Create Authentication Requirement binds each signer to each document with the proof the contract's value warrants 6. List Requirements reads the envelope back, so the matrix can be shown as it actually stands 7. A person confirms the requirement matrix, and that confirmation is what releases Activate Envelope ## What This Integration Enables Clicksign is a Brazilian electronic signature platform built around the envelope, and the envelope is what makes it a good fit for agent work. An envelope starts as a draft and does nothing at all until it is activated. Documents, signers, requirements, and observers are added to it one call at a time, and none of those calls reaches a human being. Then a single operation releases the whole thing. That structure gives a flow a place to stand, gather, and check, which is unusual in this category and is the reason this connector reads differently from the send-in-one-call platforms next to it in our [connectors](https://flowrunner.ai/concepts/connectors) catalog. What gets assembled inside that draft is the other half of the story. Clicksign's requirement vocabulary is built for the Brazilian market and it is deep: an email, SMS, or WhatsApp token, a Pix transfer, an ICP Brasil certificate, facial biometrics, or document scanning, chosen per signer per document. On top of that, a qualification requirement records in what capacity somebody signs, as signatory, party, or contractor, and that appears next to their signature on the finished document. An initials requirement can demand a mark on named pages. FlowRunner agents assemble all of it from the record that triggered the contract, then hand the finished draft to a person for the one decision the API cannot make. ### Without FlowRunner **Assembly and sending are one act**: The contract is built and dispatched in the same click, so a missing party is discovered afterward **Identity proof by default**: Every signer gets the same check, whichever document they are signing and whatever it is worth **Evidence gathered on request**: Somebody exports the audit history when a dispute makes it necessary ### With FlowRunner **Assembly and sending are separate**: The envelope is built up as a draft and reviewed whole, and activation is its own deliberate step **Identity proof per signer per document**: The requirement is set from the contract's value and the signer's role, and read back before release **Evidence gathered on completion**: List Document Events files the compliance record next to the signed PDF, every time ## Use Case Scenarios ### Assemble the whole package, release it once A deal closes in [Pipedrive](https://flowrunner.ai/integrations/pipedrive) or [RD Station](https://flowrunner.ai/integrations/rd-station). The agent calls Create Envelope with the deadline and reminder interval the contract type calls for, then Create Document From Template to render the agreement with the customer's values, reading Get Template first so the variable names match what the template defines. Create Signer adds the customer's authorized signatory with WhatsApp delivery and the internal approver with email, and Create Signature Watcher adds the account manager as an observer who is kept informed without being asked to sign. Nothing has left the building. The envelope is a draft, and it stays one until somebody activates it. ### Matching the proof to the money The same flow reads the contract value before building the requirements. Below the threshold, Create Authentication Requirement asks for an email token and the process stays light. Above it, the same operation asks for facial biometrics or an ICP Brasil certificate. Create Qualification Requirement records that the signer signs as the contracting party rather than as a witness, so the capacity appears on the document itself. On a multi-page schedule, Create Initials Requirement asks for a handwritten mark on the pages that carry the pricing. The policy is written once in the flow and applied identically to every contract, instead of depending on which template someone happened to start from. ### The compliance record files itself When the envelope closes, the agent walks List Documents and calls List Document Events for each one, which returns who viewed the document, who signed it, when, and any custom events recorded against it. That history goes into [Google Drive](https://flowrunner.ai/integrations/google-drive-api) alongside the executed PDF and a summary posts to legal in [Slack](https://flowrunner.ai/integrations/slack). Because document metadata comes back on the webhook callbacks, the agent's own identifiers travel through the whole process and land on the filed record, so the evidence is already joined to the deal rather than needing to be matched to it later. ## Human-in-Loop Highlight A Clicksign requirement binds one signer to one document. A signer who has to authenticate on two documents needs two requirements, and there is nothing that will tell you when one is missing. An envelope with an incomplete requirement matrix is not invalid. It activates cleanly, the signer receives it, and they sign with whatever proof was actually attached to them, which may be an email token on a document that the company's own policy says needs an ICP Brasil certificate. List Requirements will faithfully report what is there. No operation in this connector reports what should have been there, because that judgment lives in a policy the API has never seen. So FlowRunner agents build the whole draft and stop in front of Activate Envelope, posting the matrix as a grid: "Supply agreement, 2 documents, 3 signers. Requirements set: R. Almeida, facial biometrics on both documents, signs as party. J. Neves, email token on the main agreement only, signs as signatory. M. Duarte, no authentication requirement on either document. Activate?" The third line is the one worth a person's eyes. Activation sends the request to every signer on the envelope and cannot be taken back, and a signature collected under the wrong proof is not something a later call can repair. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 41 actions ### Envelopes 7 - **Create Envelope** Creates an envelope, the container that documents, signers, and requirements are added to. It starts as a draft and does nothing until activated, so a flow builds it up first and activates last. Automatic closing, reminder intervals, and deadline behavior are all set here. - **List Envelopes** Returns a page of the envelopes on the account, narrowable by status. The sweep behind pipeline reporting and stalled-contract detection. - **Get Envelope** Returns one envelope with its status and settings, which is how a flow knows whether it is still a draft, running, closed, or canceled. - **Update Envelope** Changes an envelope's settings, and is also how an envelope moves between statuses. Setting the status to running activates a draft and sends the request to every signer on it. - **Activate Envelope** Activates a draft envelope through its dedicated route, which starts the signing process and sends the request to every signer. Everything the envelope needs must already be on it. This is the call this page's human gate exists for. - **Delete Envelope** Permanently deletes an envelope and everything on it. - **Notify Envelope Signers** Sends the signature request again to every signer who has not signed yet, optionally with a message of your own. ### Documents 7 - **Upload Document** Adds a document to an envelope by uploading its content. Metadata supplied here comes back on the webhook callbacks, which is the usual way to carry your own identifiers through the process. - **Create Document From Template** Adds a document to an envelope by rendering a Clicksign template with your values. The variable names must match what the template defines, which Get Template reports. - **List Documents** Returns the documents inside an envelope. - **Get Document** Returns one document inside an envelope, with its status and the links to its files. - **Update Document** Changes the filename or the metadata of a document inside an envelope. - **Delete Document** Removes a document from an envelope. - **List Document Events** Returns the event history of one document: who viewed it, who signed, when, and any custom events recorded against it. This is the compliance record, and it is worth filing every time rather than fetching on demand. ### Signers 5 - **Create Signer** Adds a signer to an envelope. Each channel is set separately, so the request, the reminders, and the signed copy can each go by email, WhatsApp, or SMS. A signer can be required to give their CPF and date of birth, allowed to refuse, asked to share their location, and placed in a signing group so groups sign in order. - **List Signers** Returns the signers of an envelope, each with their own signing status. - **Get Signer** Returns one signer of an envelope with their status and settings. - **Delete Signer** Removes a signer from an envelope. The remaining signers are unaffected. - **Notify Signer** Sends the signature request again to one signer, with a fully customizable email if wanted: subject, heading, greeting, body, button text, and closing line, plus whether the token, the QR code, and the process details are shown. ### Requirements 6 - **Create Authentication Requirement** Says how a signer must prove who they are before signing a document, from an email or SMS token through to a Pix transfer, an ICP Brasil certificate, facial biometrics, or document scanning. One requirement binds one signer to one document. - **Create Qualification Requirement** Says in what capacity a signer signs a document, as the signatory, as a party, or as the contractor. This is what appears next to their signature on the finished document. - **Create Initials Requirement** Requires a signer to initial named pages of a document, either as typed initials or as a handwritten mark, with a positioned tag available so the mark lands where the document says it should. - **List Requirements** Returns the requirements on an envelope: who must prove what, in which capacity, and where they must initial. The read behind this page's review step. - **Get Requirement** Returns one requirement of an envelope. - **Delete Requirement** Removes a requirement from an envelope, so the signer is no longer asked for it. ### Observers 3 - **Create Signature Watcher** Adds an observer to an envelope, somebody kept informed of the signing process without being asked to sign anything. - **List Signature Watchers** Returns the observers of an envelope. - **Delete Signature Watcher** Removes an observer from an envelope, so they stop being kept informed. ### Templates 5 - **Create Template** Creates a template from a Word file, whose variables become the fields Create Document From Template fills. - **List Templates** Returns a page of the templates on the account. - **Get Template** Returns one template with the variables it defines, which are the keys Create Document From Template expects. The discovery call worth making before filling anything. - **Update Template** Renames a template or moves it to another folder. - **Delete Template** Deletes a template. Documents already created from it are unaffected. ### Folders 3 - **Create Folder** Creates a folder for filing envelopes and templates, optionally inside another. - **List Folders** Returns a page of the folders on the account. - **Get Folder** Returns one folder. ### Webhooks 5 - **Create Webhook** Registers a URL that Clicksign calls when events happen, optionally narrowed to named events and created either active or inactive. - **List Webhooks** Returns the webhooks registered on the account, each with its endpoint, its events, and whether it is active. Worth reading before touching any of them, because an account can carry several and they belong to different people. - **Get Webhook** Returns one registered webhook by its identifier. - **Update Webhook** Changes the endpoint, the events, or the active state of a registered webhook. Setting it inactive stops delivery without removing the registration. - **Delete Webhook** Removes a registered webhook, so Clicksign stops calling it. Deleting somebody else's webhook silently stops their integration, which is why the listing call comes first. ## Frequently Asked Questions ### What can FlowRunner do with Clicksign? FlowRunner agents can run Create Envelope, List Envelopes, and Get Envelope in Clicksign, plus 38 more actions. ### Does connecting Clicksign to FlowRunner require OAuth? No. Clicksign connects to FlowRunner with an API key, no OAuth flow required. ### Can Clicksign trigger a FlowRunner workflow automatically? Clicksign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Clicksign?** This integration exposes Clicksign to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/clicksign. Site index: https://flowrunner.ai/llms.txt