How to connect Greenhouse to OpenClaw
Connect Greenhouse to OpenClaw with ClawLink in one click — 134 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
GreenhouseOAUTH2MCPManage jobs, candidates, applications, and interviews. Once connected, OpenClaw can read and act on Greenhouse from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Greenhouse 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 Greenhouse setup: install one ClawHub skill, connect Greenhouse in the browser, and OpenClaw can call real Greenhouse actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Greenhouse skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Greenhouse" (hith3sh/greenhouse-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/greenhouse-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Greenhouse.
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 Greenhouse
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Greenhouse?"
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 Greenhouse in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Pull the relevant data from Greenhouse, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Greenhouse is connected in the dashboard, that agent calls the same 134 Greenhouse tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Greenhouse MCP for OpenClaw
Looking for a Greenhouse MCP server for OpenClaw? ClawLink connects Greenhouse to OpenClaw and exposes 134 Greenhouse tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Greenhouse integration works the same way.
What the OpenClaw Greenhouse integration can do
134 Greenhouse 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 134.
30 of 134 Greenhouse tools for OpenClaw
| Tool | What it does |
|---|---|
Get current user greenhouse_get_current_user | Get the Greenhouse user represented by the connected Harvest OAuth token |
List application stages greenhouse_list_application_stages | List the application stage history rows in your Greenhouse organization — one row per interview |
List applications greenhouse_list_applications | List the applications in your Greenhouse organization, which associate candidates with jobs |
List approval flows greenhouse_list_approval_flows | List the approval flows in a Greenhouse organization via the Harvest v3 API |
List approver groups greenhouse_list_approver_groups | List the approver groups in a Greenhouse organization via the Harvest v3 API |
List approvers greenhouse_list_approvers | List approver records in a Greenhouse organization via the Harvest v3 API |
List attachments greenhouse_list_attachments | List the attachments in your Greenhouse organization, which are files associated with |
List bulk requests greenhouse_list_bulk_requests | List the asynchronous bulk requests submitted to Greenhouse Harvest v3, each tracking a batch |
List candidate educations greenhouse_list_candidate_educations | List candidate educations in a Greenhouse organization via the Harvest v3 API |
List candidate employments greenhouse_list_candidate_employments | List candidate employments in a Greenhouse organization via the Harvest v3 API |
List candidate tags greenhouse_list_candidate_tags | List the candidate tags configured in a Greenhouse organization via the Harvest v3 API |
List candidates greenhouse_list_candidates | List the candidates (active applicants and prospects) in your Greenhouse organization |
List close reasons greenhouse_list_close_reasons | List the close reasons configured in a Greenhouse organization via the Harvest v3 API |
List custom field departments greenhouse_list_custom_field_departments | List the custom field department associations configured in a Greenhouse organization via the |
List custom field offices greenhouse_list_custom_field_offices | List the custom_field_office associations in a Greenhouse organization via the Harvest v3 API |
List custom field options greenhouse_list_custom_field_options | List the custom field options configured in a Greenhouse organization via the Harvest v3 API |
List custom fields greenhouse_list_custom_fields | List the custom field definitions configured in a Greenhouse organization via the Harvest v3 API |
List default interviewers greenhouse_list_default_interviewers | List the default interviewers configured in a Greenhouse organization via the Harvest v3 API |
List demographic answer options greenhouse_list_demographic_answer_options | List all of a Greenhouse organization's demographic answer options via the Harvest v3 API |
List demographic answers greenhouse_list_demographic_answers | List all of a Greenhouse organization's demographic answers via the Harvest v3 API |
List demographic question sets greenhouse_list_demographic_question_sets | List all of a Greenhouse organization's demographic question sets via the Harvest v3 API |
List demographic questions greenhouse_list_demographic_questions | List the demographic questions configured in a Greenhouse organization via the Harvest v3 API |
List departments greenhouse_list_departments | List the departments configured in a Greenhouse organization via the Harvest v3 API |
List eeoc greenhouse_list_eeoc | List EEOC self-identification responses in a Greenhouse organization via the Harvest v3 API |
List email templates greenhouse_list_email_templates | List the email templates configured in a Greenhouse organization via the Harvest v3 API |
List focus candidate attributes greenhouse_list_focus_candidate_attributes | List the focus candidate attributes in your Greenhouse organization — the subset of a job's |
List interview kits greenhouse_list_interview_kits | List the interview kits (per-job, per-slot evaluation packets interviewers see when conducting |
List interviewer tags greenhouse_list_interviewer_tags | List the interviewer tags in your Greenhouse organization: the organization-defined labels that |
List interviews greenhouse_list_interviews | List scheduled interview events in a Greenhouse organization via the Harvest v3 API |
List job board custom locations greenhouse_list_job_board_custom_locations | List a Greenhouse organization's job board custom locations via the Harvest v3 API |
Try it: find the Greenhouse tool you need
Browse the 30 Greenhouse tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Greenhouse, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Greenhouse, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Greenhouse, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Greenhouse, group them by priority, and recommend what OpenClaw should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Greenhouse working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Greenhouse app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Greenhouse through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Greenhouse. | 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 Greenhouse actions to the runtime in a format your agent can reliably use. | 134 tools for Greenhouse are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Greenhouse 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 Greenhouse in the browser, and the 134 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Greenhouse skill but can't call the tools
The ClawHub skill teaches OpenClaw about Greenhouse, but the calls run through the ClawLink plugin and your connected account. Make sure Greenhouse 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 Greenhouse 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 Greenhouse tools
Greenhouse 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 Greenhouse 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.
Greenhouse 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Greenhouse and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Greenhouse integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Greenhouse: link your Greenhouse account once in the browser and OpenClaw can call the Greenhouse API through 134 ready-made tools — no custom code or token handling.
How do I add Greenhouse to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Greenhouse skill from ClawHub, then you click Connect in the dashboard to authorize Greenhouse. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Greenhouse to OpenClaw?
About two minutes. Sign in, click Connect next to Greenhouse in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Greenhouse up myself?
The alternative to ClawLink is usually manual OAuth app 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 Greenhouse working from chat.
OpenClaw installed the Greenhouse skill but can't call the tools
The ClawHub skill teaches OpenClaw about Greenhouse, but the calls run through the ClawLink plugin and your connected account. Make sure Greenhouse 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.
