# How to connect Customgpt to Hermes Agent (paste one key, 40 tools) > Connect Customgpt to Hermes with ClawLink: paste your Customgpt key once and 40 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/customgpt Most guides for giving Hermes Agent Customgpt 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 Customgpt setup: pair once in the browser and your always-on Hermes agent can act on Customgpt 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 Customgpt. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Customgpt** — 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 customgpt # connect Customgpt (browser OAuth) npx -y @useclawlink/cli actions customgpt # list available actions npx -y @useclawlink/cli run customgpt --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 Customgpt in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Customgpt API key once. Verify the connection by asking Hermes: > Use Customgpt to export leads 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 Customgpt is connected in the dashboard, that agent calls the same 40 Customgpt 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). ## Customgpt MCP for Hermes Looking for a Customgpt MCP server for Hermes Agent? ClawLink connects Customgpt to Hermes Agent and exposes 40 Customgpt 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 Customgpt integration](https://claw-link.dev/openclaw/customgpt) works the same way. ## What the Hermes Agent Customgpt integration can do 40 Customgpt 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 40. ### 30 of 40 Customgpt tools for Hermes | Tool | What it does | |---|---| | **Export leads** `customgpt_export_leads` | Export leads from a CustomGPT project | | **Get message** `customgpt_get_message` | Get message details from a CustomGPT conversation | | **Get message trust score** `customgpt_get_message_trust_score` | Retrieve verification trust score for a message in a CustomGPT conversation | | **Get page metadata** `customgpt_get_page_metadata` | Get document metadata including title, source URL, word count, and custom metadata fields | | **Get plugins** `customgpt_get_plugins` | Retrieve plugin details for a specific CustomGPT agent (project) | | **Get project** `customgpt_get_project` | Get agent details | | **Get project license** `customgpt_get_project_license` | Retrieve a license for a specific project | | **Get project settings** `customgpt_get_project_settings` | Retrieve configuration settings for a specific CustomGPT agent/project | | **Get report analysis** `customgpt_get_report_analysis` | Retrieve analytics chart data for a CustomGPT project | | **Get report conversations** `customgpt_get_report_conversations` | Get conversation analytics for a CustomGPT project | | **Get report intelligence** `customgpt_get_report_intelligence` | Get customer intelligence for a CustomGPT project | | **Get report traffic** `customgpt_get_report_traffic` | Retrieve traffic analytics for a CustomGPT agent/project | | **Get stats** `customgpt_get_stats` | Get agent statistics | | **Get usage limits** `customgpt_get_usage_limits` | Get account usage limits showing current usage vs | | **Get user profile** `customgpt_get_user_profile` | Retrieve the current user's profile information | | **List conversation messages** `customgpt_list_conversation_messages` | Retrieves all messages from a CustomGPT conversation, including both user queries and AI | | **List pages** `customgpt_list_pages` | Lists all documents in a CustomGPT agent's knowledge base | | **List personas** `customgpt_list_personas` | List persona versions for a CustomGPT agent | | **List project licenses** `customgpt_list_project_licenses` | List all licenses for a CustomGPT project/agent | | **List projects** `customgpt_list_projects` | Lists all CustomGPT projects (agents) for the authenticated user | | **List sources** `customgpt_list_sources` | List all data sources connected to an agent | | **Search team members** `customgpt_search_team_members` | Search for team members by email address or user ID | | **Activate persona version** `customgpt_activate_persona_version` | Restore a previous persona version for a CustomGPT agent | | **Add source** `customgpt_add_source` | Add a data source to a CustomGPT agent's knowledge base | | **Clone project** `customgpt_clone_project` | Clone a CustomGPT agent (project) | | **Create conversation** `customgpt_create_conversation` | Create a new conversation session for a CustomGPT agent | | **Create project** `customgpt_create_project` | Create a new CustomGPT agent from a sitemap URL or file upload | | **Reindex page** `customgpt_reindex_page` | Reindex a document in CustomGPT knowledge base | | **Submit message feedback** `customgpt_submit_message_feedback` | Submit feedback (thumbs up/down) for a message in a CustomGPT conversation | | **Update page metadata** `customgpt_update_page_metadata` | Update document metadata for a specific page in a CustomGPT project | ## Example prompts **Export Leads** > Use Customgpt to export leads and walk me through the result in plain English. **Get Message** > Pull the relevant data from Customgpt, summarize it in plain English, and point out anything that needs attention. **Get Message Trust Score** > Pull the relevant data from Customgpt, summarize it in plain English, and point out anything that needs attention. **Get Page Metadata** > Pull the relevant data from Customgpt, 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 Customgpt working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Customgpt API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Customgpt 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 Customgpt. | 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 Customgpt actions to the runtime in a format your agent can reliably use. | 40 tools for Customgpt are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Customgpt 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 Customgpt in the browser, and the 40 tools above work from chat. There is no SDK and no config file, and the Customgpt 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 Customgpt 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 Customgpt 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 Customgpt tools Customgpt 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 Customgpt 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. ### Customgpt 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 Customgpt 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 Customgpt integration? Yes. ClawLink is the fastest way to connect Hermes to Customgpt: link your Customgpt account once in the browser and Hermes Agent can call the Customgpt API through 40 ready-made tools — no custom code or token handling. ### How do I connect Customgpt 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 Customgpt in the dashboard and Hermes can use it from the next message — no config files, and the Customgpt key you paste is stored server-side instead of in your environment. ### How long does it take to connect Customgpt to Hermes Agent? About two minutes. Sign in, click Connect next to Customgpt in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Customgpt 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 Customgpt working from chat. ### Hermes paired but still can't use Customgpt 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 - [DataRobot tools](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.