Docsautomator
for LuumenAI
Read your document automations, then change them as approved steps
Connect DocsAutomator with an API key and Luumen can see how your document generation is set up. List the automations in your workspace, read one automation's data source and template, check queue statistics, and review signing sessions. When something needs to change — a new automation, an updated setting, a copy of a working one — Luumen shows the plan first and waits for your approval.
The Docsautomator toolbox
9 tools: 4 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Automation DetailsRetrieve details of a specific automation by its ID.
- ReadGet Queue StatisticsRetrieve current document generation queue statistics for your workspace.
- ReadList AutomationsRetrieve all automations in your workspace with their basic details.
- ReadList Signing SessionsRetrieve signing sessions with optional filtering by status or signer email.
- WriteCreate AutomationCreate a new DocsAutomator automation with specified data source and optional Google Doc template. Approval by default
- WriteDelete AutomationPermanently delete an automation and all associated data. Approval by default
- WriteDuplicate AutomationCreate a copy of an existing automation with ' COPY' appended to the title. Approval by default
- WriteSend Test EmailSend a test email with a sample PDF attachment to verify email configuration. Approval by default
- WriteUpdate AutomationUpdate an existing automation's settings in DocsAutomator. Approval by default
One prompt, start to finish
What a governed Docsautomator 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 automation, delete automation, duplicate automation, send test email, and more — is shown as a plan and requires approval by default, including the 1 action 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 Docsautomator — 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 Docsautomator to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.