Documenso
Send Documenso envelopes for signature, manage their recipients and fields, and read the audit trail.
About
Documenso ships in the w6w first-party pack. It declares 20 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.documenso- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Legal & Compliance · Documents & Files · Productivity
Overview
Documenso sends documents out for electronic signature, and this app manages the whole lifecycle of an envelope — the unit that holds the documents, recipients, and signature fields together. A template can be turned into a real envelope with its placeholders filled in, sent to recipients, cancelled if something is wrong, or duplicated into a fresh draft; once distributed, its recipients and fields are fixed, so nothing changes what a signer already sees.
Beyond sending, it tracks the parts of a signature workflow that are easy to get wrong: reading a specific recipient’s own signing status rather than waiting for everyone to finish, re-sending only to whoever hasn’t signed yet, and pulling the audit trail — who opened, viewed, and signed, and when — which is the evidence a signed document actually depends on. Signed documents and their signing certificates can both be downloaded as short-lived links, and folders can be created to keep documents and templates organized.
Build with Documenso
Three routes to the same 20 actions. The Workflow tab is generated from Documenso'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.
Read an envelope's audit trail
envelope-audit-log Who opened, viewed and signed an envelope — the evidence behind the signature.
Cancel an envelope
envelope-cancel Stop a pending envelope. Recipients cannot sign it; the record stays.
Get the signing certificate
envelope-certificate-download A link to the certificate PDF — the record produced when a signature is disputed.
Delete an envelope
envelope-delete Permanently delete an envelope and its audit trail. Cancelling keeps both.
Send an envelope for signature
envelope-distribute Email the envelope to its recipients. Nothing is sent until this runs.
Get a download link
envelope-download A short-lived URL for the envelope's document. Check it is completed first.
Duplicate an envelope
envelope-duplicate Copy an envelope into a new draft, documents and fields included.
Add recipients
envelope-recipient-add Add signers to a draft envelope. Distributed envelopes are fixed.
Get a recipient
envelope-recipient-get One recipient's signing state — the answer the envelope's status cannot give.
Remove a recipient
envelope-recipient-remove Remove a recipient from a draft envelope, along with their fields.
Update recipients
envelope-recipient-update Correct a recipient's address, name, role or signing order.
Resend a signing request
envelope-redistribute Re-send the signing email to recipients who have not signed.
Create an envelope from a template
envelope-use Fill a template envelope's recipients and create a real one, optionally sending it.
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 Documenso's real ids.
{
"manifestVersion": "2",
"name": "documenso-example",
"steps": [
{
"id": "envelope-audit-log",
"uses": {
"app": "io.w6w.documenso",
"action": "envelope-audit-log",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"envelopeId": "<envelopeId>"
}
}
]
}Here are some of the things you can do
-
Read an envelope's audit trail
readenvelope-audit-log -
Get the signing certificate
readenvelope-certificate-download -
Send an envelope for signature
performenvelope-distribute -
Get a download link
readenvelope-download -
Duplicate an envelope
performenvelope-duplicate
+15 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 Documenso, 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 Documenso. 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: "envelope-audit-log",
payload: {
envelopeId: "<value>",
// returnAll: "<value>",
// limit: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action envelope-audit-log --payload '{"envelopeId":"<value>"}'Give an AI agent Documenso — without giving it Documenso'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.documenso#envelope-audit-log",
"input": {
"envelopeId": "<envelopeId>"
}
}
}
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 Documenso 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
Documenso'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. Documenso itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Documenso declares its own checks, so its health is a property of the app rather than something the host guesses at.
Documenso instance health
This connection's own server, via its unauthenticated /api/health endpoint — including the signing certificate check, which fails silently everywhere else.
API request headroom
The rate-limit headers Documenso sends on every response. Absent on a self-hosted instance that does not rate limit, which is reported rather than guessed at.