Xodo Sign
DocumentsXodo Sign, formerly eversign, is Apryse's electronic signature platform. Agents send documents for signature, reuse templates, drive bulk sends from a CSV, download completed PDFs, and read the audit trail behind every document.
What This Integration Enables
Xodo Sign, formerly eversign and now part of Apryse, is built for teams that issue the same agreement repeatedly rather than negotiating one contract at a time. That shape shows in the API: roles instead of named signers, merge fields instead of hand edits, a bulk job that turns a CSV into up to 250 documents, and an audit log that records every view, signature, decline and revocation with timestamps, IP addresses and file checksums. FlowRunner agents work that surface end to end. They upload a file, create a document or fill a template, chase the one signer who has not finished, reassign a signature when the original signer is unavailable, and pull the completed PDF with its audit trail into file storage.
The reason this matters to an operations owner is that issuance at volume has no undo. Once a bulk job runs, hundreds of real people have a legally binding document in their inbox and the account has been billed for every one of them. FlowRunner's human-in-the-loop design puts the assembly, the validation and the filing on the agent, and puts the decision to actually send in front of a person. Xodo Sign publishes webhooks but has no API for registering them and holds a single account-wide callback URL, so these workflows run from a schedule or an upstream event rather than from a listener on this connector.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
A policy rollout that validates itself before it sends
A recurring run reads the recipient list from Google Sheets or straight out of BambooHR. The agent calls Get Bulk Sending Blank CSV so it builds the file against the template's current roles and merge fields rather than last quarter's. It fills the rows, runs Validate Bulk Sending CSV, and gets back the parsed rows plus anything wrong: a malformed address, a required role left empty, a row count over the limit, an account short on credits. Nothing has been created and nobody has been emailed. The agent posts the summary for approval, and Create Bulk Job runs only after the answer comes back.
-
A contract issued the moment a deal is marked won
A deal reaches closed won in HubSpot. The agent reads the template with Get Document to see which roles and merge field identifiers it defines, then calls Use Template with the buyer's name, email and the commercial terms pulled from the deal record. It writes the document identifier back onto the deal. A daily sweep calls List Documents filtered by status, and Send Reminder goes to the single signer holding it up rather than to everyone on the document.
-
Evidence filed where auditors will look for it
When a document completes, the agent calls Download Final Document with the audit trail appended and stores the result in FlowRunner file storage, then copies it into Google Drive or SharePoint under the account it belongs to. It also pulls Get Audit Log and writes the event history, with each signer, timestamp, IP address and checksum, into the record in the CRM. The evidence and the agreement stay together, and neither of them depends on somebody remembering to file it.
Human-in-Loop Highlight
Create Bulk Job is the operation this page's gate exists for. One call creates up to 250 documents from a template and sends every one of them to a real person. Each document counts against the account's quota, an account that permits overages is billed for the excess, and there is no recall. Validate Bulk Sending CSV catches the shape of the file, not the truth of it: a batch where every address parses and every required column is present can still be the wrong template, last quarter's list, or a merge field that reads correctly and says the wrong number. So the agent stops before the job. It posts: "Ready to issue 214 documents from template Contractor Agreement v4. Header structure fetched today, 214 rows validated, 3 rows rejected for invalid email addresses. Account has 180 documents left this cycle, so 34 will bill as overage. Send, or hold?" A person answers. The agent builds the batch and files the evidence; the choice to put a binding document in 214 inboxes belongs to somebody who can be asked why.
Agent Capabilities
24 actionsBusinesses
1- List Businesses Returns every business on the account with the identifier that document calls are scoped to. Used when an account holds more than one business, since calls that omit the identifier fall back to the primary one.
Documents
6- Create Document Creates a document and sends it to its signers. Files come from a public URL, an identifier returned by Upload File, or base64 content, and fields are supplied as one flat list tagged with the file each sits on. Saving as a draft or enabling sandbox mode stops the document from being sent.
- Get Document Returns the full record of one document or template, including every signer with their individual status, carbon copy recipients, files, fields and stored metadata. The same call reads templates, which is how a flow discovers the roles and merge identifiers before using one.
- List Documents Lists documents on the business filtered by status. Used by sweeps that find what is still outstanding.
- Cancel Document Cancels a document still in process so its outstanding signers can no longer sign it. Required before that document can be deleted.
- Trash Document Moves a document or template to the trash. Completed documents and drafts have to be trashed before they can be deleted.
- Delete Document Permanently deletes a document or template. Xodo Sign enforces an order here, so an in-process document must be canceled first and a completed document or draft must be trashed first, and a flow that skips a step is rejected rather than half completed.
Signers and Evidence
3- Send Reminder Emails one signer a reminder about a document still waiting on them. Reminders are per signer, so a chase workflow nudges the person holding things up instead of the whole distribution.
- Reassign Signer Hands one signer's responsibility to somebody else, with an optional reason recorded. The owner, the original signer and the new signer are all notified.
- Get Audit Log Returns the complete event history of a document: creation, views, signatures, declines, forwards and revocations, each with the acting signer, a timestamp, the client and signer IP addresses, and the checksums that tie the event to the file. This is the compliance record.
Files and Downloads
4- Upload File Uploads a file and returns the identifier that Create Document and Create Template reuse, along with its page count. Unreferenced uploads are removed after 30 days, while a file already used in a document stays with it.
- Download Original Document Downloads the document exactly as uploaded, before any signature was applied, into FlowRunner file storage.
- Download Final Document Downloads the completed, signed version into FlowRunner file storage. The audit trail can be appended to the PDF, and one file of a multiple file document can be selected by sequence number.
- Get Final Document URL Returns a hosted URL for the completed document instead of its bytes, so a flow can link to the file rather than store a copy of it.
Templates
3- Create Template Creates a reusable template whose signers are defined as roles rather than people, with merge fields that get filled each time it is used.
- Use Template Creates and sends a document from a template. Every required role needs a name and an email address, and merge values are matched by field identifier, so a flow reads the template first rather than assuming its shape.
- List Templates Lists templates on the business, optionally restricted to archived templates or drafts.
Bulk Sending
7- Get Bulk Sending Blank CSV Returns the CSV header structure a template expects, built from that template's own roles and merge fields. A template change makes an older file invalid, which is why a flow fetches this rather than caching it.
- Validate Bulk Sending CSV Checks a bulk file against the template before any document is created and returns the parsed rows. Validation covers header structure, required entries, value formats, the per job document limit and whether the account has the credits.
- Create Bulk Job Creates up to 250 documents from one template in a single job and sends them. Every document counts against the account quota and overages are billed, which is why this call sits behind the human gate on this page.
- Get Bulk Job Returns one job with the template it ran from, the number of documents it created and whether all of them were created or some failed.
- Get Bulk Job Status Returns a job's progress, counting completed, canceled and in progress documents against the total.
- List Bulk Job Documents Lists the documents a job created, each as a full document record, so a flow can act on the failures individually.
- List Bulk Jobs Lists the bulk sending jobs on the account, newest first, with the template, document count and status for each.
Frequently Asked Questions
What can FlowRunner do with Xodo Sign?
FlowRunner agents can run List Businesses, Create Document, and Get Document in Xodo Sign, plus 21 more actions.
Does connecting Xodo Sign to FlowRunner require OAuth?
No. Xodo Sign connects to FlowRunner with an API key, no OAuth flow required.
Can Xodo Sign trigger a FlowRunner workflow automatically?
Xodo Sign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Documents integrations
Start building with Xodo Sign
Free plan, no card required. Connect in minutes.