--- title: "Signaturit Integration" description: "Signaturit is a Spanish electronic signature and certified delivery provider. Agents send a document for signature in a single call by email, SMS, or signing URL, require ID scans or SMS validation, download the evidence, manage templates and branding, and react to signature events." url: https://flowrunner.ai/integrations/signaturit date_modified: 2026-09-04T14:07:24-07:00 --- # Signaturit [Documents](https://flowrunner.ai/integrations/category/documents-forms) Signaturit is a Spanish electronic signature and certified delivery provider. Agents send a document for signature in a single call by email, SMS, or signing URL, require ID scans or SMS validation, download the evidence, manage templates and branding, and react to signature events. 1 trigger · 27 actions · API key · available [Signaturit website](https://www.signaturit.com/) · [Platform Documentation](https://www.signaturit.com/) · Capability data verified 2026-08-13 1. An application clears underwriting and is ready for signature 2. Agent assembles the document set and each signer's contact details from the case file 3. Get Credits confirms the account can cover the signature and SMS spend for this run 4. The flow reads the case value and the jurisdiction to work out which identity checks the pack needs 5. The case owner receives the proposed pack, the delivery route per signer, and the evidence level attached to each 6. The case owner approves the evidence level, and Create Signature Request sends the pack only once that answer comes back ## What This Integration Enables Signaturit is a Spanish provider whose real product is the evidence, not the signature. A recipient can be required to enter a code sent by SMS, photograph an identity document, take a photo, or record audio before the signature counts, and the audit trail is a separately generated artifact you download and keep. Upload Certified File goes further and records an independently verifiable fingerprint of a file at a moment in time, which is a different job from signing altogether. That is why this connector suits regulated onboarding rather than routine countersigning. It comes with a design constraint worth knowing before you build: there is no draft stage. Everything the recipient sees, including the subject, the body, the branding, the expiry, and the reminder schedule, is decided in the single Create Signature Request call, and the request is live the moment it is accepted. FlowRunner agents assemble that call from the case record, choose the delivery route per signer, and pull the signed PDF and the audit trail into flow storage the instant a document completes. Because the call is one shot, [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) sits in front of it rather than behind it, which is exactly where the platform is designed to put a person: the agent proposes and evidences, and the irreversible send waits. ### Without FlowRunner **Proof decided by habit**: Every document goes out with the same weak evidence because varying it means someone remembering to vary it **Evidence assembled after the fact**: When a signature is questioned, somebody reconstructs the audit trail from the interface, weeks after the event **One delivery channel for everyone**: The request goes by email whether or not that is the channel the signer actually answers ### With FlowRunner **Proof matched to the case**: The flow reads the value and the jurisdiction and attaches the identity checks that case calls for, with a person confirming the level **Evidence filed the moment it exists**: Signed document and audit trail land in the case folder automatically as each document completes **Delivery chosen per signer**: Email, SMS, or a signing URL embedded in your own portal, decided per recipient rather than per account ## Use Case Scenarios ### The proof matches the case, not the template An application reaches signing in the origination system. The agent pulls the borrower, the guarantor, and the document pack, then reads two things: the amount and the jurisdiction. A routine renewal below the internal threshold goes out with an SMS code. A first time borrower above it goes out requiring a photograph of an identity document. Delivery is set per recipient, so the guarantor who never opens email gets the request by SMS while the borrower signs through a URL embedded in the customer portal. Create Signature Request sends the whole arrangement in one call, and the request references land against the case record in [HubSpot](https://flowrunner.ai/integrations/hubspot). ### The evidence file assembles itself On Signature Event fires when a document completes. The agent calls Get Signature Request to read each document's status and event history, then Download Signed Document and Download Audit Trail to bring both into flow storage. Those files are filed straight into the case folder in [SharePoint](https://flowrunner.ai/integrations/sharepoint) or [Box](https://flowrunner.ai/integrations/box), named against the case reference. Download Sent Document is pulled alongside them when the file as it was presented matters, which is the version a dispute is usually actually about. Nobody assembles the evidence pack later, because the pack was assembled the moment the evidence existed. ### Escalating a stall instead of nagging one The trigger also fires on the softer events: the email delivered, the email bounced, the document opened. When a document has been opened and not signed for several days, the agent does not simply call Send Reminder again. It reads the event history from Get Signature Request, works out whether the signer opened it once and left or never received it at all because the address bounced, and routes the two cases differently. A bounce goes to operations to correct the contact record. A read and abandoned document goes to the relationship owner in [Slack](https://flowrunner.ai/integrations/slack), because that is a conversation, not a reminder. ## Human-in-Loop Highlight The evidence level on a Signaturit request is decided once and cannot be raised afterward. There is no action that adds an identity check to a request already sent, because the request went live in the same call that created it. The only remedy for sending a high value agreement with a bare click signature is Cancel Signature Request and start over, which means telling a real counterparty that the document they already signed does not count. So the origination agent stops before the send: "Case 41182, GBP 480,000, first time borrower, guarantor resident outside the UK. Proposed evidence: SMS validation for both signers. Underwriting policy suggests photo identity document for guarantors abroad. Send as proposed, or raise the guarantor to an identity document scan?" The case owner answers in one line. The agent had already read the case, sized the credits, and drafted the request. What it did not do was quietly choose how much proof the file would carry. 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 27 actions ### Signature Requests 9 - **Create Signature Request** Sends documents for signature in one call. Documents come from file URLs, which the connector fetches and uploads, or from Signaturit templates. Each recipient can be required to enter an SMS code, photograph an identity document, take a photo, or record audio, and delivery can be by email, by SMS, or as a signing URL returned to you instead of being sent at all. - **List Signature Requests** Returns signature requests newest first, narrowed by status or by a date range. The polling step behind status boards and chase workflows. - **Count Signature Requests** Returns how many requests match the filters without returning them. Used to size a job before walking the pages. - **Get Signature Request** Returns one request with each of its documents, every signer, and the full event history recorded against them. The call that tells a chase workflow what kind of stall it is looking at. - **Cancel Signature Request** Cancels a request that is still open so its signers can no longer sign it. The request stays on the account with its evidence and a canceled status. - **Send Reminder** Sends the request again to the signers who have not signed yet. - **Delete Signature Request** Permanently deletes a request and its documents. Canceling preserves the evidence; this removes it. - **Rename Signature Request** Changes the name a request is filed under without touching the documents inside it. Used to align Signaturit's filing with your own case references. - **Generate Audit Trail** Asks Signaturit to build the audit trail for a request. The trail is produced asynchronously, and the completion event fires when it is ready to download. ### Downloads 3 - **Download Signed Document** Downloads the signed version of one document into FlowRunner file storage and returns the stored file URL. - **Download Audit Trail** Downloads a document's audit trail into flow storage. The trail must have been generated first, which happens automatically once a document completes. - **Download Sent Document** Downloads the document exactly as it was presented to the signer, before any signature was applied. Often the version a dispute actually turns on. ### Files 2 - **Upload Certified File** Uploads a file to Signaturit and certifies it, recording an independently verifiable fingerprint of the file at that moment. A different job from signing, and useful wherever you need to prove a document existed in a given state on a given date. - **Get Certified File** Returns the record of a certified file: its name, its size, and the fingerprint recorded when it was uploaded. ### Templates 1 - **List Templates** Returns the templates on the account, each with the identifier Create Signature Request accepts in place of a file. ### Branding 4 - **List Brandings** Returns the brandings on the account. A branding controls how signing pages and emails look, and one can be applied per request. - **Get Branding** Returns one branding with its colors, its logo, and its text overrides. - **Create Branding** Creates a branding so the signing experience carries your own colors and wording rather than the vendor's. - **Update Branding** Changes the colors, logo, or wording of an existing branding. Every signature request using it is affected from then on, which makes this a wider change than it looks. ### Account 3 - **Get Credits** Returns the credits left on the account, which signature requests, certified emails, and SMS are all spent against. The pre-flight check before a bulk run. - **List Team Users** Returns the users on the team with their role and status. - **List Team Seats** Returns the seats on the team, including those invited but not yet accepted. ### Subscriptions 5 - **Create Subscription** Registers a URL that Signaturit calls when the chosen events happen. Several subscriptions can coexist, each with its own identifier. The trigger manages its own subscription, so this action is for feeding an endpoint outside FlowRunner. - **List Subscriptions** Returns the subscriptions registered on the account with their URLs and events. - **Get Subscription** Returns one registered subscription by its identifier. - **Update Subscription** Changes the URL or the events of a registered subscription. - **Delete Subscription** Removes a registered subscription so Signaturit stops calling it. Deleting someone else's subscription silently stops their integration, so read the list first. ## Triggers 1 triggers ### Event Triggers 1 - **On Signature Event** Fires when Signaturit reports something happening to a signature process: the email being delivered or bouncing, the document being opened, signed, completed, declined, expired, or canceled, or a signer attaching a photo, a recording, a file, or an identity document. FlowRunner registers a subscription against its own callback URL when the flow is enabled and removes it again when the flow is disabled, so nothing is left behind on the account. This is what turns evidence filing and stall escalation from polling jobs into reactions. ## Frequently Asked Questions ### What can FlowRunner do with Signaturit? FlowRunner agents can run Create Signature Request, List Signature Requests, and Count Signature Requests in Signaturit, plus 24 more actions. ### Does connecting Signaturit to FlowRunner require OAuth? No. Signaturit connects to FlowRunner with an API key, no OAuth flow required. ### Can Signaturit trigger a FlowRunner workflow automatically? Yes. Signaturit supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Signaturit?** This integration exposes Signaturit 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/signaturit. Site index: https://flowrunner.ai/llms.txt