# How to connect GetTranscribe to OpenClaw (paste one key, 9 tools) > Connect GetTranscribe to OpenClaw with ClawLink: paste your GetTranscribe key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/get-transcribe The usual route to GetTranscribe 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 GetTranscribe setup: install one ClawHub skill, connect GetTranscribe in the browser, and OpenClaw can call real GetTranscribe 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 GetTranscribe. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect GetTranscribe** — 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 get-transcribe # connect GetTranscribe (browser OAuth) npx -y @useclawlink/cli actions get-transcribe # list available actions npx -y @useclawlink/cli run get-transcribe --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 GetTranscribe in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your GetTranscribe API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from GetTranscribe, 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 GetTranscribe is connected in the dashboard, that agent calls the same 9 GetTranscribe 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). ## GetTranscribe MCP for OpenClaw Looking for a GetTranscribe MCP server for OpenClaw? ClawLink connects GetTranscribe to OpenClaw and exposes 9 GetTranscribe 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 GetTranscribe integration](https://claw-link.dev/hermes/get-transcribe) works the same way. ## What the OpenClaw GetTranscribe integration can do 9 GetTranscribe tools are ready for OpenClaw once the account is connected. ### All 9 GetTranscribe tools for OpenClaw | Tool | What it does | |---|---| | **Get current account** `get_transcribe_get_current_account` | Return the connected GetTranscribe account's safe identity, plan, usage limits, and available | | **Get folder** `get_transcribe_get_folder` | Retrieve one transcription folder owned by the connected account | | **Get transcription** `get_transcribe_get_transcription` | Retrieve one completed transcription with its text and media metadata; optionally include | | **Get transcription job** `get_transcribe_get_transcription_job` | Get the status and progress of one asynchronous transcription job, including the finished | | **List folders** `get_transcribe_list_folders` | List transcription folders owned by the connected account, optionally filtering by parent folder | | **List transcription jobs** `get_transcribe_list_transcription_jobs` | List asynchronous transcription jobs for the connected account, optionally filtered by | | **List transcriptions** `get_transcribe_list_transcriptions` | List lightweight completed-transcription metadata for the connected account, with folder and | | **Create transcription job** `get_transcribe_create_transcription_job` | Queue a paid asynchronous transcription job for a supported public video or direct media URL | | **Resolve media download URL** `get_transcribe_resolve_media_download_url` | Resolve a fresh direct download URL for supported social or direct media without creating a | ## Example prompts **Get Current Account** > Pull the relevant data from GetTranscribe, summarize it in plain English, and point out anything that needs attention. **Get Folder** > Pull the relevant data from GetTranscribe, summarize it in plain English, and point out anything that needs attention. **Get Transcription** > Pull the relevant data from GetTranscribe, summarize it in plain English, and point out anything that needs attention. **Get Transcription Job** > Pull the relevant data from GetTranscribe, 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 GetTranscribe working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the GetTranscribe API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected GetTranscribe 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 GetTranscribe. | 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 GetTranscribe actions to the runtime in a format your agent can reliably use. | 9 tools for GetTranscribe are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes GetTranscribe 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 GetTranscribe in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the GetTranscribe 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 GetTranscribe skill but can't call the tools The ClawHub skill teaches OpenClaw about GetTranscribe, but the calls run through the ClawLink plugin and your connected account. Make sure GetTranscribe 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 GetTranscribe 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 GetTranscribe tools GetTranscribe 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 GetTranscribe 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. ### GetTranscribe 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 GetTranscribe has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw GetTranscribe integration? Yes. ClawLink is the fastest way to connect OpenClaw to GetTranscribe: link your GetTranscribe account once in the browser and OpenClaw can call the GetTranscribe API through 9 ready-made tools — no custom code or token handling. ### How do I add GetTranscribe to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink GetTranscribe skill from ClawHub, then you click Connect in the dashboard to authorize GetTranscribe. OpenClaw calls the tools from the next message — no config files, and the GetTranscribe key you paste is stored server-side instead of in your environment. ### How long does it take to connect GetTranscribe to OpenClaw? About two minutes. Sign in, click Connect next to GetTranscribe in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring GetTranscribe 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 GetTranscribe working from chat. ### OpenClaw installed the GetTranscribe skill but can't call the tools The ClawHub skill teaches OpenClaw about GetTranscribe, but the calls run through the ClawLink plugin and your connected account. Make sure GetTranscribe 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 Cloudinary integration](https://claw-link.dev/openclaw/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN. - [Penpot](https://claw-link.dev/openclaw/penpot) — Open-source design and prototyping platform for collaborative design workflows. - [Connect Canva](https://claw-link.dev/openclaw/canva) — Create designs, upload assets, export content, and manage brand templates