Assinafy

Assinafy is an electronic-signature platform for businesses in Brazil. Send documents for signature, verify signers, track progress, and download signed files within your business workflows. It supports signing with A1 and A3 digital certificates, and verification by email or WhatsApp. Connect Assinafy to the tools you already use to manage customer agreements, service contracts, employee documents, and other signing processes.

Em português

A Assinafy é uma plataforma de assinatura eletrônica para empresas no mercado brasileiro. Envie documentos para assinatura, verifique a identidade dos signatários, acompanhe o andamento e baixe os arquivos assinados nos seus processos de trabalho. A plataforma oferece assinatura com certificados digitais A1 e A3 e validação por e-mail ou WhatsApp. Conecte a Assinafy às ferramentas que sua empresa já utiliza para gerenciar contratos com clientes, prestação de serviços, documentos de RH e outros processos de assinatura.

English	Português (Brasil)
Electronic signature	Assinatura eletrônica
Signer	Signatário
Signature request	Solicitação de assinatura
Send for signature	Enviar para assinatura
Signed document	Documento assinado
Signing status	Status da assinatura

Verified 2 triggers 14 actions API key available

Assinafy website Platform Documentation Capability data verified 2026-10-05

A deal moves to closed won and the contract flow starts

Agent reads the counterparty's legal name, tax ID, and contact channel from the deal record

Agent registers each party with Create Signer, including the CPF or CNPJ a certificate signature requires

Agent confirms every certificate signer has a tax ID on file and stands alone in their signing step

Agent calls Estimate Signature Cost to price the send and read the blocking reason if the balances fall short

Agent posts the signer and proof matrix, with its price, to the contract owner

The owner authorizes the send, and only then does the agent call Create Document From Template

What This Integration Enables

Assinafy makes identity a per-signer decision rather than a workspace setting. One agreement can go out with an email code for the internal approver, a WhatsApp code for the counterparty who never opens email, and an ICP-Brasil A1 or A3 certificate for the party whose signature has to carry qualified PAdES weight. Each method asks for something different: a WhatsApp code is available on paid subscriptions, and a certificate signer needs a CPF or CNPJ on file and has to stand alone in their signing step. That is the real content of a signature workflow in Brazil, and it is the part an agent can get right every time once somebody has decided how strongly this particular document needs to hold up.

FlowRunner agents work the whole lifecycle around that decision. They upload a PDF or generate one from a template, and register signers as reusable workspace records rather than one-off recipients. They send with the virtual method when signers simply sign, or the collect method when signers fill fields placed on specific pages. Before any of that becomes a live request, Estimate Signature Cost prices it. When every signer has signed, the document reaches the certificated status, and Download Document retrieves whichever artifact the archive needs: the original upload, the certificated PDF, the certificate page alone, the PAdES file carrying the signers' ICP-Brasil signatures, or a ZIP bundle of all of them. Both triggers poll. Assinafy currently allows one webhook subscription per workspace, so registering one would displace a webhook the workspace already depends on, and the connector polls rather than take that away from you. The connection also targets Production or Sandbox, so a contract flow can be rehearsed end to end before it touches a real counterparty.

Without FlowRunner

Proof method set by habit Every agreement goes out with the same identity check whether the document warrants it or not

Cost discovered after the fact What a send consumes becomes visible once the credits are already gone

Missing tax IDs found late A signer without a CPF on file cannot sign with a certificate, and nobody learns that until the request stalls

With FlowRunner

Proof chosen per signer An email code, a WhatsApp code, or an ICP-Brasil certificate, decided for the document in front of you

Price read before committing Estimate Signature Cost returns the breakdown, the balances, and the reason when they are not enough

Prerequisites checked while the document is still editable The agent confirms what each proof method needs before anything reaches a signer

Use Case Scenarios

Closed won to contract sent, with the proof decided first

A deal reaches closed won in HubSpot. The agent pulls the company record, reads the signatory's legal name and tax ID, and registers them with Create Signer so the certificate path stays open. It lists the matching template with List Templates, maps one signer to each template role, and calls Estimate Signature Cost to see what the send consumes and whether the balances cover it. The contract owner gets the whole picture in one message: which document, which signers, which proof method each one carries, and what it costs. They authorize, and Create Document From Template generates the agreement and sends it in the same call.
Certificated PDFs archived the moment they exist

On Document Signed fires when a document reaches the certificated status, meaning every signer has signed and Assinafy has issued the signed file. The agent calls Download Document for the bundle artifact, which captures the certificated PDF and its certificate page together, and uploads it to the matching client folder in Google Drive. It writes the document ID and the signing completion back onto the deal record. Nobody has to remember to file the executed copy, because the archive step is part of the same flow that sent it.
Stalled and declined requests treated as exceptions

On Document Status Changed reports a document that went declined, expired, or failed. These are automation exceptions in the exact sense: the flow did its job and the answer came back wrong. The agent gathers the context with Get Document and Get Signer, then posts to the account owner in Slack with the three moves available and what each one costs. Resend Signature Request puts the invitation back in front of one signer. A new request with a different proof method starts the clock again at a different price. Delete Document clears the record, but only while the document is in a deletable status, because a certificated document cannot be removed at all. The owner picks; the agent executes and logs which one they chose.

Human-in-Loop Highlight

Create Document From Template generates the document and sends it for signature in a single call. There is no draft sitting in the workspace afterward for somebody to look over, because by the time the call returns, every signer already has their link. That is the right place to stop. So the agent assembles everything the decision needs and then waits: "Service agreement for Construtora Vale, generated from the Contrato de Prestacao template. Signers: R. Macedo, ICP-Brasil certificate, CPF on file, alone in step 1. L. Ferreira, WhatsApp code, step 2. Estimated cost and current balances attached, balances sufficient. Send now?" The owner answers in Slack and the agent proceeds or stands down. What makes the pause worth having is what Delete Document will not do: once a document reaches the certificated status, it cannot be deleted. A contract signed by the right person under the wrong proof, or by the wrong person at all, is a permanent record in the workspace and a weaker instrument than somebody thought they were getting. The agent can prepare that send perfectly. Deciding to make it is a person's call.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

14 actions

Documents

Upload Document Uploads a PDF to the configured workspace and creates a document from it, fetching the file from a URL such as a FlowRunner file URL from an earlier step. Used when the document already exists: a contract produced by a document generator, an invoice, a signed-off scope. The new document starts processing immediately and can be sent for signature right away.
Get Document Retrieves one document by ID with its current status and artifacts. Used to confirm where a document stands before acting on it, and to gather context when a request stalls.
List Documents Lists the workspace's documents one page at a time. Used for reconciliation and reporting: which agreements are still pending signature, which expired this month, which never left metadata_ready.
Delete Document Permanently deletes a document. Only works on documents in a deletable status, including metadata_ready, pending_signature, expired, rejected_by_signer, rejected_by_user, and failed. Certificated documents and documents still processing cannot be deleted, which is why the decision to send is the one worth gating.
Download Document Downloads a document file into FlowRunner file storage and returns a URL to it. Choose the artifact: the original upload, the certificated PDF, the certificate page alone, the PAdES file that preserves the signers' ICP-Brasil signatures, or a ZIP bundle of all of them. Used to archive executed agreements the moment they are signed.

Signers

Create Signer Creates a signer in the workspace so they can be added to signature requests. Needs a full name plus an email address or a WhatsApp number, and a CPF or CNPJ for anyone who will sign with a digital certificate. Used at the front of a contract flow, where the tax ID decides which proof methods remain available later.
Get Signer Retrieves one signer by ID. Used to verify that the identity data a proof method requires is actually on file before a request goes out.
List Signers Lists the signers saved in the workspace, one page at a time. Used to find an existing counterparty rather than creating a duplicate record for someone who has signed before.
Update Signer Updates a signer, changing only the fields provided. A name can always be changed, but an email or WhatsApp number cannot be changed while the signer has already verified that channel on a document still in progress. Changing an unverified channel invalidates links and codes already sent, so pair it with Resend Signature Request.

Signature Requests

Request Signatures Sends a document out for signature by creating an assignment. Use the virtual method when signers simply sign the document, or the collect method when they fill fields placed on specific pages, which requires the document to be in metadata_ready with its field placements set. Signers are notified by email or WhatsApp, the request can be given an expiration, and the response returns each signer's signing URL.
Resend Signature Request Resends the notification to one signer of an assignment through the method chosen when signatures were requested. Used when a signer lost the invitation or when their contact channel was corrected, which is the most common reason a request sits idle.
Estimate Signature Cost Estimates what a signature request on a document would cost without creating it. Returns the cost breakdown, the current document and credit balances, whether they are sufficient, and the blocking reason when they are not. This is the action that lets a person approve a send knowing its price and whether it can even go through.

Templates

List Templates Lists the workspace's document templates one page at a time, including the role IDs a request has to fill. Used to resolve the right template and its roles before generating anything.
Create Document From Template Generates a new document from a template and sends it for signature in the same call. Provide one signer per template role, and optionally fill the template's editor fields, set the document name, an invitation message, an expiration, and tags. Because generation and sending are a single step, this is the action an agent prepares and a person authorizes.

Triggers

2 triggers

Event Triggers

On Document Status Changed Fires when a document in the workspace changes status, and can be narrowed to a single target status. Each event carries the document plus a previous_status field, which is null when an earlier poll had not seen the document yet. Used to catch the outcomes that need a person: declined, expired, and failed documents routed to the account owner while something can still be done about them.
On Document Signed Fires once for each document that reaches the certificated status, meaning every signer has signed and the certificated PDF has been issued. Used to drive the archive step, write completion back to the originating record, and release whatever was waiting on an executed agreement. Both triggers poll. Assinafy currently permits one webhook subscription per workspace, so a connector that registered one would take over a slot the workspace may already be using. Polling trades immediacy for not breaking something that already works.

Frequently asked questions

What can FlowRunner do with Assinafy?

FlowRunner agents can run Upload Document, Get Document, and List Documents in Assinafy, plus 11 more actions.

Does connecting Assinafy to FlowRunner require OAuth?

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

Can Assinafy trigger a FlowRunner workflow automatically?

Yes. Assinafy supports 2 triggers that can start a FlowRunner workflow automatically.

Start building with Assinafy

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us