Click and Sign
DocumentsClick&Sign is the electronic signature product of Lleida.net, a Spanish certified-communications provider. Agents start signature processes under a stored configuration, attach documents and signers, run bulk sends, and download the signed evidence.
What This Integration Enables
Click&Sign is the electronic signature product of Lleida.net, a Spanish certified-communications provider, and its API is built on a separation most signature platforms do not make. How a signature process behaves lives in a stored configuration set up once: which emails go out, which signature methods are allowed, whether a document is signed on reading or on signing, whether an access code is required. Each call then supplies only the document, the people, and where their signatures go. That is a governance decision expressed as an API shape, and it suits agent work exactly, because it means the automated part of the process is the part that changes and the legal part is the part that does not.
FlowRunner agents pick a configuration rather than pick settings. A low-value order gets the configuration legal built for low-value orders; a supplier agreement above threshold gets the one with a qualified certificate. Get Configuration reads back what a configuration will actually cause before a flow is wired to it, so the flow's author knows what they are triggering. Signature placement is by millimeter coordinates from the page margins rather than percentages, which is unusual enough to be worth naming, and the connector handles it. Everything else the agent does, from status sweeps to evidence collection, works against a process whose rules a person already approved.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
The configuration is the risk control
A purchase agreement reaches signing stage in Pipedrive or HubSpot. The agent reads the contract value, selects the stored configuration that matches that tier, and calls Start Signature with the document, the signatories, and the placement coordinates. It does not choose the signature method, the notification wording, or the access code requirement, because those are not its to choose. Procurement and legal maintain two or three configurations between them, and changing policy means editing a configuration rather than auditing every flow that sends a contract.
-
Fix the address, do not restart the process
Get Signatory Status shows a delivery failure on one signatory of a three-party agreement. Instead of canceling and raising a new process, which would discard the signature the other two parties already applied, the agent looks up a better address in the CRM and calls Edit Signatory to correct the contact details on the running process. Send Reminder then reaches the corrected address. The process keeps its identifier, its evidence, and its completed signatures, and the supplier never learns that anything went wrong.
-
The completed process and everything around it
When Get Signature Status reports the evidence is ready, the agent calls Download Signed Document for the executed contract and walks List Files to pull the evidence documents that sit alongside it. Get Signatory Details records what each party actually did and when. All of it lands together in Google Drive next to the vendor record, and a line is appended to the contract register in Google Sheets. The signed PDF on its own is a document. The signed PDF with its evidence set is a record, and the difference matters the day somebody disputes it.
Human-in-Loop Highlight
Click&Sign's bulk flow has a deliberate asymmetry, and it is the reason this page's gate sits where it does. Start Bulk Signature contacts everyone in the file at once, in a single call. Undoing it does not work the same way: each resulting process has to be canceled individually, one call at a time, and every one of those suppliers has already received the message. So the cost of sending is constant and the cost of the mistake scales with the size of the file. Click&Sign anticipated this and shipped the safe half separately. Validate Bulk File checks the whole file and starts nothing, and Get Bulk Validation Result reports what would be created and what is wrong with the rows that would not be. FlowRunner agents always run that half, then stop: "The Q4 terms update validates 212 of 218 rows. Six failed: four missing a signatory email, two with a supplier name that does not match the vendor master. Correcting them or sending the 212?" A person answers. The agent can build the file, check it, and explain the failures in seconds. Deciding to reach 212 suppliers at once is not a speed problem, and it is not the agent's call.
Agent Capabilities
19 actionsSignatures
8- Start Signature Uploads a PDF and starts a signature process against a stored configuration. Everyone listed is contacted immediately, by email or SMS according to the configuration, and this cannot be recalled, only canceled. The call supplies the document, the people, and where their signatures go; the configuration decides the rest.
- Get Signature Status Reads where a signature process has got to, and whether its evidence is ready to download. The polling step behind completion handling.
- Get Signatory Status Reads where one person has got to on a signature process, including delivery failures that a process-level status will not show.
- Get Signature List Lists signature processes, narrowed by whichever filters are supplied. The sweep behind reporting and stalled-process detection.
- Get Signatory Details Reads everything recorded about one signatory, including the evidence of what they did. The record that turns a signature into something defensible.
- Send Reminder Contacts a signatory again about a process they have not finished. This reaches a real person, so checking their status first is what separates a useful nudge from noise.
- Cancel Signature Stops a signature process. Anyone who has not signed can no longer do so, and what has already been signed stays on the record.
- Edit Signatory Corrects a signatory's contact details on a process that is already running, which is how a bounced address or a wrong number is fixed without starting again.
Documents
3- List Files Lists the files attached to a signature process: the documents themselves, the signed copies, and the evidence.
- Download File Downloads one file from a signature process into flow file storage and returns a link to it. List Files supplies the identifier.
- Download Signed Document Downloads the signed document from a completed process into flow file storage, ready to file against the record that started it.
Configurations
4- List Configurations Lists the stored signature configurations on the account. A configuration decides the emails, the signature type, and most other behavior of a process, and Start Signature names one.
- Get Configuration Reads one stored configuration in full, which is how a flow's author sees what a process will actually do before starting one.
- Set Configuration Creates or replaces a stored configuration. This is also the operation that sets the notification URL a process posts status changes to. The settings object is passed through as given, because the configuration surface is large and versioned by the vendor.
- Set Configuration Status Turns a stored configuration on or off. A configuration that is off cannot start a process, which is how one is retired without being deleted.
Bulk
4- Validate Bulk File Checks a bulk signature file without starting anything. The safe half of the bulk flow, and the operation this page's human gate is built around.
- Get Bulk Validation Result Reads the outcome of a bulk file check: what would be created, and what is wrong with the rows that would not be.
- Start Bulk Signature Starts every signature process in a validated bulk file. This contacts everyone in the file at once and cannot be recalled; each process then has to be canceled individually.
- Get Bulk Status Reads how a bulk job is getting on, and what it produced.
Frequently Asked Questions
What can FlowRunner do with Click and Sign?
FlowRunner agents can run Start Signature, Get Signature Status, and Get Signatory Status in Click and Sign, plus 16 more actions.
Does connecting Click and Sign to FlowRunner require OAuth?
No. Click and Sign connects to FlowRunner with an API key, no OAuth flow required.
Can Click and Sign trigger a FlowRunner workflow automatically?
Click and Sign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Documents integrations
Start building with Click and Sign
Free plan, no card required. Connect in minutes.