How to connect Castingwords to OpenClaw
Connect Castingwords to OpenClaw with ClawLink: paste your Castingwords key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
CastingwordsAPI KEYMCPCastingWords offers high-quality, human-powered transcription services with a RESTful API for seamless integration into various workflows.. Once connected, OpenClaw can read and act on Castingwords from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Castingwords 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 Castingwords setup: install one ClawHub skill, connect Castingwords in the browser, and OpenClaw can call real Castingwords 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 Castingwords.
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 Castingwords
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Castingwords?"
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 Castingwords in the ClawLink dashboard — paste your Castingwords API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Castingwords, 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 Castingwords is connected in the dashboard, that agent calls the same 9 Castingwords tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Castingwords MCP for OpenClaw
Looking for a Castingwords MCP server for OpenClaw? ClawLink connects Castingwords to OpenClaw and exposes 9 Castingwords tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Castingwords integration works the same way.
What the OpenClaw Castingwords integration can do
9 Castingwords tools are ready for OpenClaw once the account is connected.
All 9 Castingwords tools for OpenClaw
| Tool | What it does |
|---|---|
Get prepay balance castingwords_get_prepay_balance | Retrieve the current prepay balance for the account |
Get transcript castingwords_get_transcript | Retrieve the transcript for a given audiofile in the requested format (txt, doc, rtf, or html) |
Get webhook castingwords_get_webhook | Retrieve the currently registered webhook URL for account notifications |
Sku list castingwords_sku_list | Retrieves all available CastingWords transcription service SKUs with pricing |
Order transcript castingwords_order_transcript | Create a transcription order for audio/video files at publicly accessible URLs |
Order upgrades castingwords_order_upgrades | Order an upgrade for a specific audio file |
Register webhook castingwords_register_webhook | Registers a webhook URL to receive CastingWords event notifications |
Test webhook castingwords_test_webhook | Request a test webhook call for a specific event type |
Cancel audiofile castingwords_cancel_audiofile | Cancel an ordered audio file and issue a refund if applicable |
Try it: find the Castingwords tool you need
Browse the 9 Castingwords 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 Castingwords, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Castingwords, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Castingwords, summarize it in plain English, and point out anything that needs attention.
Use Castingwords to sku list and walk me through the result in plain English.
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 Castingwords working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Castingwords API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Castingwords 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 Castingwords. | 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 Castingwords actions to the runtime in a format your agent can reliably use. | 9 tools for Castingwords are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Castingwords 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 Castingwords in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Castingwords 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 Castingwords skill but can't call the tools
The ClawHub skill teaches OpenClaw about Castingwords, but the calls run through the ClawLink plugin and your connected account. Make sure Castingwords 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 Castingwords 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 Castingwords tools
Castingwords 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 Castingwords 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.
Castingwords 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 Castingwords 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 Castingwords integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Castingwords: link your Castingwords account once in the browser and OpenClaw can call the Castingwords API through 9 ready-made tools — no custom code or token handling.
How do I add Castingwords to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Castingwords skill from ClawHub, then you click Connect in the dashboard to authorize Castingwords. OpenClaw calls the tools from the next message — no config files, and the Castingwords key you paste is stored server-side instead of in your environment.
How long does it take to connect Castingwords to OpenClaw?
About two minutes. Sign in, click Connect next to Castingwords in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Castingwords 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 Castingwords working from chat.
OpenClaw installed the Castingwords skill but can't call the tools
The ClawHub skill teaches OpenClaw about Castingwords, but the calls run through the ClawLink plugin and your connected account. Make sure Castingwords 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
GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty tools
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
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.