Generate PDFs from your templates, with each document held for approval
Connect PDFMonkey with an API key and Luumen can read your workspaces, templates, and document history on request. Ask what a template expects, check why a render failed, or pull the file for a document you generated last week. When it is time to produce a document, Luumen shows the template and payload first and asks before generating.
18 tools: 11 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed PDFMonkey run looks like inside Luumen.
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 create document, create document sync, create template, delete document, 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 PDFMonkey — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.