Carbone
for LuumenAI
Turn JSON from your systems into PDFs, spreadsheets, and documents from templates
Carbone renders JSON data into PDF, DOCX, XLSX, ODT, and other formats using templates you already maintain. Connect it and Luumen can list what templates exist, check their tags and categories, confirm the server is healthy, and generate a document when you ask. Authentication is by API key.
The Carbone toolbox
11 tools: 7 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDownload TemplateDownload a template from Carbone by template ID.
- ReadGet Carbone Server StatusRetrieve the current status and health of the Carbone server.
- ReadList Template CategoriesRetrieve a list of all categories used in templates.
- ReadList TemplatesRetrieve a list of templates from Carbone storage with filtering, search, and cursor-based pagination.
- ReadList Template TagsList all tags currently used in templates.
- ReadRender Template DirectGenerate a document by uploading a base64-encoded template and data in a single API call.
- ReadSet Carbone API VersionSet the Carbone API version to be used for subsequent requests.
- WriteDelete Carbone TemplatePermanently delete a template from the Carbone server by its 64-character hexadecimal template ID. Approval by default
- WriteGenerate Carbone ReportGenerate a Carbone report from a template and JSON data. Approval by default
- WriteUpdate Template MetadataUpdate metadata and attributes of an existing Carbone template. Approval by default
- WriteUpload a templateUpload a template file to the Carbone server to obtain a template ID for document generation. Approval by default
One prompt, start to finish
What a governed Carbone 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 — delete carbone template, generate carbone report, update template metadata, upload a template — 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 Carbone — 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 Carbone to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.