Eversign
for LuumenAI
Check signature status and send documents for signing, without leaving the terminal
Connect Eversign and your agent can see which documents are out for signature, who has signed, and what the audit trail says. It lists templates, businesses, and bulk jobs on request. When something needs to move, it can create a document from a template, reassign a signer, or retire an old file — each change previewed and approved first.
The Eversign toolbox
10 tools: 6 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Document Audit LogRetrieves the complete audit trail for a document, showing all events from creation through completion.
- ReadGet Bulk Jobs ListRetrieve a list of bulk jobs for a business.
- ReadGet Bulk Job StatusRetrieve the status of a bulk job.
- ReadList BusinessesRetrieves all businesses associated with your Eversign account, or filters to a specific business if business_id is provided.
- ReadList DocumentsRetrieves a paginated list of documents from your Eversign business account.
- ReadList TemplatesList templates for a business with optional pagination.
- WriteCreate DocumentCreates a new Eversign document for electronic signature collection from one or more signers. Approval by default
- WriteCreate TemplateCreate a new template. Approval by default
- WriteDelete Document or TemplateDelete, cancel, or trash a document or template by its hash. Approval by default
- WriteReassign SignerReassign a signer to a new person. Approval by default
One prompt, start to finish
What a governed Eversign 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 template, delete document or template, reassign signer — is shown as a plan and requires approval by default, including the 1 action 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 Eversign — 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 Eversign to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.