Signority

Signority is a Canadian electronic signature platform, now part of FileCloud. Agents build documents as envelopes with roles for signers, viewers, and reviewers, hold them as drafts for release, send from templates, and organize them into folders.

20 actions Basic auth available

Signority website Platform Documentation Capability data verified 2026-08-13

An offer is approved and the letter has to reach the candidate today

Agent pulls the compensation terms, start date, and reporting line from the recruiting record

Create Document From Template builds the offer as a draft, with the hiring manager as a reviewer and the candidate as the signer

The figures on the draft are checked against the approved requisition before anything is released

Get Document confirms every recipient resolved and that an SMS code requirement has a phone number behind it

The recruiter receives the draft reference with each recipient's role beside their name

The recruiter reads the draft and calls Send Document, which is the moment the offer reaches the candidate

What This Integration Enables

Signority is a Canadian electronic signature platform, now part of FileCloud, and the most useful thing about its connector is a decision the extension made on your behalf. In Signority's own API, the difference between creating a draft and emailing every recipient is one integer. Rather than expose that as a flag on a single operation, this connector ships Create Draft Document and Create And Send Document as two separate actions that build an otherwise identical request. Picking the wrong value from a dropdown is easy. Picking the wrong operation is not.

That split is what makes Signority pleasant to automate. FlowRunner agents assemble a document from a template or from files, place recipients into the role each actually holds, and stop. A recipient can be a Signer, a Viewer, a Reviewer, a Signing Host, or an Open Signer, so the internal check happens inside the document rather than in an email thread beside it, and recipients can be made to prove who they are with an emailed or texted code before the document will open. Issue Signing Token goes one step further and opens a document inside your own application without a further sign in. The human-in-the-loop moment is not something the platform has to bolt on here. Signority already drew the line; FlowRunner just puts a person on the right side of it.

Without FlowRunner

One integer between draft and send In the underlying API a draft and a mass email differ by a single number, and a misconfigured flag sends the document

Reviewers see it after the candidate does Internal review happens over email attachments while the document itself goes straight out

Cleanup is indistinguishable from deletion Tidying old documents and destroying them permanently look like the same operation until someone needs one back

With FlowRunner

Two operations, not one flag Building a draft and sending a document are separate calls, so picking the wrong one means picking the wrong operation

Roles are part of the document Signers, viewers, reviewers, and signing hosts are declared on the document, and the review happens inside it

Trash and purge stay separate Retention sweeps move documents to the trash, where they are recoverable, and permanent removal waits for a person

Use Case Scenarios

The offer that a person still sends

An offer is approved in Greenhouse or Workable. The agent calls Create Document From Template, fills the compensation and start date from the requisition, and lists three recipients: the candidate as Signer, the hiring manager as Reviewer, and finance as Viewer. Nothing has been emailed. Get Document Fields reads back the fillable values so the flow can verify the salary figure against the approved requisition rather than trusting its own merge. The recruiter sees the draft reference in Slack, reads it, and releases it with Send Document. Everything up to the send was machine work. The send was not.
Signing inside your own onboarding portal

A new hire opens the onboarding portal and there are four documents waiting. Rather than sending four emails, the agent calls Issue Signing Token for each and embeds the signing page directly in the portal, so the employee signs the contract without leaving the flow they are already in. Documents that only need reading, such as the handbook acknowledgement, get a view only token. As each completes, Get Document reports the change and the record updates in BambooHR. List Documents By Id reads the whole set in one call, which is cheaper than polling each one when a flow is tracking a batch.
A retention sweep that stops before the point of no return

Every quarter an agent runs Search Documents for completed employee documents past the retention period, groups them by folder, and calls Delete Documents. That moves them to the trash, where they can still be recovered from the Signority interface, and the agent posts the manifest to people operations. Purge Documents is the one that actually destroys them, and the agent never reaches it on its own. The list, the count, the oldest and newest dates, and the retention rule each document matched all arrive as a summary, and a person decides whether this quarter's batch gets purged or stays in the trash for another cycle.

Human-in-Loop Highlight

Delete Documents and Purge Documents look adjacent and are not. Delete moves documents to the trash, where a person can still get them back from the Signority interface. Purge removes them permanently, and there is no recovery from it. In an employment records context that difference is the whole ball game, because the documents most likely to age past a retention rule are exactly the ones a former employee, a regulator, or your own counsel may ask about later. So the retention agent does the work and hands over the decision: "412 completed documents in Employment Records match the seven year rule. Oldest 2018-03-04, newest 2019-02-28. 9 of them are attached to open matters flagged in the legal register. Purge the 403 remaining, or hold the batch?" People operations answers. The agent built the list, cross checked it against the legal hold register, and drew the exclusions. It did not press the button that has no undo.

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

20 actions

Documents

Create Draft Document Creates a document as a draft and sends nothing. Recipients are recorded but not contacted, so a flow can add files and check the document first, then release it with Send Document. This is the safe half of the flow and the one to build against.
Create And Send Document Creates a document and emails every recipient straight away. This cannot be recalled. It exists as a separate operation from Create Draft Document on purpose, because in the underlying API the only difference is one integer.
Send Document Releases a draft, which emails every recipient on it. This is the moment the document goes out and it cannot be recalled.
Cancel Document Stops a document that is out for signature. Nobody who has not already signed can sign afterward, though the emails have gone.
Get Document Reads one document in full: its status, its recipients, and where each of them has got to.
Search Documents Searches the documents on the account, narrowed by status and by text. The entry point for retention sweeps and status reporting.
List Documents By Id Reads several documents at once by their identifiers, which is cheaper than one call each when a flow is tracking a batch.
Get Document Fields Lists the fillable fields on a document with their positions and current values. Used to verify a merged figure before release rather than trusting the merge.
Resend Invitation Emails one recipient their invitation again. This reaches a real person, so it is worth reading their status first.
Delete Documents Moves documents to the trash, where they can still be recovered from the Signority interface.
Purge Documents Removes documents permanently, including from the trash. There is no recovery from this, and it is the operation this page's human gate exists for.

Templates

Create Document From Template Makes a new document from a stored template, as a draft. Nothing is sent until you release it with Send Document.
Send From Template Makes a document from a template and sends it immediately. Everyone listed is emailed and it cannot be recalled.

Folders

List Document Folders Lists the folders documents are filed in.
List Template Folders Lists the folders templates are filed in, which are separate from the document folders.
Create Folder Creates a folder to file documents in, which is how a flow keeps a year of onboarding paperwork addressable.
Rename Folder Changes a folder's name. What is inside it is untouched.
Delete Folder Removes a folder from the account.

Account

Get Account Details Reads the account the key belongs to, including the remaining credit. Useful as a connection check, since it needs no identifiers, and as a pre-flight before a bulk run.
Issue Signing Token Issues a single use token that opens a document without a further sign in, so a signing page can be embedded in your own application. Optionally view only.

Frequently Asked Questions

What can FlowRunner do with Signority?

FlowRunner agents can run Create Draft Document, Create And Send Document, and Send Document in Signority, plus 17 more actions.

Does connecting Signority to FlowRunner require OAuth?

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

Can Signority trigger a FlowRunner workflow automatically?

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

Start building with Signority

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us