Oksign
for LuumenAI
Send contracts and forms out for signature from the terminal
Connect Oksign and Luumen can see which documents are active, which signed copies still exist, and who is on your contact and user lists. When a contract or purchase order needs to go out, the agent uploads the document, attaches the form fields, and sends the signing notifications as an approved step. Authentication is by API key.
The Oksign toolbox
17 tools: 7 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadRetrieve Briefcase InformationRetrieve a previously uploaded briefcase tokeninfo for consultation.
- ReadRetrieve ContactsRetrieve the list of contacts stored in the account.
- ReadRetrieve Account CreditsRetrieve account credit balance and storage information.
- ReadCheck Document ExistsCheck if a signed or unsigned document still exists on the OKSign platform.
- ReadGet Active DocumentsRetrieve all active document IDs and properties from OKsign account.
- ReadRetrieve Linked Document ListRetrieve the list of linked signed or source document IDs related to a specific document.
- ReadRetrieve UsersRetrieve the list of users associated with the OkSign account.
- WriteRemove BriefcaseRemove a previously created briefcase from OKSign platform. Approval by default
- WriteRemove ContactsRemove specified contacts from the account's contact list. Approval by default
- WriteUpload ContactsInsert or update contact information in the account's contact list. Approval by default
- WriteRemove DocumentRemove a signed or unsigned document from the OKSign platform. Approval by default
- WriteUpload DocumentUpload a PDF or Word document to OKSign platform for completion and/or signing. Approval by default
- WriteCreate Editor Express SessionInvoke the OKSign Editor Express for modifying documents and form descriptors. Approval by default
- WriteUpload Form DescriptorUpload form descriptor defining signature fields and other field types to a document. Approval by default
- WriteUpload NotificationsUpload notifications defining email(s) and/or SMS(es) to be sent to signer(s) with signing links. Approval by default
- WriteUpdate Organization Token InfoUpdate organizational token information and settings for the account. Approval by default
- WriteRemove SignExpress TokenRemove a previously uploaded SignExpress tokeninfo JSONObject from the OKSign platform. Approval by default
One prompt, start to finish
What a governed Oksign 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 — remove briefcase, remove contacts, upload contacts, remove document, 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 Oksign — 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 Oksign to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.