Conversion Tools
for LuumenAI
Convert documents between formats, and track every conversion task
Connect Conversion Tools and Luumen can handle the file format work that sits between systems. It checks which conversions are supported, inspects a file's size and name before touching it, follows a task to completion, and pulls the result down. Conversions run as approved steps, so nothing is submitted without you seeing the plan first.
The Conversion Tools toolbox
11 tools: 6 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDownload Converted FileDownload a converted file from the Conversion Tools API using its file ID.
- ReadGet Auth InfoGet information about the authenticated user including email address.
- ReadGet Conversion ConfigGet available conversion types and their configuration.
- ReadGet File InfoGet metadata about a file including size, name, and preview (for text files).
- ReadGet Task StatusGet the status of a conversion task.
- ReadList Conversion TasksGet all tasks for the authenticated user (up to 50 most recent tasks).
- WriteConvert Excel to HTMLConvert an Excel (.xlsx) file to HTML table format. Approval by default
- WriteConvert Word to TextConvert Word documents (.doc/.docx) to plain text (.txt). Approval by default
- WriteCreate Conversion TaskCreate a new conversion task. Approval by default
- WriteUpdate Task RetentionUpdate the retention mode for a task. Approval by default
- WriteUpload FileUpload a file to the ConversionTools API for subsequent conversion operations. Approval by default
One prompt, start to finish
What a governed Conversion Tools 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 convert excel to html, convert word to text, create conversion task, update task retention, 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 Conversion Tools — 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 Conversion Tools to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.