Autentique

Autentique is a Brazilian electronic signature platform that reaches signers by email, SMS, or WhatsApp. Agents upload a PDF, name who signs and how they prove identity, organize documents into folders, and track every signature to completion.

27 actions API key available

Autentique website Platform Documentation Capability data verified 2026-08-13

A deal reaches Won in the CRM

Agent builds the signer list from the deal's contacts, with the channel each one actually answers on

The deal value decides the identity proof each signer faces, from an email link through to facial biometrics

Create Document uploads the PDF and contacts every signer at once, by email, SMS, or WhatsApp

Get Document reports who has viewed, who has signed, and whose identity check is waiting on a person

A pending manual identity review posts to the deal owner with the evidence the signer submitted

The owner calls Approve Biometric Check or Reject Biometric Check, and the signature stands or does not

What This Integration Enables

Autentique is a Brazilian electronic signature platform, and the assumption it is built on is that reaching a signer is a separate problem from proving who they are. A signer with an email address gets emailed. A signer with a phone number is reached by WhatsApp or SMS. A signer with only a name gets a link the flow delivers itself. Independently of any of that, each signer can be asked for an SMS code, a photo ID, a liveness check, or facial biometrics, chosen one signer at a time. FlowRunner agents make both choices from data they already hold, which is the difference between a policy that exists in a document and a policy that runs.

The connector covers the full document lifecycle: create and send in one call, add or remove signers on a document already in flight, file documents into shared folders, and pull the signed PDF with its audit trail when everyone has finished. Two of its operations are unusual, because they are not automation at all. Approve Biometric Check and Reject Biometric Check exist because Autentique itself decided that some identity decisions belong to a person. FlowRunner agrees, and this page is largely about what an agent does with a vendor that has already drawn the line.

Without FlowRunner

One channel for everyone The contract goes by email, including to the signer whose email has bounced twice before

Identity proof set by habit Every deal gets the same signature type, whether it is a small renewal or a six-figure agreement

Reviews that sit in a queue A signer's photo ID waits for whoever opens the dashboard next, and nobody is watching

With FlowRunner

The channel the signer answers on Email, WhatsApp, SMS, or a link delivered by your own flow, chosen per signer from what you already know

Identity proof matched to value The check is decided from the deal record before the document is created, not after somebody complains

Reviews routed to a named person A waiting identity check reaches the deal owner with the evidence attached and a decision to make

Use Case Scenarios

Send on the signal, not on a schedule

A deal moves to Won in Pipedrive or HubSpot. The agent assembles the signer list from the deal's contacts, checks each address against past delivery failures, and picks WhatsApp for the contact whose email has bounced before. It reads the deal value and sets a liveness check on the authorized signatory and a plain email token on the witness. Create Document uploads the contract and dispatches everything in one call. Nobody opened a browser, and the identity requirements match the size of the agreement rather than the habits of whoever normally sends it.
Rehearsing a new template without touching a customer

The first time a new contract template runs, the agent turns on Test Mode. Autentique creates the document without spending a credit and without contacting anyone. The agent then calls List Documents with the test filter turned on, because test documents are hidden from listings by default and would otherwise look like they had vanished, and reads the result back with Get Document to confirm the field placements, the signer order, and the deadline. Only when a person has looked at the rehearsal does the flow run for real. New templates fail in test, not in front of a customer.
Filing the evidence, not just the PDF

When the last signature lands, the agent calls Download Document to pull the signed copy into file storage and reads Get Document for the full record of who viewed, who signed, who refused, and when. The signed PDF and the timestamp record go together into Google Drive or Box next to the deal, and Move Document To Folder files the Autentique-side copy in the folder for that quarter. A year later, the question is not where the contract is. It is what happened around it, and the answer sits in the same place.

Human-in-Loop Highlight

Most connectors need FlowRunner to invent the pause. Autentique already built one. When a signer's identity check is set to manual approval, their signature does not stand until somebody on your side looks at what they submitted and calls Approve Biometric Check or Reject Biometric Check. There is no automated verdict available, by design, because the vendor decided that matching a face to a document is not a call an API should make on your behalf. So the agent does everything around it and nothing inside it. It watches for signers stuck in that state, pulls the document context with Get Document, and posts to the deal owner: "Marina Costa's identity check on the Q3 supply agreement is waiting for review. She was asked for facial biometrics because the deal is above the 50,000 threshold. Approve or reject?" The owner decides. Approving lets a signature stand under a claimed identity; rejecting blocks a customer who may well be exactly who they say they are. Both directions carry cost, which is precisely why the answer belongs to a person and the gathering belongs to the agent.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

27 actions

Documents

List Documents Lists the documents on the account with their signers and where each of them has got to. Sandbox documents stay hidden unless you ask for them, which is worth remembering after a test run.
Get Document Reads one document, its signers, what each of them has done, and links to the original and signed files. The context call behind every reminder and every escalation.
List Documents In Folder Lists the documents filed in one folder, so a flow can work through a quarter or a client without scanning the account.
Create Document Uploads a PDF and sends it for signature in one call. Everyone listed is contacted immediately, by email, SMS, or WhatsApp, and this cannot be recalled. Test Mode runs the whole shape of it without spending a credit or reaching anyone.
Update Document Changes the settings of a document that has already been created, such as its name, its deadline, or whether it may be refused. Only the fields supplied are changed.
Sign Document Signs a document as the account the connection belongs to. This is how the sending organization applies its own signature without a person opening a link.
Delete Document Permanently removes a document from the account.
Transfer Document Moves a document to another organization or group on the account, which is how a shared workspace hands a deal to the entity that owns it.
Move Document To Folder Files a document in a folder, or takes it out of one. An empty destination moves it back to the root.
Download Document Downloads a document into flow file storage and returns a link to it, taking the signed copy when there is one and the original otherwise.

Signers

Add Signer Adds another person to a document that has already been sent. They are contacted the same way the original signers were, so a late addition is a real send.
Remove Signer Takes a pending signer off a document. Someone who has already signed cannot be removed.
Resend Signature Requests Emails the signing request again to people who have not signed. This reaches real people, so reading the document first is the difference between a nudge and a nuisance.
Create Signing Link Returns a short signing link for one signer, so your own flow can deliver it through whatever channel that person actually uses.
Approve Biometric Check Approves a signer's identity check that was waiting on a person to review it, which lets their signature stand. The operation this page's human gate exists for.
Reject Biometric Check Rejects a signer's identity check that was waiting on a person to review it. The other half of the same decision, and equally a person's to make.

Folders

List Folders Lists the folders on the account, with their subfolders.
Get Folder Reads one folder, including who it is shared with and whether it is password protected.
Create Folder Creates a folder, optionally inside another one, so filing structure can follow the record rather than a convention nobody remembers.
Update Folder Renames a folder.
Delete Folder Removes a folder from the account.
Share Folder Gives people access to a folder, as editors or viewers, and emails them about it. This reaches real people and grants real access, so it belongs in reviewed flows.
Update Folder Sharing Changes how a folder is shared: someone's role, whether it is reachable by link, and whether that link needs a password.

Account

Get Current User Reads the account the connection belongs to, including how many documents and credits are left on the plan. Useful as a connection check, since it needs no identifiers.
Get Organization Reads the organization the connection is currently acting as.
List Organizations Lists every organization the account belongs to. Their identifiers are what Transfer Document and Sign Document take.
List Email Templates Lists the email templates set up on the account, so Create Document can send under the wording legal already approved.

Frequently Asked Questions

What can FlowRunner do with Autentique?

FlowRunner agents can run List Documents, Get Document, and List Documents In Folder in Autentique, plus 24 more actions.

Does connecting Autentique to FlowRunner require OAuth?

No. Autentique connects to FlowRunner with an API key, no OAuth flow required.

Can Autentique trigger a FlowRunner workflow automatically?

Autentique doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Autentique

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us