Docupilot
for LuumenAI
Check your Docupilot folder layout, then add new ones as approved steps.
Docupilot generates PDFs, contracts, and invoices from templates. Connect it with an API key and Luumen can read your folder structure and confirm which account it is acting as. When a new folder is needed for a team or document type, Luumen shows the plan first and creates it after you approve.
The Docupilot toolbox
3 tools: 2 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadList all foldersList all folders.
- ReadGet Authenticated UserRetrieve information about the authenticated user.
- WriteCreate Docupilot FolderCreate a new folder. Approval by default
One prompt, start to finish
What a governed Docupilot 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 docupilot folder — is shown as a plan and requires approval by default. 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 Docupilot — 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 Docupilot to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.