# How to connect Happy Scribe to OpenClaw (paste one key, 19 tools) > Connect Happy Scribe to OpenClaw with ClawLink: paste your Happy Scribe key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/happy-scribe The usual route to Happy Scribe 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 Happy Scribe setup: install one ClawHub skill, connect Happy Scribe in the browser, and OpenClaw can call real Happy Scribe 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 Happy Scribe. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Happy Scribe** — 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 happy-scribe # connect Happy Scribe (browser OAuth) npx -y @useclawlink/cli actions happy-scribe # list available actions npx -y @useclawlink/cli run happy-scribe --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 Happy Scribe in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Happy Scribe API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Happy Scribe, 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 Happy Scribe is connected in the dashboard, that agent calls the same 19 Happy Scribe 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). ## Happy Scribe MCP for OpenClaw Looking for a Happy Scribe MCP server for OpenClaw? ClawLink connects Happy Scribe to OpenClaw and exposes 19 Happy Scribe 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 Happy Scribe integration](https://claw-link.dev/hermes/happy-scribe) works the same way. ## What the OpenClaw Happy Scribe integration can do 19 Happy Scribe tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 19. ### 17 of 19 Happy Scribe tools for OpenClaw | Tool | What it does | |---|---| | **Get account details** `happy_scribe_get_account_details` | Retrieve details about your account, including subscription status and usage statistics | | **Get language list** `happy_scribe_get_language_list` | Retrieve the list of supported language codes for Happy Scribe transcription services | | **Get rate limit** `happy_scribe_get_rate_limit` | Get Happy Scribe API rate limit information | | **Get signed upload URL** `happy_scribe_get_signed_upload_url` | Get a signed URL for uploading a file to Happy Scribe's S3 storage | | **Hs export transcription** `happy_scribe_hs_export_transcription` | Creates an export job to download transcription content in various formats | | **Hs get API version** `happy_scribe_hs_get_api_version` | Retrieve current API version and check for updates | | **Hs get error codes** `happy_scribe_hs_get_error_codes` | Returns a list of HTTP error codes used by the Happy Scribe API along with their descriptions | | **Hs get supported formats** `happy_scribe_hs_get_supported_formats` | Retrieve supported file formats | | **Hs get transcription** `happy_scribe_hs_get_transcription` | Retrieve details and status of a specific transcription job | | **Hs get webhooks** `happy_scribe_hs_get_webhooks` | Retrieve webhooks configured for your account | | **Hs retrieve export** `happy_scribe_hs_retrieve_export` | Retrieve information about a specific export | | **List transcriptions** `happy_scribe_list_transcriptions` | Retrieves a paginated list of transcription jobs for a Happy Scribe organization | | **Retrieve order** `happy_scribe_retrieve_order` | Retrieve details of a Happy Scribe order by its ID | | **Create subtitle** `happy_scribe_create_subtitle` | Create subtitles for a video file using Happy Scribe's automatic transcription service | | **Create translation task** `happy_scribe_create_translation_task` | Creates an AI-powered translation task to translate an existing transcription into another | | **Hs confirm order** `happy_scribe_hs_confirm_order` | Confirm a pending order | | **Hs create translation order** `happy_scribe_hs_create_translation_order` | Create a translation order from an existing transcription | ## Example prompts **Get Account Details** > Pull the relevant data from Happy Scribe, summarize it in plain English, and point out anything that needs attention. **Get Language List** > Pull the relevant data from Happy Scribe, summarize it in plain English, and point out anything that needs attention. **Get Rate Limit** > Pull the relevant data from Happy Scribe, summarize it in plain English, and point out anything that needs attention. **Get Signed Upload Url** > Pull the relevant data from Happy Scribe, 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 Happy Scribe working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Happy Scribe API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Happy Scribe 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 Happy Scribe. | 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 Happy Scribe actions to the runtime in a format your agent can reliably use. | 19 tools for Happy Scribe are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Happy Scribe 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 Happy Scribe in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Happy Scribe 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 Happy Scribe skill but can't call the tools The ClawHub skill teaches OpenClaw about Happy Scribe, but the calls run through the ClawLink plugin and your connected account. Make sure Happy Scribe 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 Happy Scribe 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 Happy Scribe tools Happy Scribe 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 Happy Scribe 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. ### Happy Scribe 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 Happy Scribe has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Happy Scribe integration? Yes. ClawLink is the fastest way to connect OpenClaw to Happy Scribe: link your Happy Scribe account once in the browser and OpenClaw can call the Happy Scribe API through 19 ready-made tools — no custom code or token handling. ### How do I add Happy Scribe to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Happy Scribe skill from ClawHub, then you click Connect in the dashboard to authorize Happy Scribe. OpenClaw calls the tools from the next message — no config files, and the Happy Scribe key you paste is stored server-side instead of in your environment. ### How long does it take to connect Happy Scribe to OpenClaw? About two minutes. Sign in, click Connect next to Happy Scribe in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Happy Scribe 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 Happy Scribe working from chat. ### OpenClaw installed the Happy Scribe skill but can't call the tools The ClawHub skill teaches OpenClaw about Happy Scribe, but the calls run through the ClawLink plugin and your connected account. Make sure Happy Scribe 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 - [PagerDuty](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.