Signwell
for LuumenAI
Check signature status and chase unsigned documents without leaving the terminal
Connect SignWell and Luumen can read your documents, bulk sends, and webhook registrations for context. Ask who has signed a contract, what a stalled bulk send contains, or which callback URLs are registered. When a document needs to go out or a signer needs a nudge, the agent shows the plan first and waits for your approval.
The Signwell toolbox
12 tools: 4 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet CredentialsRetrieve account information for the authenticated API key.
- ReadGet DocumentReturn a document and all associated document data.
- ReadList Bulk SendsList all Bulk Sends.
- ReadList WebhooksList all registered webhooks.
- WriteCreate DocumentCreate and optionally send a new document for signing. Approval by default
- WriteCreate Document from TemplateCreate and optionally send a new document for signing from a template. Approval by default
- WriteCreate WebhookRegister a webhook callback URL. Approval by default
- WriteDelete DocumentDelete a document (and cancel signing if in progress). Approval by default
- WriteDelete WebhookDeletes a registered webhook by its ID. Approval by default
- WriteSend ReminderSend a reminder email to recipients that have not signed yet. Approval by default
- WriteUpdate and Send DocumentUpdate a draft document and send it to recipients for signing. Approval by default
- WriteUpdate TemplateUpdate an existing template in SignWell. Approval by default
One prompt, start to finish
What a governed Signwell run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create document, create document from template, create webhook, delete document, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Signwell — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Signwell to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.