# How to connect Backendless to Hermes Agent (paste one key, 30 tools) > Connect Backendless to Hermes with ClawLink: paste your Backendless key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/backendless Most guides for giving Hermes Agent Backendless 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 Backendless setup: pair once in the browser and your always-on Hermes agent can act on Backendless 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 Backendless. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Backendless** — 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 backendless # connect Backendless (browser OAuth) npx -y @useclawlink/cli actions backendless # list available actions npx -y @useclawlink/cli run backendless --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 Backendless in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Backendless API key once. Verify the connection by asking Hermes: > Use Backendless to directory listing 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 Backendless is connected in the dashboard, that agent calls the same 30 Backendless 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). ## Backendless MCP for Hermes Looking for a Backendless MCP server for Hermes Agent? ClawLink connects Backendless to Hermes Agent and exposes 30 Backendless 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 Backendless integration](https://claw-link.dev/openclaw/backendless) works the same way. ## What the Hermes Agent Backendless integration can do 30 Backendless tools are ready for Hermes Agent once the account is connected. The 26 below are the ones people reach for most; your agent can call all 30. ### 26 of 30 Backendless tools for Hermes | Tool | What it does | |---|---| | **Directory listing** `backendless_directory_listing` | Retrieve a listing of files and directories at a given path | | **General object retrieval** `backendless_general_object_retrieval` | Retrieve objects from a specified Backendless table with filtering, sorting, and pagination | | **Get all values** `backendless_get_all_values` | Retrieve all values from a map in a specified Hive | | **Get counter value** `backendless_get_counter_value` | Retrieve the current value of a Backendless counter | | **Get file count** `backendless_get_file_count` | Get the count of files in a Backendless directory | | **Get key items** `backendless_get_key_items` | Retrieve values for a specified key in a list (all, single, or range) | | **Get timer** `backendless_get_timer` | Retrieve information about a specific timer | | **User find** `backendless_user_find` | Retrieve user information by ID | | **Validate user token** `backendless_validate_user_token` | Validate a user session token | | **Copy file** `backendless_copy_file` | Copy a file or directory within Backendless file storage | | **Create directory** `backendless_create_directory` | Create a new directory at the specified path | | **Create hive** `backendless_create_hive` | Create a new Hive | | **Create timer** `backendless_create_timer` | Create a new timer with schedule and code | | **Map put** `backendless_map_put` | Set or update key-value pairs in a Hive map | | **Move file** `backendless_move_file` | Move a file or directory within Backendless file storage | | **Publish message** `backendless_publish_message` | Publish a message to a specified messaging channel | | **Reset counter** `backendless_reset_counter` | Reset a Backendless counter back to zero | | **Set counter value** `backendless_set_counter_value` | Set a Backendless counter to a specific value conditionally | | **Update timer** `backendless_update_timer` | Update schedule or code of an existing timer | | **User grant permission** `backendless_user_grant_permission` | Grant a permission to a user on a specific data object | | **User login** `backendless_user_login` | Log in a registered user with identity and password | | **User password recovery** `backendless_user_password_recovery` | Initiate password recovery for a user | | **User registration** `backendless_user_registration` | Register a new user with email and password | | **User update** `backendless_user_update` | Update properties of an existing Backendless user | | **User logout** `backendless_user_logout` | Log out the currently authenticated user | | **User revoke permission** `backendless_user_revoke_permission` | Revoke a permission from a specified user or role on a specific data object | ## Example prompts **Directory Listing** > Use Backendless to directory listing and walk me through the result in plain English. **General Object Retrieval** > Use Backendless to general object retrieval and walk me through the result in plain English. **Get All Values** > Pull the relevant data from Backendless, summarize it in plain English, and point out anything that needs attention. **Get Counter Value** > Pull the relevant data from Backendless, 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 Backendless working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Backendless API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Backendless 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 Backendless. | 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 Backendless actions to the runtime in a format your agent can reliably use. | 30 tools for Backendless are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Backendless 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 Backendless in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Backendless 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 Backendless 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 Backendless 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 Backendless tools Backendless 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 Backendless 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. ### Backendless 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 Backendless 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 Backendless integration? Yes. ClawLink is the fastest way to connect Hermes to Backendless: link your Backendless account once in the browser and Hermes Agent can call the Backendless API through 30 ready-made tools — no custom code or token handling. ### How do I connect Backendless 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 Backendless in the dashboard and Hermes can use it from the next message — no config files, and the Backendless key you paste is stored server-side instead of in your environment. ### How long does it take to connect Backendless to Hermes Agent? About two minutes. Sign in, click Connect next to Backendless in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Backendless 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 Backendless working from chat. ### Hermes paired but still can't use Backendless 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 - [GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/hermes/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.