How to connect Harvest to OpenClaw
Connect Harvest to OpenClaw with ClawLink in one click — 57 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
HarvestOAUTH2MCPTrack time, manage projects, and invoice clients. Once connected, OpenClaw can read and act on Harvest from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Harvest 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 Harvest setup: install one ClawHub skill, connect Harvest in the browser, and OpenClaw can call real Harvest actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Harvest 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 "Harvest" (hith3sh/harvest) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/harvest
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 Harvest.
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 Harvest
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Harvest?"
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 Harvest in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Pull the relevant data from Harvest, 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 Harvest is connected in the dashboard, that agent calls the same 57 Harvest tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Harvest MCP for OpenClaw
Looking for a Harvest MCP server for OpenClaw? ClawLink connects Harvest to OpenClaw and exposes 57 Harvest tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Harvest integration works the same way.
What the OpenClaw Harvest integration can do
57 Harvest 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 57.
30 of 57 Harvest tools for OpenClaw
| Tool | What it does |
|---|---|
Get client harvest_get_client | Retrieves a specific client by ID from Harvest |
Get company info harvest_get_company_info | Retrieves detailed information about the company associated with the authenticated Harvest |
Get estimate harvest_get_estimate | Retrieve a specific estimate by ID |
Get invoice harvest_get_invoice | Retrieve a specific invoice by ID |
Get project harvest_get_project | Retrieve a specific Harvest project by ID |
Get task harvest_get_task | Retrieve a specific task by ID |
Get time entry harvest_get_time_entry | Retrieve a single time entry by ID |
Get user harvest_get_user | Retrieve a specific user by ID |
List client contacts harvest_list_client_contacts | List client contacts |
List clients harvest_list_clients | List clients |
List estimate messages harvest_list_estimate_messages | Lists all messages associated with a specific estimate in Harvest |
List expense categories harvest_list_expense_categories | List expense categories |
List invoice item categories harvest_list_invoice_item_categories | Retrieve invoice item categories |
List invoice messages harvest_list_invoice_messages | List messages associated with a given invoice |
List invoice payments harvest_list_invoice_payments | List all payments recorded for a specific invoice |
List invoices harvest_list_invoices | List invoices |
List projects harvest_list_projects | List projects |
List tasks harvest_list_tasks | List tasks |
List time entries harvest_list_time_entries | Retrieve a list of time entries |
List users harvest_list_users | List users |
Create client harvest_create_client | Create a new client |
Create client contact harvest_create_client_contact | Create a new client contact |
Create estimate harvest_create_estimate | Create a new estimate |
Create estimate item category harvest_create_estimate_item_category | Create a new estimate item category in Harvest |
Create estimate message harvest_create_estimate_message | Create a new message for an estimate |
Create expense harvest_create_expense | Create a new expense entry |
Create invoice harvest_create_invoice | Create a new invoice |
Create invoice item category harvest_create_invoice_item_category | Create a new invoice item category |
Create invoice message harvest_create_invoice_message | Creates a new message for an invoice in Harvest |
Create invoice payment harvest_create_invoice_payment | Create a new payment on an invoice |
Try it: find the Harvest tool you need
Browse the 30 Harvest 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 Harvest, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Harvest, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Harvest, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Harvest, summarize it in plain English, and point out anything that needs attention.
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 Harvest working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Harvest app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Harvest 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 Harvest. | 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 Harvest actions to the runtime in a format your agent can reliably use. | 57 tools for Harvest are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Harvest 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 Harvest in the browser, and the 57 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 Harvest skill but can't call the tools
The ClawHub skill teaches OpenClaw about Harvest, but the calls run through the ClawLink plugin and your connected account. Make sure Harvest 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 Harvest 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 Harvest tools
Harvest 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 Harvest 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.
Harvest 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 Harvest 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 Harvest integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Harvest: link your Harvest account once in the browser and OpenClaw can call the Harvest API through 57 ready-made tools — no custom code or token handling.
How do I add Harvest to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Harvest skill from ClawHub, then you click Connect in the dashboard to authorize Harvest. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Harvest to OpenClaw?
About two minutes. Sign in, click Connect next to Harvest in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Harvest 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 Harvest working from chat.
OpenClaw installed the Harvest skill but can't call the tools
The ClawHub skill teaches OpenClaw about Harvest, but the calls run through the ClawLink plugin and your connected account. Make sure Harvest 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.
