Check signature request status and send documents out, with writes held for approval
Connect Dropbox Sign and your agent can answer signature questions from the terminal: who has signed, what is still open, which team members hold access to a template. When something needs to change — a bulk send, a new team invite, canceling a stalled request — the agent shows the plan first and waits for your approval before it acts. Luumen authenticates with an API key.
56 tools: 27 read, 29 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Dropbox Sign 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.
Read actions answer immediately. Anything that writes — invite user to team, add user to template, bulk create embedded signature request with template, bulk send with template, and more — is shown as a plan and requires approval by default, including the 5 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 Dropbox Sign — 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.