eSignatures
for LuumenAI
Read contracts and templates, then draft and edit signature paperwork as approved steps.
Connect eSignatures and Luumen can look up any contract's status, signers, and current Markdown, list the templates your team maintains, and preview an edit before it lands. When paperwork needs to change, the agent drafts the contract, updates placeholder fields, or adds a signer as a step you approve first.
The eSignatures toolbox
28 tools: 9 read, 19 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ContractGet one contract's current status, details, signers, signer field values, and temporary signed-PDF URL when available.
- ReadGet Contract ContentReturn the Markdown content of one contract.
- ReadGet Contract Placeholder FieldsReturn the current placeholder replacements for one contract.
- ReadGet TemplateGet one template's metadata, placeholder keys, and signer-field IDs.
- ReadGet Template ContentReturn the Markdown content of one template.
- ReadList Template CollaboratorsReturn all collaborators who can edit one template.
- ReadList TemplatesReturn all templates available to the connected account.
- ReadPreview Contract Content UpdatePreview the prospective Markdown from exact find-and-replace edits without mutating the contract.
- ReadPreview Template Content UpdatePreview the prospective Markdown from exact find-and-replace edits without mutating the template.
- WriteAdd Contract SignerAdd a signer to an editable contract without automatically sending a signature request. Approval by default
- WriteAdd Contract SignersAdd a non-empty list of signers to an editable contract by calling the provider's singular endpoint sequentially in request order. Approval by default
- WriteAdd Template CollaboratorCreate a name-only collaborator who can edit a template. Approval by default
- WriteCreate and Send ContractCreate a contract from a template or from ad-hoc Markdown and immediately send signature requests to its signers. Approval by default
- WriteCreate Contract DraftCreate a test or production contract draft from a template or from ad-hoc Markdown, without sending signature requests or otherwise delivering it externally. Approval by default
- WriteCreate TemplateCreate a reusable Markdown contract template. Approval by default
- WriteDelete Contract SignerPermanently remove a signer from an editable contract. Approval by default
- WriteDelete TemplatePermanently delete a template. Approval by default
- WriteDuplicate TemplateDuplicate a template with a new title plus optional placeholder replacements. Approval by default
- WriteInvite Template CollaboratorInvite a collaborator to edit a template. Approval by default
- WriteRemove Template CollaboratorRemove a collaborator's permission to edit a template. Approval by default
- WriteResend Sign RequestResend a signature request to one signer. Approval by default
- WriteSend Draft ContractSend an existing draft to its signers. Approval by default
- WriteUpdate Contract ContentApply exact Markdown find-and-replace edits to a contract. Approval by default
- WriteUpdate Contract Placeholder FieldsUpdate selected placeholder replacements on an unsigned contract. Approval by default
- WriteUpdate Contract SignerUpdate selected contact, delivery, authentication, or redirect details for a signer without resending the contract. Approval by default
- WriteUpdate TemplateUpdate a template's title and/or labels without changing its Markdown content. Approval by default
- WriteUpdate Template ContentApply exact Markdown find-and-replace edits to a template. Approval by default
- WriteWithdraw ContractIrreversibly withdraw an active unsigned contract so it can no longer be signed. Approval by default
One prompt, start to finish
What a governed eSignatures 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.
This connection exposes write actions such as add contract signer, add contract signers, add template collaborator, create and send contract, 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 eSignatures — 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 to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.