Docnify
for LuumenAI
Check signing status and chase unsigned documents without leaving the terminal
Connect Docnify and Luumen can read your documents, templates, recipients, and field layouts on request. Ask who still hasn't signed the vendor renewal, or what fields a template expects before you send it. When something needs to change — a resend, a new recipient, a corrected email address — Luumen shows the exact call and waits for your approval before it runs.
The Docnify toolbox
13 tools: 4 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet DocumentFetch a specific document by its ID.
- ReadGet TemplateFetch a specific template by its ID.
- ReadList DocumentsList documents in the Docnify account.
- ReadList TemplatesList templates in the Docnify account.
- WriteAdd Document RecipientAdd a recipient to a document. Approval by default
- WriteCreate Document FieldsCreate one or more fields on a document. Approval by default
- WriteDelete DocumentDelete a specific document by its ID. Approval by default
- WriteDelete Document FieldDelete a field from a document. Approval by default
- WriteDelete document recipientRemove a recipient from a document. Approval by default
- WriteResend DocumentResend a document for signing. Approval by default
- WriteSend DocumentSend a document for signing. Approval by default
- WriteUpdate Document FieldsUpdate metadata of document fields. Approval by default
- WriteUpdate Document RecipientUpdate a recipient's details (name, email, role) on a document. Approval by default
One prompt, start to finish
What a governed Docnify 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 document recipient, create document fields, delete document, delete document field, and more — is shown as a plan and requires approval by default, including the 3 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 Docnify — 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 Docnify to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.