eSignatures.com

eSignatures.com turns a Markdown template into a contract, fills its placeholders, and collects signatures in a single call. Agents create and send contracts, save drafts for human approval, manage signers and templates, and embed signing in your own product.

25 actions Basic auth available

eSignatures.com website Platform Documentation Capability data verified 2026-08-13

A deal reaches contract stage in the CRM

Get Template reports the placeholder keys and signer field identifiers the template actually defines

Create Contract builds the agreement with the draft option on, so nothing reaches the signers

Update Contract Content applies the negotiated clause changes, run first in dry run so the result comes back without being saved

Get Contract Content returns the wording as it now stands, and the agent compares it with what it intended to produce

The wording differences and the placeholder values post to the contract owner

The owner reads the actual wording and releases Send Draft Contract

What This Integration Enables

eSignatures.com treats the contract itself as data. The wording is Markdown, the placeholders are named keys, and a placeholder can be filled with plain text, with more Markdown, or with another entire template. That last option is what makes the platform interesting to an agent: a clause library stops being a folder of documents people copy from and becomes a set of components a flow assembles according to the deal in front of it. One call creates and sends, or creates and holds, and everything about the finished contract can be read back and rewritten while it remains unsigned.

That programmability is also what this connector has to be careful with, and the platform gives FlowRunner two levers to be careful with. The first is Save As Draft, which turns Create Contract from a send into an assembly step, with Send Draft Contract as a separate deliberate act afterward. The second is dry run on content edits, which returns the result of a rewrite without saving it. Both exist because the vendor understood that a contract is the kind of object where the difference between what you meant and what you wrote is worth catching before a counterparty reads it. FlowRunner agents use both by default, and that is the shape human-in-the-loop takes on this page.

Without FlowRunner

Contracts assembled by hand Somebody copies a template, swaps the clauses the deal needs, and hopes nothing was missed

Optional clauses pasted in Alternative terms live in a document somewhere and are re-pasted each time, drifting as they go

One reminder for everybody Chasing a single unresponsive signer means resending to all of them

With FlowRunner

Contracts assembled from the record Placeholders are filled from the deal, keyed by the identifiers the template reports

Optional clauses assembled from a library A placeholder can be filled with another whole template, so the clause library stays the single source

Reminders aimed at one person Resend Sign Request reaches the signer who has stalled and leaves the rest alone

Use Case Scenarios

The contract built from a clause library

A deal reaches contract stage in Salesforce or HubSpot. The agent reads the deal's terms and decides which optional clauses apply: a data processing addendum for a customer in a regulated sector, a multi-year discount schedule where the term exceeds twelve months. Each of those clauses is its own template, and Create Contract fills the corresponding placeholder with the whole template rather than a pasted block of text. When legal updates the data processing wording, they update one template and every future contract picks it up, instead of somebody remembering which folder holds the current version.
Signing inside your own product

For a self-serve tier, the emailed signing request is the wrong experience. The agent creates the contract with the signer's delivery set so that nobody is contacted, reads the signing page URL out of the response, and hands it to the application, which shows the signing page in the flow the customer is already in. Setting the delivery deliberately matters here: leaving it on the default lets the API decide, which usually means an email goes out. This is one of the cases where an unset field is a decision rather than the absence of one.
Chasing precisely, and filing on completion

Get Contract reports which signers have viewed a contract and which have signed it. Where one signer has looked and not acted past the agreed window, the agent calls Resend Sign Request for that person alone and notes it in Slack, rather than reminding a counterparty who signed on the first day. When the last signature lands, Download Signed Contract pulls the executed PDF into file storage and files it against the account record in Google Drive, with the contract identifier kept as the link back to the signing record.

Human-in-Loop Highlight

Update Contract Content rewrites a contract by finding Markdown and putting something else in its place, and the blanks in that operation carry meaning of their own. An empty search replaces the entire document. An empty replacement deletes what was found. A heading on its own line replaces the whole section beneath it. Now consider the ordinary failure: a search string that matches nothing. The call succeeds. The contract is unchanged, which means the clause the agent was told to swap is still the old clause, and everything downstream reports a clean run. The opposite failure is quieter still, because a search string that matches in two places changes both, and a contract with a duplicated amendment is still a perfectly valid document that opens, paginates, and reads as finished. Nothing in the response distinguishes any of these from success.

So the gate on this connector is the wording itself. The agent creates with the draft option on, runs every content edit in dry run first, then calls Get Contract Content and compares the returned Markdown against what it intended to produce, and posts the differences: "Contract for Vellmark Industries is assembled and held as a draft. Two edits applied: liability cap changed from 100,000 to 250,000, one occurrence. Governing law clause replacement matched zero occurrences and was not applied. Placeholder values attached. Send to the signers?" The second line is the one worth a lawyer's eyes, and it would never have surfaced from a status code. Only after that answer does the agent call Send Draft Contract. Note what the alternative would cost: nothing in this API deletes a contract. Withdraw Contract stops one being signed, but the record remains and can still be read, so a mistaken contract is withdrawn, never removed.

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

25 actions

Contracts

Create Contract Creates a contract from a template and, unless it is saved as a draft, sends it to the signers. Turning on the draft option is what makes this an assembly step rather than a send.
Get Contract Reads a contract with its signers, their answers, and, once signed, a link to the finished PDF. The status call behind targeted chasing and completion handling.
Download Signed Contract Reads a signed contract and stores the finished PDF in flow file storage, ready to file against the record that started it.
Withdraw Contract Withdraws a contract so it can no longer be signed. A signed contract cannot be withdrawn, and nothing here deletes the record, so a withdrawn contract stays readable.
Send Draft Contract Sends a contract that was saved as a draft. This is the moment it reaches the signers, and the call this page's human gate sits directly in front of.
Generate Contract PDF Preview Asks for a PDF preview of a contract. The link arrives on a webhook rather than in the response, so a flow that wants a rendered preview has to be built to receive it.
Get Contract Content Reads the wording of a contract as Markdown. The verification read after any edit, and the input to a difference the agent can show a person.
Update Contract Content Rewrites parts of a contract by finding Markdown and putting something else in its place. The blanks mean something, a search that matches nothing still succeeds, and dry run returns the result without saving it.
Get Contract Placeholder Fields Reads the placeholder values currently set on a contract, so a review shows the figures as the contract actually carries them.
Update Contract Placeholder Fields Changes placeholder values on an unsigned contract. Only the placeholders named are touched.

Signers

Add Signer Adds a signer to an existing contract. Adding one does not send them anything by itself, which makes it safe to use during assembly.
Update Signer Corrects a signer's details on a contract. Changing them does not resend the contract.
Resend Sign Request Sends the signature request to one signer again, leaving the others alone. The targeted chase.
Delete Signer Removes a signer from a contract.

Templates

List Templates Lists the templates on the account with their identifiers.
Get Template Reads a template, including the placeholder keys and signer field identifiers it defines. The discovery call that turns a mapping into something checkable.
Create Template Creates a template from Markdown wording, which is how a clause becomes a reusable component rather than a paragraph somebody copies.
Update Template Renames a template or changes its labels.
Duplicate Template Copies a template, optionally filling in its placeholders as it goes, which is how a variant is created without editing the original.
Delete Template Deletes a template.
Get Template Content Reads the wording of a template as Markdown.
Update Template Content Rewrites parts of a template by finding Markdown and putting something else in its place. The same care applies here as on a contract, with more reach, because a template edit affects every contract made from it afterward.

Collaborators

Add Template Collaborator Gives someone an editor link for a template. Supplying an email address invites them by email, so this reaches a real person.
List Template Collaborators Lists who can edit a template, with each one's editor link. Worth reviewing periodically, because template edit rights are contract drafting rights.
Remove Template Collaborator Takes away a collaborator's permission to edit a template.

Frequently Asked Questions

What can FlowRunner do with eSignatures.com?

FlowRunner agents can run Create Contract, Get Contract, and Download Signed Contract in eSignatures.com, plus 22 more actions.

Does connecting eSignatures.com to FlowRunner require OAuth?

No. eSignatures.com connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can eSignatures.com trigger a FlowRunner workflow automatically?

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

Start building with eSignatures.com

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us