CloudPDF
for LuumenAI
Check CloudPDF documents, usage, and webhooks, then change them with approval
Connect CloudPDF and your team can ask about a document's processing status, default permissions, or how much of the plan's upload and storage allowance is left. Answers come back in the terminal. Changes — a permission update, a new webhook, a deleted subscription — are previewed and approved before they run. Luumen authenticates with an API key.
The CloudPDF toolbox
10 tools: 5 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet AccountReturn the connected CloudPDF organization's plan, allowances, and current upload, view, and storage usage.
- ReadGet DocumentRetrieve one CloudPDF document by ID, including metadata, default permissions, and current file processing status.
- ReadGet Document FileRetrieve one known CloudPDF file version and its processing status.
- ReadGet WebhookRetrieve one CloudPDF webhook subscription by its ID.
- ReadList WebhooksReturn all webhook subscriptions configured for the connected CloudPDF organization.
- WriteCreate WebhookCreate a CloudPDF webhook subscription for selected document, collection, tracker, lead, or file-processing events. Approval by default
- WriteDelete DocumentPermanently delete one known CloudPDF document by UUID. Approval by default
- WriteDelete WebhookDelete one CloudPDF webhook subscription by its decimal ID. Approval by default
- WriteUpdate DocumentUpdate selected metadata or default-permission fields on a known CloudPDF document without requiring unchanged values to be resent. Approval by default
- WriteUpdate WebhookUpdate selected fields of a CloudPDF webhook subscription without requiring unchanged values to be resent. Approval by default
One prompt, start to finish
What a governed CloudPDF 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 webhook, delete document, delete webhook, update 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 CloudPDF — 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 CloudPDF to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.