PDFMonkey
for LuumenAI
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.
The PDFMonkey toolbox
18 tools: 11 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDownload Document FileDownload a generated PDF file via a presigned URL.
- ReadGet Current UserRetrieve details about the currently authenticated user.
- ReadGet DocumentFetch a Document by its ID.
- ReadGet DocumentCardFetch a DocumentCard by ID.
- ReadGet Template by IDFetch a Document Template by ID.
- ReadList DocumentCardsList DocumentCards.
- ReadList PDF EnginesLists all available PDF rendering engines in PDFMonkey.
- ReadList Template CardsList all document template cards for a workspace.
- ReadList WorkspacesList workspaces (applications).
- ReadPreview TemplateFetches the template preview viewer page from PDFMonkey's preview_url.
- ReadView Public Share LinkDownload a publicly shared PDF via its permanent share link.
- WriteCreate DocumentCreate a Document. Approval by default
- WriteCreate Document SyncCreate a document and wait for generation to finish. Approval by default
- WriteCreate TemplateCreates a new PDF document template in PDFMonkey. Approval by default
- WriteDelete DocumentDelete a Document by its ID. Approval by default
- WriteDelete PDFMonkey Document TemplateDelete a document template by ID. Approval by default
- WriteUpdate DocumentUpdates an existing PDFMonkey document's payload, metadata, template, or status. Approval by default
- WriteUpdate Document TemplateUpdate a document template’s properties. Approval by default
One prompt, start to finish
What a governed PDFMonkey 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 document, create document sync, create template, delete document, and more — is shown as a plan and requires approval by default, including the 2 actions 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 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.
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 PDFMonkey to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.