Check signature requests and send new ones without opening DocuSeal
Connect DocuSeal and your team can ask where a signature request stands, who has signed, and which template was used — answered from the terminal. When something needs to move, the agent can clone a template, send a submission from a template or a PDF, or archive one that is finished. Writes are previewed and held for approval by default.
22 tools: 7 read, 15 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed DocuSeal 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 archive submission, archive template, clone template (v2), create submission, 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 DocuSeal — 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.