--- title: "DigiSign Integration" description: "DigiSign is a Czech electronic signature platform with qualified signatures, Bank iD, and SMS authentication. Agents build envelopes from documents and recipients, check they are sendable, send them in one step, and react to envelope events as they happen." url: https://flowrunner.ai/integrations/digisign date_modified: 2026-09-04T14:07:24-07:00 --- # DigiSign [Documents](https://flowrunner.ai/integrations/category/documents-forms) DigiSign is a Czech electronic signature platform with qualified signatures, Bank iD, and SMS authentication. Agents build envelopes from documents and recipients, check they are sendable, send them in one step, and react to envelope events as they happen. 1 trigger · 28 actions · Session · available [DigiSign website](https://digisign.org/) · [Platform Documentation](https://api.digisign.org/) · Capability data verified 2026-08-13 1. On Envelope Event reports an authentication failure for one recipient of a sent envelope 2. Get Envelope returns the document, every recipient, and how far each of them has got 3. List Recipients confirms who has already signed and must not be disturbed 4. Agent looks up a corrected contact for the failed recipient in the system of record 5. The proposed fix posts to the contract owner, naming who would be contacted and what that would cause 6. The owner authorizes the change, and only then does the agent add the corrected recipient to the live envelope ## What This Integration Enables DigiSign is a Czech electronic signature platform, and two things about it shape how an agent should use it. The first is that it takes identity seriously in a way that suits European contract work: Bank iD, qualified signatures, and SMS authentication, set as a default on the envelope and overridable per recipient. The second is rarer and more useful. DigiSign publishes an operation whose entire job is to tell you whether an envelope is ready to send, and to report what is wrong when it is not. Most platforms in this category find out at send time, on the recipient's behalf. FlowRunner agents build an envelope as a draft, attach the PDF, add each recipient with the authentication level the contract's value calls for, order the signing sequence, and run Validate Envelope before anything reaches anybody. Send Envelope is then a single deliberate act rather than the end of a hopeful sequence. Afterward the envelope trigger closes the loop, reporting deliveries, failures, signatures, and completions as they happen, so the flow reacts to what DigiSign observed instead of polling and guessing. That is what [automation exceptions](https://flowrunner.ai/concepts/automation-exceptions) look like when a vendor gives you the instrumentation to see them. ### Without FlowRunner **Sending unattended and hoping**: An envelope goes out and a missing document or an unset requirement surfaces as a signer's confused reply **Silence between send and signature**: Nobody knows a recipient failed authentication until the deadline passes **Slow deals restarted**: A negotiation that runs past the expiry is rebuilt as a new envelope, losing what was already signed ### With FlowRunner **Sending after a real check**: Validate Envelope reports whether the envelope is actually sendable, and the flow reads the answer **Events as they happen**: The envelope trigger reports sends, deliveries, failures, and signatures as DigiSign sees them **Slow deals extended**: Extend Envelope pushes the expiry back so a signer who ran out of time can still sign ## Use Case Scenarios ### Assemble, validate, then let a person send A contract is approved in [Salesforce](https://flowrunner.ai/integrations/salesforce-pro). The agent calls Create Envelope with the defaults for that contract type, uploads the PDF with Add Document, adds each party with Add Recipient, and calls Reorder Recipients so the counterparty signs after the internal approver. Then it runs Validate Envelope and posts the result to [Slack](https://flowrunner.ai/integrations/slack). Somebody presses send. The agent did the assembly, which is tedious and error-prone by hand; the person owns the one step that cannot be undone. Nothing in that division of labor is a compromise, and it is why the connector's own documentation calls the validation step worth taking on any unattended flow. ### Authentication level read from the deal, not from habit Before adding recipients, the agent reads the contract amount off the record. Above the threshold it requires Bank iD on the signature; below it, a simple electronic signature is enough. Because envelope settings act as defaults that each recipient may override, a single flow handles a mixed envelope where the external signatory needs Bank iD and the internal witness does not. Get Account Statistics runs first on large batches so the flow knows the plan will carry the run rather than stopping halfway through a set of contracts. ### Closing the loop on completion On an envelope-completed event, the agent calls Download Envelope to pull every document into file storage, files the executed PDF against the record in [Google Drive](https://flowrunner.ai/integrations/google-drive-api), and keeps the envelope identifier as the link back. A digest posts to the deal channel in [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams). Separately, a scheduled sweep reads List Envelopes for anything near expiry and raises those with their owner, and Extend Envelope is called only where a person says so, because pushing a legal deadline is a decision about the deal rather than about the workflow. ## Human-in-Loop Highlight Add Recipient does two completely different things depending on state, and nothing in its name says which. On a draft envelope it is a build step, as harmless as attaching a file, and no signer learns it happened. On an envelope that has already been sent, the same call contacts that person immediately, and DigiSign offers no way to take it back. So the dangerous version of this operation is the one that looks routine: a recovery flow reacting to a bounced delivery or a missing counterparty is, by definition, running against a live envelope. FlowRunner agents therefore treat Add Recipient as gated whenever Get Envelope reports the envelope is out for signature. The agent does the work that has no consequences: it reads the envelope, confirms with List Recipients who has already signed, finds a corrected contact in the CRM, and posts the proposal to the contract owner. "The supply agreement was sent Tuesday. J. Havel failed Bank iD authentication. I found a second address for him on the account record. Adding him will email him now. The other two recipients have already signed and are unaffected. Proceed?" The owner answers. Clone Envelope exists for the cases where starting clean is better, and that is also a judgment rather than a rule, which is exactly why a person is reading this message. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 28 actions ### Envelopes 11 - **List Envelopes** Lists the envelopes on the account, newest first. The sweep behind expiry monitoring and pipeline reporting. - **Get Envelope** Reads one envelope, its documents, and its recipients with where each of them has got to. The context call before any decision about a live envelope. - **Create Envelope** Creates an envelope as a draft. Nothing is sent: documents and recipients are added, the envelope is checked, and then it is released. The envelope carries the defaults every recipient inherits unless they override them. - **Validate Envelope** Checks whether an envelope is ready to send and reports what is wrong if it is not. Worth calling before every send, and especially on unattended flows. - **Send Envelope** Sends the envelope to everyone on it. This is the moment of no return: the requests go out and cannot be recalled, only canceled. - **Cancel Envelope** Stops an envelope that is out for signature. Nobody who has not signed can sign afterward, so a merely slow deal wants Extend Envelope instead. - **Resend Envelope** Sends the request again to everyone who has not finished. This reaches real people, so reading the envelope first is what keeps a reminder targeted. - **Clone Envelope** Copies an envelope into a new draft, with its documents and settings but nothing signed. The safe way to send the same agreement again. - **Extend Envelope** Pushes an envelope's expiry back, so a signer who has run out of time can still sign. - **Delete Envelope** Removes an envelope from the account. - **Download Envelope** Downloads every document on an envelope into flow file storage, which is the completion step behind filing an executed contract. ### Documents 4 - **List Documents** Lists the documents on an envelope. - **Add Document** Uploads a PDF to an envelope. The file is uploaded first and then attached, which is how DigiSign separates storing bytes from building an envelope. - **Download Document** Downloads one document from an envelope into flow file storage. - **Delete Document** Removes a document from an envelope that has not been sent yet. ### Recipients 6 - **List Recipients** Lists everyone on an envelope and where each of them has got to, including who has already signed and therefore must not be disturbed. - **Add Recipient** Adds a person to an envelope. On a draft this is part of building it; on a sent envelope they are contacted as soon as they are added, which is the case this page's human gate covers. - **Reorder Recipients** Sets the order recipients are asked to sign in, by listing their identifiers in the order wanted. - **Resend To Recipient** Contacts one recipient again about an envelope they have not finished, leaving everyone else alone. - **Get Recipient Signing Link** Returns an embedded signing link for one recipient, so the signing page can open inside your own application rather than depending on the email arriving. - **Delete Recipient** Takes someone off an envelope. ### Webhooks 4 - **List Webhooks** Lists the webhooks registered on the account, including any the trigger created. - **Create Webhook** Registers a URL of your own to be called when chosen events happen. The trigger manages its own registrations, so this is for pointing DigiSign at something outside FlowRunner. - **Delete Webhook** Removes a webhook, so DigiSign stops calling it. - **Test Webhook** Fires a sample delivery at a registered webhook, so an endpoint can be checked without waiting for a real signature. ### Account 3 - **List Templates** Lists the envelope templates on the account. - **Get Account** Reads the account the keys belong to. Useful as a connection check, since it needs no identifiers. - **Get Account Statistics** Reads how much of the plan has been used: envelopes sent, signatures, and the credit left. Worth calling before a large run. ## Triggers 1 triggers ### Event Triggers 1 - **On Envelope Event** Fires when DigiSign reports something happening to an envelope. The event is chosen when the trigger is configured, and the vocabulary is wide: the envelope itself being sent, completed, expired, declined, disapproved, canceled, deleted, or withdrawn; each recipient being sent to, delivered to, failing delivery, failing authentication, signing, downloading, declining, disapproving, canceling, or withdrawing; plus registered deliveries and identity verification. This is what turns a signing process from something a flow polls into something a flow reacts to, and it is the entry point for completion filing, targeted chasing, and the recovery path this page's human gate sits inside. ## Frequently Asked Questions ### What can FlowRunner do with DigiSign? FlowRunner agents can run List Envelopes, Get Envelope, and Create Envelope in DigiSign, plus 25 more actions. ### Does connecting DigiSign to FlowRunner require OAuth? No. DigiSign connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can DigiSign trigger a FlowRunner workflow automatically? Yes. DigiSign supports 1 trigger that can start a FlowRunner workflow automatically. **Work at DigiSign?** This integration exposes DigiSign to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/digisign. Site index: https://flowrunner.ai/llms.txt