--- title: "ZapSign Integration" description: "ZapSign is a Brazilian electronic signature platform used across Latin America. Agents send documents for signature from a file, a Word template, or Markdown, set signing order, manage signers and templates, read the activity log, and register webhooks." url: https://flowrunner.ai/integrations/zapsign date_modified: 2026-09-04T14:07:24-07:00 --- # ZapSign [Documents](https://flowrunner.ai/integrations/category/documents-forms) ZapSign is a Brazilian electronic signature platform used across Latin America. Agents send documents for signature from a file, a Word template, or Markdown, set signing order, manage signers and templates, read the activity log, and register webhooks. 29 actions · API key · available [ZapSign website](https://zapsign.com.br/) · [Platform Documentation](https://docs.zapsign.com.br/) · Capability data verified 2026-08-13 1. A deal is marked won and the contract has to reach the customer the same day 2. Agent reads the customer, the tax registration, and the commercial terms from the deal record 3. Create Document From Template fills the template's variables and sends the contract to its signers 4. Add Signer sets the signing order and requires a token over WhatsApp, with the signer's details locked so they cannot be edited at signing time 5. Resend Notifications chases anyone still outstanding after the agreed interval 6. Get Document Activity Log records who opened it, who signed, when, and from which address 7. When a counterparty stalls or pushes back on the terms, a person decides whether to keep chasing, cancel, or formally refuse ## What This Integration Enables ZapSign is a Brazilian electronic signature platform used widely across Latin America, and its regional fit is not a footnote. WhatsApp delivery is first class here, for the signature request and for the signed file, and the identity token that gates the signing can be sent over WhatsApp too. For a sales team selling into Brazil, that is the difference between a contract that gets signed this afternoon and one that sits in an inbox. FlowRunner agents create documents from a PDF, a Word file, or Markdown text, generate them from a Word template with the variables filled from a CRM record, set the signing order so an approver only sees the document once the first party has signed, and attach a second document so both are signed in one ceremony. The other half is the record. Get Document Activity Log returns who opened the document, who signed, when, and from which address, and it can be requested as a PDF, which makes it the compliance artifact rather than a debugging aid. Validate PDF Signature works on files that arrived from somewhere else entirely, so a flow can check the signatures inside a supplier's countersigned copy rather than assuming them. What ZapSign does not offer is a draft state: every create is a send. That places the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) moment before the call rather than after it, and it is why the decisions this page cares about are the ones that reach a counterparty. ZapSign lets you register webhooks through the API but publishes no way to list them, so this connector ships webhook management as actions rather than as a FlowRunner trigger. A flow reads status with Get Document or List Documents, or points a webhook at an endpoint of your own. ### Without FlowRunner **The channel does not match the market**: Signature requests go out by email to signers who conduct most of their business on WhatsApp **Identity taken on trust**: Whoever opens the link signs, and the name and tax number on the document are whatever they typed **Evidence is the signed file**: When a signature is questioned, the only artifact anyone kept is the PDF, not the record of how it came to exist ### With FlowRunner **The request reaches the signer where they are**: Requests and signed files go over WhatsApp as well as email, which is how the Brazilian market actually works **Identity is proven and locked**: A token over email, SMS, or WhatsApp proves who is signing, and the details supplied are locked against edits at signing time **Evidence is filed with the file**: The activity log is pulled alongside the signed document, so who opened it and from where is part of the record ## Use Case Scenarios ### The contract goes out the moment the deal closes An opportunity moves to won in [Pipedrive](https://flowrunner.ai/integrations/pipedrive). The agent reads the customer record, calls Get Template to learn exactly which variables the contract template declares, and fills them from the deal rather than guessing at names. Create Document From Template sends the contract. Add Signer places the customer's authorized signatory first and the internal approver second, so the approver only sees a document that has already been accepted, and each signer must enter a token sent over WhatsApp before signing. The name, email, and tax number pulled from the CRM are locked, so the signing page is not an opportunity to quietly change who is contracting. The document reference lands back on the deal and a note posts to [Slack](https://flowrunner.ai/integrations/slack). ### Filing evidence, not just the file When a document reaches signed, the agent does two things rather than one. It stores the signed PDF, and it calls Get Document Activity Log for the record of how the signature came about, requested as a PDF so it can be filed beside the contract in [Google Drive](https://flowrunner.ai/integrations/google-drive-api). The same flow handles inbound paperwork in the other direction: when a supplier returns a countersigned copy through email, Validate PDF Signature checks the digital signatures inside that file and reports whether they hold, which is a different question from whether the file opened. ### Chasing, then knowing when to stop On a schedule, List Documents finds anything still pending past the agreed window. Resend Notifications goes to the signers who have not signed. A signer who has locked themselves out by failing the token check too many times gets Reset Signer Attempts, which lets them try again without anybody rebuilding the document. Signers whose contact details turn out to be wrong get corrected with Update Signer while they still have not signed. Then the flow reaches the case it cannot resolve: a counterparty who has read the contract, gone quiet, and started renegotiating terms in email. That one goes to a person, because the next move is a position, not a reminder. ## Human-in-Loop Highlight Refuse Document As User is the one action here that speaks for the company. It refuses a document on the account holder's behalf and records why, and that reason is written into the activity log, which is the record a dispute is read from later and which ZapSign will hand out as a PDF. Canceling a document is administrative and can be explained as housekeeping. Formally refusing it, with a stated reason, is your organization taking a position that a counterparty can quote back. So the renewal agent never reaches it. It assembles the case instead: "Document 77-4412, Distribuidora Verde, BRL 320,000 annual. Signed by their commercial director on 12 August. Their legal team has since asked for two changes to clause 9 by email. Options: leave it open and negotiate, Cancel Document, or Refuse Document As User with a stated reason." The account owner picks. The agent had already pulled the activity log, matched the email thread to the document, and drafted three candidate reasons. What it declined to do was put a refusal in the permanent record on its own authority. 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 29 actions ### Documents 11 - **Create Document** Creates a document from a PDF, a Word file, or Markdown text and sends it to its signers. Exactly one source is given. Signers can be asked in a fixed order, reminded every so many days, and allowed or not allowed to refuse, and the signing experience can carry your own logo, color, and sender name. - **Create Document From Template** Creates a document from a ZapSign template, filling the template variables with your values, and sends it to the signer. Variable names must match what the template defines, which Get Template reports. - **Get Document** Returns one document with its status, its signers and each signer's own status, plus the links to the original and signed files. - **List Documents** Returns a page of the documents on the account, newest first, narrowed to a folder, a status, a date range, or your own external id. The polling step behind every chase workflow. - **Update Document** Renames a document or moves it to another folder. Only what is sent is changed. - **Delete Document** Permanently deletes a document. Its signing links stop working immediately. - **Get Document Activity Log** Returns the activity history of a document: who opened it, who signed, when, and from where. This is the compliance record, and it can be requested as a PDF. - **Cancel Document** Cancels a document so it can no longer be signed, optionally telling the signers. - **Add Extra Document** Attaches a further document to an existing one, so the same signers sign both in a single ceremony. - **Add Extra Document From Template** Attaches a further document generated from a template to an existing document, so the same signers sign both together. - **Validate PDF Signature** Checks the digital signatures inside a PDF and reports what they are and whether they hold. Used on a file that arrived from elsewhere, rather than on a ZapSign document whose status already says so. ### Signers 7 - **Add Signer** Adds a signer to an existing document. The signer can be asked to prove who they are by a token sent over email, SMS, or WhatsApp, and the details you supply can be locked so they cannot be changed at signing time. - **Get Signer** Returns one signer with their status, their signing link, and how they were asked to prove who they are. - **Update Signer** Updates a signer who has not signed yet: their name, how to reach them, how they prove who they are, and whether those details are locked. - **Delete Signer** Removes a signer from a document. The remaining signers are unaffected. - **Reset Signer Attempts** Clears the failed authentication attempts of a signer who has locked themselves out of the signing flow, letting them try again without the document being rebuilt. - **Resend Notifications** Resends the signature request to every signer of a document who has not signed yet. - **Refuse Document As User** Refuses a document on the account holder's behalf, recording why, rather than waiting for a signer to refuse it. The reason lands in the activity log, which is why this is the operation this page's human gate exists for. ### Templates 5 - **Create Template** Creates a template from a Word file, whose variables later become the fields that Create Document From Template fills. - **List Templates** Returns a page of the templates on the account, each with the token Create Document From Template needs. - **Get Template** Returns one template with the variables it defines, which are the field names Create Document From Template expects. The call that comes before a merge rather than after a failed one. - **Update Template** Renames a template, changes its language, moves it to another folder, or changes where signers are sent after signing. - **Delete Template** Deletes a template. Documents already created from it are unaffected. ### Account 4 - **Get Plan Information** Returns the plan the account is on and what it has used against it. The cheapest authenticated call in the API, so it doubles as a connection check. - **List Account Users** Returns a page of the users on the account with their roles. - **Create Account User** Adds a user to the account. A user is a billable seat, unlike a signer, who needs no account at all. - **Delete Account User** Removes a user and frees the seat. Documents they created remain on the account. ### Webhooks 2 - **Create Webhook** Registers a URL that ZapSign calls when the chosen event happens. One event type per webhook, and a webhook can be narrowed to documents created from a single template. - **Delete Webhook** Removes a registered webhook by its identifier so ZapSign stops calling it. Deleting someone else's webhook silently stops their integration. ## Frequently Asked Questions ### What can FlowRunner do with ZapSign? FlowRunner agents can run Create Document, Create Document From Template, and Get Document in ZapSign, plus 26 more actions. ### Does connecting ZapSign to FlowRunner require OAuth? No. ZapSign connects to FlowRunner with an API key, no OAuth flow required. ### Can ZapSign trigger a FlowRunner workflow automatically? ZapSign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at ZapSign?** This integration exposes ZapSign 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/zapsign. Site index: https://flowrunner.ai/llms.txt