PDFgen
for LuumenAI
Read your PDF templates and usage logs, then generate documents on approval
Connect PDFgen with an API key and Luumen can read your saved templates, their full HTML, the connected account's plan and credit usage, and recent generation logs. From there it can generate a PDF from a template, HTML, Markdown, or a prompt, or create and update templates. Changes are previewed and approved before they run.
The PDFgen toolbox
8 tools: 4 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet AccountReturn the connected PDFgen account, organization, plan, and current credit usage.
- ReadGet TemplateGet one saved PDFgen template, including its complete HTML content.
- ReadList TemplatesList saved PDF templates owned by the connected account and return one page with a continuation cursor.
- ReadList Usage LogsList recent PDFgen API calls for auditing, billing inspection, and generation troubleshooting.
- WriteCreate TemplateCreate a reusable HTML template for later PDF generation. Approval by default
- WriteDelete TemplatePermanently delete one saved template owned by the connected account. Approval by default
- WriteGenerate PDFGenerate a PDF from exactly one saved template, HTML document, Markdown document, or AI prompt and return a temporary download URL. Approval by default
- WriteUpdate TemplatePartially update a saved template's name, HTML content, or rendering engine without replacing omitted fields. Approval by default
One prompt, start to finish
What a governed PDFgen 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 template, delete template, generate pdf, update 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 PDFgen — 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 PDFgen to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.