SignRequest
Create documents and send them out for signature via SignRequest, track and cancel SignRequests, download signed PDFs, work from templates, and subscribe webhooks to document/signer events.
About
SignRequest ships in the w6w first-party pack. It declares 26 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.signrequest- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Legal & Compliance · Documents & Files · Productivity
Overview
SignRequest is a straightforward e-signature service: upload or reference a document, describe who needs to sign it and how, and it handles sending the request, tracking who has viewed/signed/declined, and returning the signed PDF plus a signing log. This app covers that full lifecycle against SignRequest’s REST API.
A document can be created from a publicly reachable URL, from base64-encoded content, or by copying one of the account’s own templates, and then sent for signature either as two calls (create the document, then send a SignRequest against it) or in one call via SignRequest’s own quick-create endpoint. Once sent, a SignRequest can be cancelled, resent as a reminder, or forwarded from one signer to another, and attachments can be required from or supplied to signers before it goes out. Documents, SignRequests, templates and team members can all be listed and read back, including a free-text search across an account’s documents. Webhook subscriptions let a workflow react to document and signer events (sent, viewed, signed, declined, and more) instead of polling, and the event and audit-event logs are both readable directly.
Every document a SignRequest here sends already exists in the account, or is created fresh from a URL or inline content within this same app — SignRequest offers no way to hand it a file uploaded through a different channel, since the sandbox this app’s Actions run in cannot smuggle raw multipart bytes across the worker boundary. Team creation and membership administration are left to SignRequest’s own interface.
Build with SignRequest
Three routes to the same 26 actions. The Workflow tab is generated from SignRequest'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.
Add Document Attachment
document-attachment-create Attach a file signers can view/download before signing. Only for a not-yet-sent document created via File from URL / File from Content, not one created from a template.
List Document Attachments
document-attachment-list List document attachments, optionally filtered by document.
Create Document
document-create Create a document from a template, a publicly reachable URL, or base64-encoded content. Exactly one of Template ID / File from URL / File from Content should be given.
Delete Document
document-delete Delete a document (immediately for the sender; a grace period applies to signers).
List Events
event-list List document/signer events, optionally filtered by document, type, or status.
Cancel SignRequest
signrequest-cancel Cancel a SignRequest that has not been fully signed or declined yet.
Forward SignRequest to Another Signer
signrequest-forward-signer Forward a SignRequest from one signer's email to a different one.
List SignRequests
signrequest-list List SignRequests, optionally filtered by who sent them or their `who` mode.
Quick Create SignRequest
signrequest-quick-create Create a document and send a SignRequest for it in one call. Exactly one of Template ID / File from URL / File from Content should be given.
Resend SignRequest Email
signrequest-resend-email Resend the SignRequest email as a reminder to signers who haven't signed yet.
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 SignRequest's real ids.
{
"manifestVersion": "2",
"name": "signrequest-example",
"steps": [
{
"id": "document-attachment-create",
"uses": {
"app": "io.w6w.signrequest",
"action": "document-attachment-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"documentId": "<documentId>"
}
}
]
}Here are some of the things you can do
-
Add Document Attachment
performdocument-attachment-create -
List Audit Events
readaudit-event-list -
List Document Attachments
readdocument-attachment-list -
Create Document
performdocument-create -
Get Document
readdocument-get
+21 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 SignRequest, 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 SignRequest. 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: "document-attachment-create",
payload: {
documentId: "<value>",
// name: "<value>",
// fileFromUrl: "<value>",
// fileFromContent: "<value>",
// fileFromContentName: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action document-attachment-create --payload '{"documentId":"<value>"}'Give an AI agent SignRequest — without giving it SignRequest'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.signrequest#document-attachment-create",
"input": {
"documentId": "<documentId>"
}
}
}
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 SignRequest 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
SignRequest'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. SignRequest itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
SignRequest declares its own checks, so its health is a property of the app rather than something the host guesses at.
SignRequest platform status
Atlassian Statuspage for signrequest.statuspage.io, narrowed to the API component (Web app / Workers are read but capped at degraded). Unauthenticated and unsigned.