Orshot
for LuumenAI
Render Orshot templates and manage brand assets from the terminal
Connect Orshot and Luumen can read your workspace the way you would: which Studio templates exist, what modifications each one accepts, which brand colors and assets are saved, and which social accounts are still connected. Rendering a template or saving a new brand color is a separate, approved step you see before it runs.
The Orshot toolbox
8 tools: 5 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ProfileReturn the authenticated Orshot profile and the IDs, names, and slugs of its accessible workspaces.
- ReadGet Studio TemplateReturn one Studio template's metadata, pages, and available render modifications by template ID.
- ReadList Brand AssetsList one category of workspace brand assets, optionally requiring all supplied tags.
- ReadList Social AccountsReturn connected social-account IDs and platforms, optionally checking whether each account needs reconnection.
- ReadList Studio TemplatesReturn one filtered page of Studio templates in the API key's workspace, with an opaque cursor for the next page.
- WriteAdd Brand ColorSave a hex, RGB, HSL, or gradient color to the workspace brand assets and return its new ID. Approval by default
- WriteDelete Brand ColorPermanently delete one saved workspace brand color by ID. Approval by default
- WriteRender Studio TemplateRender an owned Studio template as an image or PDF URL/base64 result. Approval by default
One prompt, start to finish
What a governed Orshot 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.
This connection exposes write actions such as add brand color, delete brand color, render studio template. 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 Orshot — 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
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Orshot to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.