--- title: "Signable Integration" description: "Signable is a UK electronic signature service. Agents send envelopes built from one or more templates, chase and track signers, add copy recipients, maintain the contact book and users, register webhooks, and manage partner sub accounts." url: https://flowrunner.ai/integrations/signable date_modified: 2026-09-04T14:07:24-07:00 --- # Signable [Documents](https://flowrunner.ai/integrations/category/documents-forms) Signable is a UK electronic signature service. Agents send envelopes built from one or more templates, chase and track signers, add copy recipients, maintain the contact book and users, register webhooks, and manage partner sub accounts. 36 actions · Basic auth · available [Signable website](https://www.signable.co.uk/) · [Platform Documentation](https://www.signable.co.uk/) · Capability data verified 2026-08-13 1. A deal is marked won and the paperwork has to go out today 2. Agent reads the counterparty, the terms, and the broker of record from the source system 3. Get Template reports the party ids each template defines, so every person is addressed on the right document 4. List Contact Envelopes confirms this person has not already been sent the same agreement 5. Send Envelope builds one envelope from the terms template and the annex, with the broker added as a copy recipient 6. The deal owner gets the envelope reference and its current status in their channel 7. When the envelope is still unsigned days later, a person decides whether it gets a reminder, an expiry, or a phone call ## What This Integration Enables Signable is built for UK teams that send the same agreements over and over, and the connector reflects that: the envelope is the unit of work, and it is assembled from templates rather than uploaded ad hoc. That has a consequence worth designing around. When one envelope draws on several templates, each party holds a separate party id per template, so the flow reads the template's own definition with Get Template before it addresses anybody. FlowRunner agents send envelopes, track every party's individual signing status, remind the ones who have stalled, and answer "what has this person been sent" from a single contact lookup. The other half of this connector is account governance, which is unusual for an e-signature integration and is where the risk sits. Agents manage the address book, the seats, the company wide signing settings, and, on a partner account, whole sub accounts belonging to other companies. FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline is what makes that surface safe to automate: the agent gathers the evidence at machine speed, and the calls that remove a company or change every future envelope on the account wait for a named person. Signable does not publish the shape of the event its webhooks deliver, so this connector ships webhook management as ordinary actions rather than as a FlowRunner trigger. A flow starts from your own systems or from a schedule and reads status with Get Envelope, which is honest about what the platform can actually promise. ### Without FlowRunner **Envelopes assembled by hand**: Someone opens the Signable interface, picks templates, and retypes party details that already exist in the CRM **Wrong party on the wrong document**: With several templates in one envelope, the same person holds a different party id on each, and a mismatch is easy to make and hard to see **Chasing is somebody's memory**: Outstanding signatures are tracked in a spreadsheet, and reminders go out when someone remembers to look ### With FlowRunner **Envelopes assembled from the record**: Agents read the deal, resolve the template's party ids, and send the envelope the moment the trigger condition is met **Addressing is resolved, not assumed**: The flow asks the template what parties it defines before it builds the envelope, so the mapping is read rather than guessed **Chasing is a running process**: Agents poll envelope status, send reminders on a schedule, and escalate the ones that need a person ## Use Case Scenarios ### One envelope, several documents, everyone addressed correctly A deal closes in [Pipedrive](https://flowrunner.ai/integrations/pipedrive) and the paperwork is not one document. It is the master terms, a jurisdiction annex, and a data processing schedule, and not every party signs all three. The agent calls Get Template on each, reads the party ids that template defines, and builds the Send Envelope call so each signer is bound to the documents that concern them, with the introducing broker added as a copy recipient who receives the pack without being asked to sign it. Get Envelope then reports each party's own signing status, so a status board in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) shows which of three signers is holding the deal up rather than a single unhelpful "sent". ### A chase that knows what it is asking for On a schedule, the agent calls List Envelopes narrowed to the sent status and finds the ones that have been open too long. First pass, it calls Remind Envelope. Second pass, it posts to [Slack](https://flowrunner.ai/integrations/slack) with the counterparty, the days outstanding, and the deal value. Only then does anything terminal happen, and the three terminal options are genuinely different: Cancel Envelope and Expire Envelope both stop the signing and leave the envelope on the account with its history, while Delete Envelope removes it and its documents outright. The agent presents that choice rather than making it, because "we are withdrawing this offer" and "erase the record that we made it" are not the same decision. ### A partner account that reports on itself A firm reselling Signable to its own clients runs a monthly agent. List Sub Accounts walks the companies under the partner account, Get Sub Account Usage reads envelope volume per company, and the results land in a billing sheet alongside the contract each client is on. Clients trending over their allowance get a note to their account manager. Clients at zero for a full quarter get flagged for a conversation, not for cleanup, because nothing about a quiet quarter authorizes an agent to remove a company. ## Human-in-Loop Highlight Delete Sub Account does not remove a record. It removes a whole company from the partner account, along with everything on it, and it cannot be undone. So the account hygiene agent never calls it. When a sub account has shown zero envelope usage for a full quarter, the agent assembles the case and stops: "Sub account Harrow Legal Ltd has sent no envelopes since March. It holds 214 completed envelopes and 3 active users. Its partner contract renews in six weeks. Delete the sub account, downgrade it, or leave it in place?" The partner operations lead answers. The agent did the counting, the correlation with the contract, and the write up. What it did not do was decide that a company's entire signed archive was disposable. 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 36 actions ### Envelopes 7 - **Send Envelope** Creates an envelope from one or more templates and sends it to its parties. Each document names the template behind it, and each party is either a signer or a copy recipient. When several templates are in play, give each party its party id per template. - **List Envelopes** Returns a page of envelopes newest first, narrowed by status or by a search against the title. The polling step behind every chase workflow. - **Get Envelope** Returns one envelope with its status, its documents, and every party's own signing status. Used to answer whether a deal is waiting on one person or on three. - **Remind Envelope** Emails a reminder to the parties who have not signed yet. The first escalation rung, before anything terminal. - **Cancel Envelope** Stops an envelope that is still out for signature. The envelope stays on the account with its history intact. - **Expire Envelope** Expires an envelope immediately rather than waiting for its expiry date. Its parties can no longer sign it. - **Delete Envelope** Permanently deletes an envelope and the documents inside it. Canceling stops the signing; this removes the record, so read anything still needed first. ### Templates 3 - **List Templates** Returns the templates available to the account, each with the fingerprint Send Envelope needs. - **Get Template** Returns one template with its configuration and the parties it defines. The party ids it reports are what Send Envelope matches against, which is why this call comes before addressing anybody. - **Delete Template** Permanently deletes a template. Envelopes already sent from it are unaffected, but nothing can be sent from it afterward. ### Contacts 6 - **Create Contact** Adds a contact to the account address book so the same person can be reused across envelopes without retyping. - **List Contacts** Returns a page of the address book, used for reconciliation sweeps against the CRM. - **Get Contact** Returns one contact from the address book. - **List Contact Envelopes** Returns the envelopes one contact appears on. The fastest way to answer what a given person has been sent and what they have signed. - **Update Contact** Updates a contact's name or email address, which is how a CRM change propagates into the address book. - **Delete Contact** Removes a contact from the address book. Envelopes already sent to them are unaffected. ### Users 5 - **Create User** Adds a user to the Signable account. A user is a billable seat, unlike a contact, which is only an address book entry. - **List Users** Returns the users on the account with their roles. The input to an access review. - **Get User** Returns one user with its role. - **Update User** Updates a user's name, email address, or role. - **Delete User** Removes a user and frees the seat. Envelopes they sent remain on the account. ### Account 4 - **Get Company Settings** Returns the company wide signing and email settings, such as which signature formats are accepted and whether the signed PDF is attached to the completion email. - **Update Company Settings** Updates those settings. They apply to every envelope the account sends from then on, so a change here is not scoped to the flow that made it. - **Get Branding Options** Returns the branding applied to signing pages and emails, including the logo and colors. - **List Branding Emails** Returns the branded email templates on the account, one per email Signable sends. ### Webhooks 5 - **Create Webhook** Registers a URL that Signable calls when the chosen events happen. Several webhooks can coexist, each with its own identifier, so registering one does not disturb another. - **List Webhooks** Returns the registered webhooks with their URLs and subscribed events. Read this before changing anything, because somebody else's integration may depend on one. - **Get Webhook** Returns one registered webhook by its identifier. - **Update Webhook** Changes the URL or the subscribed events of a registered webhook. - **Delete Webhook** Removes a registered webhook so Signable stops calling it. Deleting someone else's webhook silently stops their integration. ### Partner Accounts 6 - **Create Sub Account** Creates a sub account under a partner account with its own first user. This provisions a real, billable company. - **List Sub Accounts** Returns the sub accounts under the partner account. The starting point for usage reporting. - **Get Sub Account** Returns one sub account under the partner account. - **Update Sub Account** Updates the name or contact address of a sub account. - **Delete Sub Account** Deletes a sub account, which removes a whole company and everything on it. This cannot be undone, and it is the operation this page's human gate exists for. - **Get Sub Account Usage** Returns envelope usage per sub account, which is what the partner is billed on. ## Frequently Asked Questions ### What can FlowRunner do with Signable? FlowRunner agents can run Send Envelope, List Envelopes, and Get Envelope in Signable, plus 33 more actions. ### Does connecting Signable to FlowRunner require OAuth? No. Signable connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Signable trigger a FlowRunner workflow automatically? Signable doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Signable?** This integration exposes Signable 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/signable. Site index: https://flowrunner.ai/llms.txt