# How to connect Ashby to OpenClaw (paste one key, 125 tools) > Connect Ashby to OpenClaw with ClawLink: paste your Ashby key once and 125 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ashby The usual route to Ashby 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 Ashby setup: install one ClawHub skill, connect Ashby in the browser, and OpenClaw can call real Ashby actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/ashby ## Setup It takes three steps to connect OpenClaw to Ashby. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Ashby** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 ashby # connect Ashby (browser OAuth) npx -y @useclawlink/cli actions ashby # list available actions npx -y @useclawlink/cli run ashby --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 Ashby in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ashby API key once. Verify the connection by asking OpenClaw: > Use Ashby to add candidate project and walk me through the result in plain English. ### 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 Ashby is connected in the dashboard, that agent calls the same 125 Ashby 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). ## Ashby MCP for OpenClaw Looking for a Ashby MCP server for OpenClaw? ClawLink connects Ashby to OpenClaw and exposes 125 Ashby 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 Ashby integration](https://claw-link.dev/hermes/ashby) works the same way. ## What the OpenClaw Ashby integration can do 125 Ashby tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 125. ### 30 of 125 Ashby tools for OpenClaw | Tool | What it does | |---|---| | **Add candidate project** `ashby_add_candidate_project` | Add a candidate to a project in Ashby | | **Add candidate tag** `ashby_add_candidate_tag` | Add a tag to a candidate in Ashby | | **Add hiring team member** `ashby_add_hiring_team_member` | Add an Ashby user to a hiring team at the application, job, or opening level | | **Add interviewer pool user** `ashby_add_interviewer_pool_user` | Add a user to an interviewer pool | | **Get API key info** `ashby_get_api_key_info` | Retrieve information about the current API key, including associated organization, user details, and permissions | | **Get application info** `ashby_get_application_info` | Retrieve detailed information about a specific application by its ID | | **Get candidate info** `ashby_get_candidate_info` | Retrieve detailed information about a specific candidate by their ID | | **Get custom field info** `ashby_get_custom_field_info` | Retrieve detailed information about a specific custom field by its ID | | **Get department info** `ashby_get_department_info` | Retrieve detailed information about a specific department by its ID | | **Get feedback form definition** `ashby_get_feedback_form_definition` | Retrieve detailed information about a specific feedback form definition by its ID | | **Get file info** `ashby_get_file_info` | Retrieve the URL of a file associated with a candidate | | **Get interview info** `ashby_get_interview_info` | Retrieve detailed information about a specific interview type by its ID | | **Get interview stage info** `ashby_get_interview_stage_info` | Fetch interview stage details by ID | | **Get interviewer pool info** `ashby_get_interviewer_pool_info` | Retrieve detailed information about a specific interviewer pool by its ID | | **Get interviewer user settings** `ashby_get_interviewer_user_settings` | Get interviewer settings for a specific user by their ID | | **Get job info** `ashby_get_job_info` | Retrieve detailed information about a specific job by its ID | | **Get job interview plan info** `ashby_get_job_interview_plan_info` | Retrieve the interview plan information for a specific job | | **Get job posting info** `ashby_get_job_posting_info` | Retrieve detailed information about a specific job posting by its ID | | **Get location info** `ashby_get_location_info` | Retrieve detailed information about a specific location by its ID | | **Get offer info** `ashby_get_offer_info` | Retrieve detailed information about a specific offer by its ID | | **Get opening info** `ashby_get_opening_info` | Retrieve detailed information about a specific opening (job requisition) by its ID | | **Get survey form definition** `ashby_get_survey_form_definition` | Retrieve detailed information about a specific survey form definition by its ID | | **Get user info** `ashby_get_user_info` | Retrieve detailed information about a specific user by their ID | | **List application criteria evaluations** `ashby_list_application_criteria_evaluations` | Retrieve AI-generated criteria evaluations for an application | | **List application feedback** `ashby_list_application_feedback` | Retrieve all feedback submissions for an application | | **List application hiring team role** `ashby_list_application_hiring_team_role` | Retrieve all available hiring team roles for applications in the organization | | **List application history** `ashby_list_application_history` | Retrieve the complete history of stage transitions for an application | | **List applications** `ashby_list_applications` | Retrieve a list of applications with optional pagination and sync-token filtering for | | **List approval** `ashby_list_approval` | Retrieve a list of approvals (offer approvals, job approvals, etc.) | | **List archive reasons** `ashby_list_archive_reasons` | Retrieve a list of all archive reasons | ## Example prompts **Add Candidate Project** > Use Ashby to add candidate project and walk me through the result in plain English. **Add Candidate Tag** > Use Ashby to add candidate tag and walk me through the result in plain English. **Add Hiring Team Member** > Use Ashby to add hiring team member and walk me through the result in plain English. **Add Interviewer Pool User** > Use Ashby to add interviewer pool user and walk me through the result in plain English. ## 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 Ashby working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ashby API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ashby 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 Ashby. | 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 Ashby actions to the runtime in a format your agent can reliably use. | 125 tools for Ashby are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ashby 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 Ashby in the browser, and the 125 tools above work from chat. There is no SDK and no config file, and the Ashby 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 Ashby skill but can't call the tools The ClawHub skill teaches OpenClaw about Ashby, but the calls run through the ClawLink plugin and your connected account. Make sure Ashby 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 Ashby 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 Ashby tools Ashby 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 Ashby 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. ### Ashby 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 Ashby has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Ashby integration? Yes. ClawLink is the fastest way to connect OpenClaw to Ashby: link your Ashby account once in the browser and OpenClaw can call the Ashby API through 125 ready-made tools — no custom code or token handling. ### How do I add Ashby to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ashby skill from ClawHub, then you click Connect in the dashboard to authorize Ashby. OpenClaw calls the tools from the next message — no config files, and the Ashby key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ashby to OpenClaw? About two minutes. Sign in, click Connect next to Ashby in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Ashby 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 Ashby working from chat. ### OpenClaw installed the Ashby skill but can't call the tools The ClawHub skill teaches OpenClaw about Ashby, but the calls run through the ClawLink plugin and your connected account. Make sure Ashby 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 - [BambooHR](https://claw-link.dev/openclaw/bamboohr) — Manage employees, time-off, benefits, and hiring