Signi

Signi is a Czech electronic signature platform built around the contract. Agents upload a PDF with who signs, in what capacity and order, place signatures by coordinates or anchor text, hold drafts for a person to release, and read the audit trail.

18 actions API key available

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

A negotiated agreement reaches final terms and is ready for execution

Agent pulls the counterparty, the signing parties, and the final PDF from the matter record

Each person is matched to the act they are actually performing, whether that is signing, approving, stamping, or only being notified

Signature placement is resolved against anchor words in the document rather than page coordinates, so it survives a re-layout

Create Contract uploads the PDF with the state set to Draft, so nothing reaches a counterparty yet

The matter owner receives the party list with every person's capacity and proof method beside the deal value

The matter owner checks the capacities and releases the contract from Signi

What This Integration Enables

Signi is a Czech platform built around the contract, and the thing it models better than most is capacity. Its parties do not divide into signers and everyone else. A person can sign, approve, stamp, sign with a certificate, sign with Bank ID, or be added as notice only, and those are genuinely different acts with different weight. FlowRunner agents build the contract from the matter record with each person placed in the right one, position signatures by anchor text so the layout can change without breaking the document, and pull the signed PDF and the revision list the moment execution completes.

Two structural facts shape how a flow should be built here, and both work in FlowRunner's favor. First, Create Contract sends by default: leave the state alone and Signi's own default emails everyone immediately, and that cannot be recalled. Setting the state to Draft creates the contract without sending it, and release happens from the Signi application. Second, there is no update path. The connector creates contracts and deletes them, but nothing amends one that already exists. Together those make Signi a natural fit for human-in-the-loop rather than an awkward one: the agent assembles the whole instrument, and a person performs the release. Signi's webhooks live inside each contract rather than as an account level subscription, so this connector ships no FlowRunner trigger. Point a contract's webhook at your own endpoint and use Download Contract Preview with the hash it delivers.

Without FlowRunner

Everyone is a signer The distinction between signing, approving, and merely being copied lives in email etiquette rather than in the document

Placement breaks on re-layout Signature boxes pinned to page coordinates land in the wrong place the moment a clause is added

Evidence is a screenshot Proving a signature took place means someone exporting a revision list by hand when it is asked for

With FlowRunner

Capacity is part of the record Each party is created with the act they perform, and the contract itself carries who approved and who executed

Placement follows the words Anchors in the template put each signature where the clause is, not where the page break used to be

Evidence is a link The revision list is readable in flow and shareable to outside counsel without granting anyone account access

Use Case Scenarios

The party list is the point

A supply agreement closes in Pipedrive and four people touch it. The customer's authorized signatory signs. Their finance director approves. Your own company stamps. The introducing partner is notice only. The agent builds all four into one Create Contract call, assigns the signing order so the approval lands before the countersignature, and places each signature on an anchor word in the template rather than at a fixed coordinate. Because the state is set to Draft, the whole arrangement exists and is inspectable before anybody receives an email.
Evidence you can hand to someone else

When a contract completes, the agent calls Get Audit Trail to read the revision list: what happened, when, and by whom. That record is written into the matter file alongside the signed PDF pulled by Download Contract. When outside counsel later asks for proof of execution, the agent calls Create Audit Trail Link and sends a shareable link rather than a PDF export or an account invitation. The evidence leaves the building without the account access leaving with it, and a note goes to the matter channel in Slack.
A contract book that stays honest

A weekly agent reconciles the Signi address book against the CRM. New counterparty contacts are added in bulk with Import Contacts from a generated CSV, changed email addresses go through Update Contact, and people who have left an account are removed with Delete Contact. Because a contract's people list takes an email address rather than an identifier, keeping that book accurate is what stops a contract being addressed to somebody's former colleague. The reconciliation report lands in Google Sheets, and List Contracts filtered by state gives the same sheet a live view of what is still outstanding.

Human-in-Loop Highlight

Signi has no operation that amends a contract. The connector lists, reads, creates, downloads, and deletes, and there is nothing between create and delete. So the capacity you assign a party, the proof method you choose, and the signing order you set are decided once, in the Create Contract call, and the only correction available is Delete Contract and building it again while the counterparty watches. That matters most when the choice is Sign With Bank ID versus an ordinary signature on a high value agreement, because the weaker proof does not fail loudly. It executes, and the weakness surfaces only when someone disputes it. So the execution agent creates every contract as a Draft and posts the arrangement: "Contract 8841, supply agreement, CZK 4.2m. Novak signs with Bank ID. Prochazkova approves. Our side stamps. Horak is notice only. Signing order: approve, then sign, then stamp. Release or amend?" The matter owner reads six lines instead of building a contract, and the release stays where the liability already sits.

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

18 actions

Contracts

List Contracts Lists the contracts a person is a signer on, optionally narrowed to one state. The polling step behind outstanding-execution reporting.
Get Contract Reads one contract, its parties, and where each of them has got to.
Create Contract Uploads a PDF and creates a contract from it. With the state left at Pending this sends to everyone listed straight away and cannot be recalled; set the state to Draft to create it without sending and release it later from the Signi application.
Delete Contract Removes a contract from the account, optionally with everything attached to it.
Delete Contract File Removes a contract's file while leaving the contract record on the account. The route to use when the record has to stay for audit purposes and only the document has to go.
Download Contract Downloads a contract into flow file storage and returns a link to it.
Download Contract Preview Downloads a contract using the hash a webhook delivered rather than its identifier. How a flow reacting to a Signi webhook gets the document without looking anything up first.
List Signers Lists the signing identities on a contract, with what each is required to do and whether they have done it.
Get Audit Trail Reads the revision list for a contract: what happened to it, when, and by whom. This is the evidence a signature took place.
Create Audit Trail Link Returns a shareable link to a contract's revision list, so the audit trail can be sent to someone without giving them account access.

Templates And Tags

List Templates Lists the contract templates on the account, optionally with the parameters each one takes.
List Tags Lists the tags and folders on the account.
Create Tag Creates a tag or a folder. Signi treats both as tags and tells them apart by a single flag, which is why this action asks which one you mean.

Contacts

List Contacts Lists the address book on the account.
Update Contact Changes a contact's name or email address, which is how a CRM correction reaches the book a contract is addressed from.
Delete Contact Removes a contact from the address book.
Import Contacts Adds contacts to the address book in bulk from a CSV file. The action behind a scheduled reconciliation against your CRM.

Account

Get Current User Reads the account the connection belongs to. Useful as a connection check, since it needs no identifiers.

Frequently Asked Questions

What can FlowRunner do with Signi?

FlowRunner agents can run List Contracts, Get Contract, and Create Contract in Signi, plus 15 more actions.

Does connecting Signi to FlowRunner require OAuth?

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

Can Signi trigger a FlowRunner workflow automatically?

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

Start building with Signi

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us