# How to connect Breathe HR to OpenClaw (paste one key, 50 tools) > Connect Breathe HR to OpenClaw with ClawLink: paste your Breathe HR key once and 50 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/breathehr The usual route to Breathe HR 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 Breathe HR setup: install one ClawHub skill, connect Breathe HR in the browser, and OpenClaw can call real Breathe HR actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Breathe HR. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Breathe HR** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 breathehr # connect Breathe HR (browser OAuth) npx -y @useclawlink/cli actions breathehr # list available actions npx -y @useclawlink/cli run breathehr --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 Breathe HR in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Breathe HR API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Breathe HR, summarize it in plain English, and point out anything that needs attention. ### 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 Breathe HR is connected in the dashboard, that agent calls the same 50 Breathe HR 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). ## Breathe HR MCP for OpenClaw Looking for a Breathe HR MCP server for OpenClaw? ClawLink connects Breathe HR to OpenClaw and exposes 50 Breathe HR 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 Breathe HR integration](https://claw-link.dev/hermes/breathehr) works the same way. ## What the OpenClaw Breathe HR integration can do 50 Breathe HR 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 50. ### 30 of 50 Breathe HR tools for OpenClaw | Tool | What it does | |---|---| | **Get account** `breathehr_get_account` | Retrieve account information including ID, name, domain, UUID, and RTA usage status | | **Get employee** `breathehr_get_employee` | Retrieve detailed information about a specific employee by ID | | **Get employee expense** `breathehr_get_employee_expense` | Retrieve a specific employee expense record by ID | | **Get leave request** `breathehr_get_leave_request` | Retrieve detailed information about a specific leave request by ID | | **Get leave request cancelling** `breathehr_get_leave_request_cancelling` | Retrieve the leave request that is being cancelled | | **List absences** `breathehr_list_absences` | List all absences with optional filtering by date range, employee, department, and type | | **List benefits** `breathehr_list_benefits` | Retrieve a list of employee benefits with optional pagination | | **List bonuses** `breathehr_list_bonuses` | Retrieve employee bonuses from BreatheHR with pagination support | | **List change requests** `breathehr_list_change_requests` | List change requests from BreatheHR | | **List company documents** `breathehr_list_company_documents` | Retrieve a paginated list of company documents from BreatheHR | | **List company projects** `breathehr_list_company_projects` | List company projects from BreatheHR | | **List company training types** `breathehr_list_company_training_types` | List company training types | | **List department absences** `breathehr_list_department_absences` | List absences for a specific department | | **List department benefits** `breathehr_list_department_benefits` | List all employee benefits for a specific department | | **List department bonuses** `breathehr_list_department_bonuses` | List bonuses for a specific department | | **List department leave requests** `breathehr_list_department_leave_requests` | List leave requests for a specific department | | **List department salaries** `breathehr_list_department_salaries` | List salaries for a specific department | | **List departments** `breathehr_list_departments` | List all company departments from BreatheHR | | **List divisions** `breathehr_list_divisions` | Retrieve all company divisions | | **List employee absences** `breathehr_list_employee_absences` | List absences for a specific employee from BreatheHR | | **List employee benefits** `breathehr_list_employee_benefits` | List benefits for an employee | | **List employee bonuses** `breathehr_list_employee_bonuses` | List bonuses for a specific employee | | **List employee change requests** `breathehr_list_employee_change_requests` | List change requests for a specific employee | | **List employee expense claims** `breathehr_list_employee_expense_claims` | List employee expense claims from BreatheHR | | **List employee expenses** `breathehr_list_employee_expenses` | List employee expenses from BreatheHR | | **List employee holiday years** `breathehr_list_employee_holiday_years` | Get holiday years for an employee | | **List employee jobs** `breathehr_list_employee_jobs` | List employee jobs with optional employee filtering | | **List employee leave requests** `breathehr_list_employee_leave_requests` | List leave requests for a specific employee | | **List employee salaries** `breathehr_list_employee_salaries` | List salaries for a specific employee | | **List employee training courses** `breathehr_list_employee_training_courses` | List employee training courses with optional filtering by employee and pagination support | ## Example prompts **Get Account** > Pull the relevant data from Breathe HR, summarize it in plain English, and point out anything that needs attention. **Get Employee** > Pull the relevant data from Breathe HR, summarize it in plain English, and point out anything that needs attention. **Get Employee Expense** > Pull the relevant data from Breathe HR, summarize it in plain English, and point out anything that needs attention. **Get Leave Request** > Pull the relevant data from Breathe HR, 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Breathe HR working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Breathe HR API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Breathe HR 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 Breathe HR. | 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 Breathe HR actions to the runtime in a format your agent can reliably use. | 50 tools for Breathe HR are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Breathe HR 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 Breathe HR in the browser, and the 50 tools above work from chat. There is no SDK and no config file, and the Breathe HR 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 Breathe HR skill but can't call the tools The ClawHub skill teaches OpenClaw about Breathe HR, but the calls run through the ClawLink plugin and your connected account. Make sure Breathe HR 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 Breathe HR 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 Breathe HR tools Breathe HR 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 Breathe HR 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. ### Breathe HR 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 Breathe HR has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Breathe HR integration? Yes. ClawLink is the fastest way to connect OpenClaw to Breathe HR: link your Breathe HR account once in the browser and OpenClaw can call the Breathe HR API through 50 ready-made tools — no custom code or token handling. ### How do I add Breathe HR to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Breathe HR skill from ClawHub, then you click Connect in the dashboard to authorize Breathe HR. OpenClaw calls the tools from the next message — no config files, and the Breathe HR key you paste is stored server-side instead of in your environment. ### How long does it take to connect Breathe HR to OpenClaw? About two minutes. Sign in, click Connect next to Breathe HR in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Breathe HR 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 Breathe HR working from chat. ### OpenClaw installed the Breathe HR skill but can't call the tools The ClawHub skill teaches OpenClaw about Breathe HR, but the calls run through the ClawLink plugin and your connected account. Make sure Breathe HR 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 - [Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Moco tools](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints