How to connect Lever to OpenClaw
Connect Lever to OpenClaw with ClawLink: paste your Lever key once and 64 tools work from chat. No MCP server to run, nothing stored on your machine.
LeverAPI KEYMCPManage candidates, opportunities, interviews, and requisitions. Once connected, OpenClaw can read and act on Lever from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Lever 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 Lever setup: install one ClawHub skill, connect Lever in the browser, and OpenClaw can call real Lever 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 Lever.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Lever
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Lever?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Lever in the ClawLink dashboard — paste your Lever API key once.
Verify the connection by asking OpenClaw:
Use Lever to download file 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Lever is connected in the dashboard, that agent calls the same 64 Lever tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Lever MCP for OpenClaw
Looking for a Lever MCP server for OpenClaw? ClawLink connects Lever to OpenClaw and exposes 64 Lever tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Lever integration works the same way.
What the OpenClaw Lever integration can do
64 Lever 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 64.
30 of 64 Lever tools for OpenClaw
| Tool | What it does |
|---|---|
Download file lever_download_file | Download a file associated with an opportunity |
Get file lever_get_file | Retrieve metadata for a single file on an opportunity |
Get form lever_get_form | Retrieve a specific profile form for an opportunity |
Get form template lever_get_form_template | Retrieve a single form template by unique identifier |
Get interview lever_get_interview | Retrieve a single interview for an opportunity |
Get note lever_get_note | Retrieve a single note for an opportunity |
Get opportunity lever_get_opportunity | Retrieve detailed information about a single opportunity |
Get panel lever_get_panel | Retrieve a single interview panel for an opportunity |
Get requisition lever_get_requisition | Retrieve detailed information about a single requisition by ID |
Get requisition field lever_get_requisition_field | Retrieve detailed information about a single custom requisition field by ID |
Get stage lever_get_stage | Retrieve detailed information about a single stage by its UUID |
Get user lever_get_user | Retrieve detailed information about a single user by their UUID |
List files lever_list_files | List all files on an opportunity |
List form templates lever_list_form_templates | List all active form templates |
List forms lever_list_forms | List all profile forms for an opportunity |
List interviews lever_list_interviews | List all interviews for an opportunity |
List notes lever_list_notes | List notes on an opportunity profile |
List offers lever_list_offers | List offers for an opportunity |
List opportunities lever_list_opportunities | List all opportunities in the hiring pipeline |
List panels lever_list_panels | List all interview panels for an opportunity |
List postings lever_list_postings | List all job postings including published, internal, closed, draft, pending, and rejected |
List referrals lever_list_referrals | List all referrals for an opportunity |
List requisition fields lever_list_requisition_fields | List all requisition field schemas in your Lever account with optional filtering |
List requisitions lever_list_requisitions | List all requisitions with filtering and pagination |
List resumes lever_list_resumes | List all resumes for an opportunity |
List sources lever_list_sources | List all recruitment sources in your Lever account |
List stages lever_list_stages | Retrieve all pipeline stages in your Lever account |
List tags lever_list_tags | List all tags in your Lever account |
List users lever_list_users | Retrieve all active users in your Lever account with optional filters |
Add opportunity links lever_add_opportunity_links | Add links to a contact associated with an opportunity |
Try it: find the Lever tool you need
Browse the 30 Lever tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Lever to download file and walk me through the result in plain English.
Pull the relevant data from Lever, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Lever, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Lever, 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 Lever working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Lever API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Lever 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 Lever. | 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 Lever actions to the runtime in a format your agent can reliably use. | 64 tools for Lever are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Lever 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 Lever in the browser, and the 64 tools above work from chat. There is no SDK and no config file, and the Lever key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Lever skill but can't call the tools
The ClawHub skill teaches OpenClaw about Lever, but the calls run through the ClawLink plugin and your connected account. Make sure Lever 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 Lever 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 Lever tools
Lever 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 Lever 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.
Lever 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 Lever has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Lever integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Lever: link your Lever account once in the browser and OpenClaw can call the Lever API through 64 ready-made tools — no custom code or token handling.
How do I add Lever to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Lever skill from ClawHub, then you click Connect in the dashboard to authorize Lever. OpenClaw calls the tools from the next message — no config files, and the Lever key you paste is stored server-side instead of in your environment.
How long does it take to connect Lever to OpenClaw?
About two minutes. Sign in, click Connect next to Lever in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Lever 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 Lever working from chat.
OpenClaw installed the Lever skill but can't call the tools
The ClawHub skill teaches OpenClaw about Lever, but the calls run through the ClawLink plugin and your connected account. Make sure Lever 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
OpenClaw Greenhouse integration
Manage jobs, candidates, applications, and interviews
Connect Ashby
Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process.
BambooHR tools
Manage employees, time-off, benefits, and hiring