How to connect Orshot to OpenClaw
Connect Orshot to OpenClaw with ClawLink: paste your Orshot key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
OrshotAPI KEYMCPOrshot generates images, PDFs, and videos from templates and manages workspace templates, brand assets, and social publishing.. Once connected, OpenClaw can read and act on Orshot from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Orshot access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Orshot setup: install one ClawHub skill, connect Orshot in the browser, and OpenClaw can call real Orshot actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Orshot.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Orshot
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Orshot?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Orshot in the ClawLink dashboard — paste your Orshot API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Orshot, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Orshot is connected in the dashboard, that agent calls the same 8 Orshot tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Orshot MCP for OpenClaw
Looking for a Orshot MCP server for OpenClaw? ClawLink connects Orshot to OpenClaw and exposes 8 Orshot tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Orshot integration works the same way.
What the OpenClaw Orshot integration can do
8 Orshot tools are ready for OpenClaw once the account is connected. The 7 below are the ones people reach for most; your agent can call all 8.
7 of 8 Orshot tools for OpenClaw
| Tool | What it does |
|---|---|
Get profile orshot_get_profile | Return the authenticated Orshot profile and the IDs, names, and slugs of its accessible |
Get studio template orshot_get_studio_template | Return one Studio template's metadata, pages, and available render modifications by template ID |
List brand assets orshot_list_brand_assets | List one category of workspace brand assets, optionally requiring all supplied tags |
List social accounts orshot_list_social_accounts | Return connected social-account IDs and platforms, optionally checking whether each account |
List studio templates orshot_list_studio_templates | Return one filtered page of Studio templates in the API key's workspace, with an opaque cursor |
Add brand color orshot_add_brand_color | Save a hex, RGB, HSL, or gradient color to the workspace brand assets and return its new ID |
Render studio template orshot_render_studio_template | Render an owned Studio template as an image or PDF URL/base64 result |
Try it: find the Orshot tool you need
Browse the 7 Orshot tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Orshot, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Orshot, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Orshot, group them by priority, and recommend what OpenClaw should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Orshot working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Orshot API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Orshot account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Orshot. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Orshot actions to the runtime in a format your agent can reliably use. | 8 tools for Orshot are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Orshot to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Orshot in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Orshot key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Orshot skill but can't call the tools
The ClawHub skill teaches OpenClaw about Orshot, but the calls run through the ClawLink plugin and your connected account. Make sure Orshot is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Orshot from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Orshot tools
Orshot tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Orshot call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Orshot returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Orshot has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Orshot integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Orshot: link your Orshot account once in the browser and OpenClaw can call the Orshot API through 8 ready-made tools — no custom code or token handling.
How do I add Orshot to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Orshot skill from ClawHub, then you click Connect in the dashboard to authorize Orshot. OpenClaw calls the tools from the next message — no config files, and the Orshot key you paste is stored server-side instead of in your environment.
How long does it take to connect Orshot to OpenClaw?
About two minutes. Sign in, click Connect next to Orshot in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Orshot up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Orshot working from chat.
OpenClaw installed the Orshot skill but can't call the tools
The ClawHub skill teaches OpenClaw about Orshot, but the calls run through the ClawLink plugin and your connected account. Make sure Orshot is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw DataRobot integration
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
Chatbotkit tools
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
Just One API
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.