API2PDF
for LuumenAI
Generate, merge, and trim PDFs from your operations runbooks
Api2Pdf turns HTML, URLs, and office documents into PDFs using wkhtmltopdf, Headless Chrome, and LibreOffice. Connect it and Luumen can assemble incident reports, change records, and audit packets on request. Luumen checks service health and generates barcodes on the spot. Document changes are previewed and held for approval before they run.
The API2PDF toolbox
10 tools: 2 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCheck API StatusCheck the health status of the API2PDF service.
- ReadGenerate Barcode or QR CodeGenerate barcodes or QR codes using Zebra Crossing (ZXING).
- WriteAdd Header FooterConvert HTML to PDF with customizable headers and footers using Headless Chrome. Approval by default
- WriteDelete PDFDelete a previously generated PDF from API2PDF storage by its response ID. Approval by default
- WriteExtract PDF PagesExtract specific pages from a PDF document. Approval by default
- WriteLibreOffice PDF to HTMLConvert a PDF document to HTML using LibreOffice. Approval by default
- WriteLibreOffice ThumbnailGenerate a thumbnail image of a document using LibreOffice. Approval by default
- WriteMerge PDFsMerge multiple PDF documents into a single PDF file. Approval by default
- WriteOptimize PDFOptimize a PDF document to reduce file size while maintaining quality. Approval by default
- WriteReorder PDF PagesReorder pages of a PDF document by specifying a new page sequence. Approval by default
One prompt, start to finish
What a governed API2PDF 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 header footer, delete pdf, extract pdf pages, libreoffice pdf to html, 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 API2PDF — 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 API2PDF to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.