Find documents, check signers, and add recipients as approved steps
Documenso holds the signature work your team already depends on: vendor agreements, access forms, change sign-offs. Luumen reads it directly, so you can ask which documents are still waiting on a signer, who the recipients are, and what a completed file contains. Changes — new recipients, fields, envelopes — are previewed and sent for approval first. Authentication is by API key.
77 tools: 22 read, 55 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Documenso run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create document beta, create document field, create document fields (bulk), create document recipient, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Documenso — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.