Drop to CDN
for LuumenAI
Publish files and HTML pages to public CDN URLs, and clean them up later
Drop to CDN gives your team a place to put artifacts that need a link. Upload a log bundle, a diff, or a rendered status page, and get back a public URL you can paste into a ticket or a channel. Luumen reads your file list, metadata, and account usage on its own, and holds uploads, page publishes, and deletes for your approval first. Connects with an API key.
The Drop to CDN toolbox
6 tools: 3 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Account UsageReturn the connected account's plan and current upload/storage usage context for deciding whether an upload is appropriate.
- ReadGet FileGet metadata and the public CDN URL for one file or hosted page owned by the connected account.
- ReadList FilesReturn one newest-first page of files and hosted pages owned by the connected account, with a cursor for the next page.
- WritePermanently Delete FilePermanently and irreversibly delete a file or hosted page owned by the connected account. Approval by default
- WritePublish PagePublish HTML as a publicly hosted page and return its CDN URL. Approval by default
- WriteUpload FileUpload a file and return its public CDN URL and expiration metadata. Approval by default
One prompt, start to finish
What a governed Drop to CDN 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 — permanently delete file, publish page, upload file — 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 Drop to CDN — 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 Drop to CDN to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.