# How to connect GetTranscribe to Hermes Agent (paste one key, 9 tools)

> Connect GetTranscribe to Hermes 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/hermes/get-transcribe

Most guides for giving Hermes Agent GetTranscribe access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical GetTranscribe setup: pair once in the browser and your always-on Hermes agent can act on GetTranscribe for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to GetTranscribe.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect GetTranscribe** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent 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 <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect GetTranscribe in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your GetTranscribe API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from GetTranscribe, summarize it in plain English, and point out anything that needs attention.

### Using a different agent?

The Hermes 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 Hermes

Looking for a GetTranscribe MCP server for Hermes Agent? ClawLink connects GetTranscribe to Hermes Agent 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 OpenClaw instead? The [OpenClaw GetTranscribe integration](https://claw-link.dev/openclaw/get-transcribe) works the same way.

## What the Hermes Agent GetTranscribe integration can do

9 GetTranscribe tools are ready for Hermes Agent once the account is connected.

### All 9 GetTranscribe tools for Hermes

| 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 Hermes Agent. 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 Hermes Agent 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.

### Hermes paired but still can't use GetTranscribe
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### 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 Hermes Agent GetTranscribe integration?
Yes. ClawLink is the fastest way to connect Hermes to GetTranscribe: link your GetTranscribe account once in the browser and Hermes Agent can call the GetTranscribe API through 9 ready-made tools — no custom code or token handling.

### How do I connect GetTranscribe to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect GetTranscribe in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to GetTranscribe in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want GetTranscribe working from chat.

### Hermes paired but still can't use GetTranscribe
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [Hermes Cloudinary integration](https://claw-link.dev/hermes/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/hermes/penpot) — Open-source design and prototyping platform for collaborative design workflows.
- [Canva](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates