FlowRunner
PricingContact
Theme
Start Free

ForSign

Documents

ForSign is a Brazilian electronic signature platform. Agents upload a PDF, create a signing operation with members and signing order, request identity documents or a selfie before signature, collect form answers, and download the signed files.

16 actions API key available
ForSign website Vendor Site Capability data verified 2026-08-13
A supplier clears review and their agreement has to be signed with identity documents on file
Upload Document registers the PDF, which spends no credits and notifies nobody
Create Operation configures every member with their signing order, their authentication, and the documents each one has to upload first
List Member Attachments reports what each signer has provided and whether it has been accepted yet
Download Attachment brings an uploaded document into flow file storage so its contents can be read
Agent posts what it read next to the supplier record the operation belongs to
A reviewer decides, and Approve Attachments lets that signature stand or Reject Attachments asks for a replacement with a reason

What This Integration Enables

ForSign is a Brazilian electronic signature platform, and it is built around a shape most signing APIs do not have: a review step that sits between a signer and their signature. When you create an operation you can require each member to upload documents first, an identity card, a proof of address, a selfie taken on the front camera, and their signature does not stand until somebody accepts what they sent. That is a human-in-the-loop step the vendor designed into the product rather than an approval you bolt on afterwards.

The flow itself is two calls. Upload Document registers the PDF and spends nothing. Create Operation then does everything at once: it names the document, configures every member with their authentication method and their form and attachment requirements, sets the signing order and the deadline, spends plan credits and fires the notifications. It runs as a single transaction, so a validation failure costs nothing, which makes it safe for an agent to attempt and expensive for an agent to get right. FlowRunner agents assemble the operation, chase it, read the form answers back as data, download the signed files and the evidence, and hold the operation open under manual completion when the close needs a person. ForSign publishes signed webhooks but they are configured in its own panel rather than through the API, so these flows run on a schedule or from an upstream event rather than from a listener here.

Without FlowRunner

Document review happens in an inbox Identity documents arrive by email and get checked whenever somebody gets to them
Signature and evidence collected separately The contract is signed in one place and the supporting documents are chased in another
Rejections are vague A signer is told their document was not accepted without being told what to send instead

With FlowRunner

Review is a step in the signing flow The signature waits on the document review, because the platform puts it there
Signature and evidence in one operation The signed contract, the uploaded documents and the evidence file download together
Rejections carry a reason The signer is notified with what was wrong and the operation waits for them again

Use Case Scenarios

  • Supplier onboarding where the paperwork proves itself

    A supplier is approved in NetSuite. The agent calls Upload Document with the master services agreement, then Create Operation naming the supplier's signatory and your own, setting the signing order so your side signs second, and requiring the supplier to upload a company registration document and a photo identity card before signing. Members are reached by email, SMS or WhatsApp, and each of them can be required to enter a second factor code before the document even opens. When the operation completes, Download All Files pulls the signed contract, the uploaded documents and the evidence as one ZIP, and the agent files it into Google Drive against the supplier record.

  • A short form answered before the signature, read back as data

    Some agreements need facts from the signer that nobody has yet: a bank account, a tax registration, a delivery address. Rather than emailing a spreadsheet, the operation attaches a form to each member's signature. Once it completes, the agent calls Get Form Answers and receives what the members typed as structured data rather than as a PDF someone has to read, and writes those values straight onto the supplier record. The contract and the data it depends on stop being two separate chases.

  • Holding the close until a person releases it

    For agreements where the last signature is not the last word, the agent calls Set Manual Completion. The operation then waits rather than sealing itself the moment everyone signs, which gives a contracts owner a window to confirm that the countersigned version matches what was negotiated. When they confirm, Complete Operation seals the documents and generates the evidence. When the terms changed during signing, Cancel Operation stops it instead, and nobody who has not signed can sign afterwards. Set Automatic Completion puts the operation back to closing on its own for the routine cases where none of this is needed.

Human-in-Loop Highlight

Approve Attachments is the operation this page turns on, and it is unusual because ForSign built the pause rather than leaving it to be added. When a member uploads the identity card or the proof of address the operation asked for, their signature does not count until those documents are accepted. Approving them lets the signature stand and the operation carry on. Rejecting them notifies the member, tells them what to send instead, and makes the operation wait for that person again.

An agent can do most of this. Download Attachment brings the uploaded file into flow storage, so the agent can read the name on the identity card, compare it against the supplier record, check that the address matches the one on the contract, and flag the obvious mismatches before a person spends a second on them. What the agent should not do is accept the document. Deciding that a blurry photo of a card is good enough, that a proof of address three months old is acceptable for this counterparty, or that this really is the person authorized to bind the company, is a judgment about risk and about a real human being. So the agent posts: "Member Ana Ribeiro uploaded 2 documents for operation 8841. Photo ID name matches the signatory on file. Proof of address is dated 14 months ago and lists a different city than the contract. Approve both, or reject the proof of address with a reason?" A reviewer answers. Then Approve Attachments or Reject Attachments runs. The agent read the documents. The person accepted them.

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

16 actions

Documents

3
  • Upload Document Uploads a PDF and returns the identifier Create Operation takes. Nothing is sent and no credits are spent, which makes this the safe first half of the flow.
  • Download Document Downloads one document from an operation into flow file storage, decoding the Base64 ForSign returns.
  • Download All Files Downloads everything attached to an operation as a single ZIP: the signed documents, the attachments the signers uploaded, and the evidence. The archival call at the end of a flow.

Operations

6
  • Create Operation Creates a signature operation from an already uploaded document and sends it. One call registers the document, configures every signer with their authentication, form and attachment requirements, sets the order and the deadline, spends plan credits and fires the notifications. It runs as one transaction, so a validation failure costs nothing.
  • Cancel Operation Stops an operation, so nobody who has not signed can sign afterwards.
  • Complete Operation Finishes an operation that is waiting to be completed by hand, which seals the documents and generates the evidence.
  • Set Manual Completion Switches an operation to finishing by hand, so it waits for Complete Operation instead of closing as soon as everyone has signed. This is how a flow keeps a person in the close.
  • Set Automatic Completion Switches an operation back to closing on its own once everyone has signed, optionally with a deadline.
  • Get Form Answers Returns what the members typed into the forms attached to their signatures, as data rather than as a PDF. The operation that turns a signed agreement into records.

Members

3
  • List Members Lists everyone on an operation and where each of them has reached. The read behind every chase and status report.
  • Add Members Adds people to an operation that is already running. They are contacted the same way the original members were.
  • Remove Member Takes someone off an operation. Anyone who has already signed cannot be removed.

Attachments

4
  • List Member Attachments Lists the documents one member uploaded, with whether each has been approved yet. The queue a review flow works from.
  • Download Attachment Downloads a document a member uploaded into flow file storage, so it can be read and checked before anybody decides on it.
  • Approve Attachments Accepts the documents a member uploaded, which lets their signature stand and the operation carry on. This is the operation the human gate on this page exists for.
  • Reject Attachments Refuses the documents a member uploaded and asks them for new ones. They are notified with the reason and the operation waits for them again.

Frequently Asked Questions

What can FlowRunner do with ForSign?

FlowRunner agents can run Upload Document, Download Document, and Download All Files in ForSign, plus 13 more actions.

Does connecting ForSign to FlowRunner require OAuth?

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

Can ForSign trigger a FlowRunner workflow automatically?

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

Start building with ForSign

Free plan, no card required. Connect in minutes.