eSignatures.io
for LuumenAI
Read contracts and templates, then send signature requests as approved steps
Connect eSignatures.io and the agent can look up a contract, check who has signed, and read the templates behind it without leaving the terminal. When something needs to change — a resend to a stalled signer, a corrected email address, a new contract from a template — the agent shows the plan first and waits for your approval by default. Authentication is by API key.
The eSignatures.io toolbox
17 tools: 5 read, 12 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGenerate Contract PDF PreviewGenerate a PDF preview of a contract and receive a webhook notification with a download URL.
- ReadGet ContractRetrieve details of a specific contract by its ID.
- ReadGet TemplateRetrieve details of a specific template by its ID.
- ReadList Template CollaboratorsRetrieve all collaborators with editing access to a template.
- ReadList TemplatesRetrieve a list of all templates.
- WriteAdd Template CollaboratorGrant editing access to a template with optional email invitation. Approval by default
- WriteCopy TemplateDuplicate an existing template with optional customization. Approval by default
- WriteCreate ContractCreate a new contract using a specified template and signer details. Approval by default
- WriteCreate SignerAdd a signer to an existing contract/signature request. Approval by default
- WriteCreate TemplateCreate a new template. Approval by default
- WriteDelete SignerRemove a signer from a contract. Approval by default
- WriteDelete TemplateDelete a specific template by its ID. Approval by default
- WriteRemove Template CollaboratorRevoke a collaborator's template editing permissions. Approval by default
- WriteSend Contract to SignerSend or resend a contract signature request to a specific signer via their configured communication channel. Approval by default
- WriteUpdate SignerUpdate contact details of an existing signer on a contract. Approval by default
- WriteUpdate TemplateUpdate an existing template's content, title, or labels. Approval by default
- WriteWithdraw ContractWithdraw a contract by its ID. Approval by default
One prompt, start to finish
What a governed eSignatures.io 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 — add template collaborator, copy template, create contract, create signer, and more — is shown as a plan and requires approval by default, including the 4 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 eSignatures.io — 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 eSignatures.io to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.