# How to connect Tave to Hermes Agent (paste one key, 129 tools) > Connect Tave to Hermes with ClawLink: paste your Tave key once and 129 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/tave Most guides for giving Hermes Agent Tave 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 Tave setup: pair once in the browser and your always-on Hermes agent can act on Tave for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — 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. ## Setup It takes three steps to connect Hermes to Tave. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Tave** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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 tave # connect Tave (browser OAuth) npx -y @useclawlink/cli actions tave # list available actions npx -y @useclawlink/cli run tave --input '' # 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 Tave in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Tave API key once. Verify the connection by asking Hermes: > Use Tave to apply payment to order and walk me through the result in plain English. ### 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 Tave is connected in the dashboard, that agent calls the same 129 Tave 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). ## Tave MCP for Hermes Looking for a Tave MCP server for Hermes Agent? ClawLink connects Tave to Hermes Agent and exposes 129 Tave 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 Tave integration](https://claw-link.dev/openclaw/tave) works the same way. ## What the Hermes Agent Tave integration can do 129 Tave tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 129. ### 30 of 129 Tave tools for Hermes | Tool | What it does | |---|---| | **Apply payment to order** `tave_apply_payment_to_order` | Apply a payment to a specific order in Tave | | **Create brand** `tave_create_brand` | Create a new brand in VSCO Workspace | | **Create custom field** `tave_create_custom_field` | Create a custom field in Tave for Jobs or Contacts | | **Create discount type** `tave_create_discount_type` | Create a new discount type in Tave | | **Get brand** `tave_get_brand` | Retrieve a specific brand from Tave by its ULID | | **Get event** `tave_get_event` | Get a specific event by its ID | | **Get event type** `tave_get_event_type` | Retrieve a specific event type by ID | | **Get gallery** `tave_get_gallery` | Retrieve a specific gallery by ID from Tave/VSCO Workspace | | **Get resource address book** `tave_get_resource_address_book` | Fetch a specific Address Book entity by its ULID | | **Get resource address book ca** `tave_get_resource_address_book_ca` | Fetch the address associated with a given location ID | | **Get resource custom field** `tave_get_resource_custom_field` | Fetch a specific custom field by ID from Tave | | **Get resource discount** `tave_get_resource_discount` | Retrieve a specific discount by its ID | | **Get resource discount type** `tave_get_resource_discount_type` | Get a specific discount type by ID | | **Get resource job** `tave_get_resource_job` | Fetch a specific job by ID from Tave | | **Get resource job closed reason** `tave_get_resource_job_closed_reason` | Retrieve a specific job closed reason by its ID | | **Get resource job contact** `tave_get_resource_job_contact` | Fetch a specific job contact by ID from Tave | | **Get resource job role** `tave_get_resource_job_role` | Retrieve a specific job role by its ID | | **Get resource job type** `tave_get_resource_job_type` | Retrieve a specific job type by ID | | **Get resource job worksheet** `tave_get_resource_job_worksheet` | Fetch a Job Worksheet for a specific job by job ID | | **Get resource lead source** `tave_get_resource_lead_source` | Retrieve a specific lead source by its ID | | **Get resource lead status** `tave_get_resource_lead_status` | Retrieve a specific lead status by its ID | | **Get resource my studio** `tave_get_resource_my_studio` | Retrieve information about your studio from Tave | | **Get resource note** `tave_get_resource_note` | Fetch a specific note by ID from Tave | | **Get resource order** `tave_get_resource_order` | Fetch a specific order by ID from Tave | | **Get resource payment** `tave_get_resource_payment` | Fetch a specific payment by ID from Tave | | **Get resource payment method** `tave_get_resource_payment_method` | Retrieve a specific payment method by its ID | | **Get resource product** `tave_get_resource_product` | Retrieve a specific product by its ID | | **Get resource product type** `tave_get_resource_product_type` | Retrieve a specific product type by its ID | | **Get resource profit center** `tave_get_resource_profit_center` | Retrieve a specific profit center by its ID | | **Get resource tax rate** `tave_get_resource_tax_rate` | Retrieve a specific tax rate by its ULID | ## Example prompts **Apply Payment To Order** > Use Tave to apply payment to order and walk me through the result in plain English. **Create Brand** > Create it in Tave for me, then confirm the important fields before you finish. **Create Custom Field** > Create it in Tave for me, then confirm the important fields before you finish. **Create Discount Type** > Create it in Tave for me, then confirm the important fields before you finish. ## 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 Tave working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Tave API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Tave 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 Tave. | 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 Tave actions to the runtime in a format your agent can reliably use. | 129 tools for Tave are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Tave 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 Tave in the browser, and the 129 tools above work from chat. There is no SDK and no config file, and the Tave 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 Tave 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 Tave 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 Tave tools Tave 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 Tave 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. ### Tave 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 Tave 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 Tave integration? Yes. ClawLink is the fastest way to connect Hermes to Tave: link your Tave account once in the browser and Hermes Agent can call the Tave API through 129 ready-made tools — no custom code or token handling. ### How do I connect Tave 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 Tave in the dashboard and Hermes can use it from the next message — no config files, and the Tave key you paste is stored server-side instead of in your environment. ### How long does it take to connect Tave to Hermes Agent? About two minutes. Sign in, click Connect next to Tave in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Tave 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 Tave working from chat. ### Hermes paired but still can't use Tave 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 HubSpot integration](https://claw-link.dev/hermes/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM tools](https://claw-link.dev/hermes/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce](https://claw-link.dev/hermes/salesforce) — Manage CRM data and workflows