SignWell
Send documents and templates out for e-signature with SignWell, track and remind recipients, run bulk sends, and fetch completed PDFs.
About
SignWell ships in the w6w first-party pack. It declares 18 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.signwell- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Documents & Files · Legal & Compliance · Productivity
Overview
SignWell is an e-signature service, and this app covers its REST API for the full send-and-track loop. Create a document from a file URL or base64 content, or from one or more saved templates with the template’s fields pre-filled; keep it as a draft or send it to its recipients, in a fixed signing order or all at once, by email or SMS, with a passcode if needed. Read a document back to see where each recipient stands, remind the ones who have not signed, correct a recipient’s name or email, delete a document, and fetch a download link for the completed PDF (optionally with the audit page, or as a zip). Templates can be created, read, updated and deleted, and a template can be sent to many people at once through a bulk send built from a CSV. The account call returns who the key belongs to and what plan it is on, and webhooks can be listed, registered and removed so a workflow can react to signing events.
SignWell has one API host and one credential, an API key sent as the X-Api-Key header. Deliberately out of scope: the API application endpoints, authentication updates, bulk-send CSV helpers, and the Mexico NOM-151 certificate; and the completed-document download is always returned as a link, never as raw PDF bytes, because the sandbox has no place to put a binary body.
Build with SignWell
Three routes to the same 18 actions. The Workflow tab is generated from SignWell's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Account
account-get Read who the API key belongs to and the account's plan and signing preferences.
Create a Bulk Send
bulk-send-create Send one or more templates to many recipients at once from a base64 CSV.
Get a Bulk Send
bulk-send-get Read one bulk send — status, how many documents completed, and its templates.
Get a Completed Document Link
document-completed-pdf Get a download URL for a completed document's final PDF (or zip).
Create a Document
document-create Create a document from a file URL or base64 content and send it for signature (or keep it as a draft). Sends to recipients unless Create as draft is on.
Create a Document from a Template
document-create-from-template Create a document from one or more saved templates, assign recipients to the template's placeholders, and pre-fill its fields. Sends to recipients unless Create as draft is on.
Get a Document
document-get Read one document — its status, recipients (with each one's state), and files.
Send a Document
document-send Send a draft document to its recipients, optionally updating its settings first.
Update Recipients
document-update-recipients Change a recipient's name or email (and optionally their subject, message or passcode).
Create a Template
template-create Create a reusable template from files, with named placeholders for the signers.
Delete a Template
template-delete Delete a template. Documents already created from it are not affected.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying SignWell's real ids.
{
"manifestVersion": "2",
"name": "signwell-example",
"steps": [
{
"id": "bulk-send-create",
"uses": {
"app": "io.w6w.signwell",
"action": "bulk-send-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"template_ids": "<template_ids>",
"bulk_send_csv": "<bulk_send_csv>"
}
}
]
}Here are some of the things you can do
-
Create a Bulk Send
performbulk-send-create -
Get Account
readaccount-get -
Get a Bulk Send
readbulk-send-get -
List Bulk Sends
searchbulk-send-list -
Get a Completed Document Link
readdocument-completed-pdf
+13 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for SignWell, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to SignWell. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "bulk-send-create",
payload: {
template_ids: "<value>",
bulk_send_csv: "<value>",
// name: "<value>",
// subject: "<value>",
// message: "<value>",
// skip_row_errors: "<value>",
// apply_signing_order: "<value>",
// custom_requester_name: "<value>",
// custom_requester_email: "<value>",
// api_application_id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action bulk-send-create --payload '{"template_ids":"<value>","bulk_send_csv":"<value>"}'Give an AI agent SignWell — without giving it SignWell's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.signwell#bulk-send-create",
"input": {
"template_ids": "<template_ids>",
"bulk_send_csv": "<bulk_send_csv>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's SignWell connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
SignWell's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. SignWell itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
SignWell declares its own checks, so its health is a property of the app rather than something the host guesses at.
SignWell platform status
Top-level indicator from status.signwell.com (Statuspage). INFORMATIONAL: the page's only component is `Docsketch Service`, so nothing on it is specifically the API.
API reachable
Unauthenticated GET https://www.signwell.com/api/v1/me. A 401 carrying SignWell's JSON error envelope (`meta.error`) passes — it proves the API and its auth layer are answering.