Developer tools
Harvest for AI agents.
Make recorded time easier to review.
Read Harvest time entries and authorized projects or reports. Prepare recorded-hours briefings within the connected user’s role.
About Harvest
With the Harvest connector, your agent reads time tracking data in each user’s own Harvest account. It can list time entries, read an entry, list projects, and run time reports by project or by task, using only the tools your project allows.
Harvest is a time tracking and invoicing service for teams.
Tools
What your agent can do in Harvest.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Harvest connection.
-
List time entries
Readharvest_list_time_entriesFind time entries within an explicit date, user or project scope.
-
Read a time entry
Readharvest_get_time_entryRetrieve one identified time entry and its recorded details.
-
List projects
Readharvest_list_projectsFind projects when the connected role has project-list access.
-
Read a project
Readharvest_get_projectRetrieve one identified project when the connected role permits it.
-
Project time report
Readharvest_time_report_by_projectRead recorded time grouped by project for an explicit date range.
-
Task time report
Readharvest_time_report_by_taskRead recorded time grouped by task for an explicit date range.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Harvest, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read time entries and reports, and switch off
harvest_time_report_by_taskif it should only report by project. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example time entries and projects but not reports. A call outside them is refused.
Get started
Connect Harvest
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Harvest
Each end user authorizes their own Harvest account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Harvest account, once. const connection = await agent200 .user("user_123") .connect("harvest"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Harvest tools
Name the user, the model and the tools. The model decides which Harvest tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "How many hours did we log on the website project this month", tools: ["harvest"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Connect the intended Harvest account
Authorize Harvest through the user’s OAuth connection and select the correct Harvest account when several are available.
-
Match the user’s role to the request
Time-entry and report visibility varies by Administrator, Manager or Member role. Project listing is restricted to Administrators and Managers with managed projects.
-
Set an explicit reporting period
Choose the account and date range before reading entries or reports. Keep the Agent200 key in secure application configuration.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Harvest connector and how to use it.
Connector: Harvest, through Agent200. In code: "harvest". What it does: Read Harvest time entries and authorized projects or reports. Prepare recorded-hours briefings within the connected user’s role. Page: https://www.agent200.com/connectors/harvest/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Harvest's own page, through the authorization link Agent200 returns. Never ask a user for a Harvest password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: harvest_list_time_entries, harvest_get_time_entry, harvest_list_projects, harvest_get_project, harvest_time_report_by_project, harvest_time_report_by_task. Name "harvest" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/harvest/framework/claude/ https://www.agent200.com/connectors/harvest/framework/chatgpt/ https://www.agent200.com/connectors/harvest/framework/claude-code/ https://www.agent200.com/connectors/harvest/framework/muse/ https://www.agent200.com/connectors/harvest/framework/grok-bot/ https://www.agent200.com/connectors/harvest/framework/openai-dots/ https://www.agent200.com/connectors/harvest/framework/claude-duet/ https://www.agent200.com/connectors/harvest/framework/hermes-agent/ https://www.agent200.com/connectors/harvest/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/harvest.md
Guides
Use Harvest with the AI you build on.
Step-by-step setup for Harvest with a specific model, assistant or agent framework.
-
Harvest + Claude
How to connect Harvest to Claude
-
Harvest + ChatGPT
How to connect Harvest to ChatGPT
-
Harvest + Claude Code
How to connect Harvest to Claude Code
-
Harvest + Muse
How to connect Harvest to Muse
-
Harvest + Grok Bot
How to connect Harvest to Grok Bot
-
Harvest + OpenAI Dots
How to connect Harvest to OpenAI Dots
-
Harvest + Claude Duet
How to connect Harvest to Claude Duet
-
Harvest + Hermes Agent
How to connect Harvest to Hermes Agent
-
Harvest + OpenClaw
How to connect Harvest to OpenClaw
FAQ
Harvest and Agent200, answered.
Can every user list all projects?
No. Harvest project listing requires an Administrator or a Manager with managed projects; a Member may receive a 403. Time-entry visibility also follows the connected role. Harvest projects reference.
Are time reports complete company totals?
Only for the account, role, date range and returned pages the user can access. Harvest requires from and to dates; the documented range is at most 365 days. Time reports reference.
Which Harvest account is used?
Use the authorized account selected for the request. Harvest OAuth can grant access to several accounts and API requests identify the account separately.
Can the agent start a timer or edit entries?
The listed operations read time entries and reports. A suggested correction in the response is not saved to Harvest.
What if a member sees only their own time?
State that the briefing covers the member’s visible entries. Do not infer team totals or unseen project activity from a partial response.