# How to connect Shotstack to OpenClaw (paste one key, 23 tools) > Connect Shotstack to OpenClaw with ClawLink: paste your Shotstack key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/shotstack The usual route to Shotstack 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 Shotstack setup: install one ClawHub skill, connect Shotstack in the browser, and OpenClaw can call real Shotstack 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 Shotstack. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Shotstack** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect shotstack # connect Shotstack (browser OAuth) npx -y @useclawlink/cli actions shotstack # list available actions npx -y @useclawlink/cli run shotstack --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Shotstack in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Shotstack API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Shotstack, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Shotstack is connected in the dashboard, that agent calls the same 23 Shotstack tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Shotstack MCP for OpenClaw Looking for a Shotstack MCP server for OpenClaw? ClawLink connects Shotstack to OpenClaw and exposes 23 Shotstack tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Shotstack integration](https://claw-link.dev/hermes/shotstack) works the same way. ## What the OpenClaw Shotstack integration can do 23 Shotstack tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 23. ### 20 of 23 Shotstack tools for OpenClaw | Tool | What it does | |---|---| | **Get assets** `shotstack_get_assets` | Fetch details of a hosted asset by its unique identifier | | **Get assets render** `shotstack_get_assets_render` | Retrieve hosted assets by render ID | | **Get render callback** `shotstack_get_render_callback` | Retrieve the webhook/callback URL configuration for a specific render job | | **Get render status** `shotstack_get_render_status` | Retrieve the current status and details of a Shotstack render job by render ID | | **Get source** `shotstack_get_source` | Fetch the details of a specific source asset | | **Get template** `shotstack_get_template` | Retrieve details of a specific template | | **Get template by version** `shotstack_get_template_by_version` | Retrieve a template by template id and API version | | **Inspect media** `shotstack_inspect_media` | Inspect media metadata | | **List sources** `shotstack_list_sources` | List all source assets | | **List sources2** `shotstack_list_sources2` | List all ingested source files with environment selection | | **List templates** `shotstack_list_templates` | List all Shotstack templates for the account | | **List templates2** `shotstack_list_templates2` | List all Shotstack templates for the specified environment | | **Create template** `shotstack_create_template` | Create a new template for video editing | | **Create template2** `shotstack_create_template2` | Save an Edit as a re-usable template | | **Fetch source** `shotstack_fetch_source` | Fetch a remote media file and store it as a source asset | | **Get upload URL** `shotstack_get_upload_url` | Request a signed URL for direct file upload to Shotstack | | **Post upload** `shotstack_post_upload` | Request a signed URL for direct file upload | | **Render video** `shotstack_render_video` | Initiate a new video render job | | **Transfer asset** `shotstack_transfer_asset` | Transfer a file from any publicly available URL to one or more Serve API destinations | | **Update template** `shotstack_update_template` | Update an existing template by its ID | ## Example prompts **Get Assets** > Pull the relevant data from Shotstack, summarize it in plain English, and point out anything that needs attention. **Get Assets Render** > Pull the relevant data from Shotstack, summarize it in plain English, and point out anything that needs attention. **Get Render Callback** > Pull the relevant data from Shotstack, summarize it in plain English, and point out anything that needs attention. **Get Render Status** > Pull the relevant data from Shotstack, summarize it in plain English, and point out anything that needs attention. ## 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 Shotstack working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Shotstack API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Shotstack 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 Shotstack. | 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 Shotstack actions to the runtime in a format your agent can reliably use. | 23 tools for Shotstack are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Shotstack 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 Shotstack in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the Shotstack key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Shotstack skill but can't call the tools The ClawHub skill teaches OpenClaw about Shotstack, but the calls run through the ClawLink plugin and your connected account. Make sure Shotstack 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 Shotstack 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 Shotstack tools Shotstack 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 Shotstack 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. ### Shotstack 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 Shotstack has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Shotstack integration? Yes. ClawLink is the fastest way to connect OpenClaw to Shotstack: link your Shotstack account once in the browser and OpenClaw can call the Shotstack API through 23 ready-made tools — no custom code or token handling. ### How do I add Shotstack to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Shotstack skill from ClawHub, then you click Connect in the dashboard to authorize Shotstack. OpenClaw calls the tools from the next message — no config files, and the Shotstack key you paste is stored server-side instead of in your environment. ### How long does it take to connect Shotstack to OpenClaw? About two minutes. Sign in, click Connect next to Shotstack in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Shotstack 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 Shotstack working from chat. ### OpenClaw installed the Shotstack skill but can't call the tools The ClawHub skill teaches OpenClaw about Shotstack, but the calls run through the ClawLink plugin and your connected account. Make sure Shotstack 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 GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.