# 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.

- Page: https://www.agent200.com/connectors/harvest/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `harvest`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

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/

## About

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.

## Harvest tools

- **List time entries** (`harvest_list_time_entries`, read): Find time entries within an explicit date, user or project scope.
- **Read a time entry** (`harvest_get_time_entry`, read): Retrieve one identified time entry and its recorded details.
- **List projects** (`harvest_list_projects`, read): Find projects when the connected role has project-list access.
- **Read a project** (`harvest_get_project`, read): Retrieve one identified project when the connected role permits it.
- **Project time report** (`harvest_time_report_by_project`, read): Read recorded time grouped by project for an explicit date range.
- **Task time report** (`harvest_time_report_by_task`, read): Read recorded time grouped by task for an explicit date range.

## Limits you can set

**Turn single tools on or off.** Let the agent read time entries and reports, and switch off `harvest_time_report_by_task` if 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "How many hours did we log on the website project this month"
- "List my time entries from last week"
- "Show hours by task for the Acme project"

## Guides: Harvest with your AI framework

- [Harvest + Claude](https://www.agent200.com/connectors/harvest/framework/claude.md): Read time entries with Claude and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.
- [Harvest + ChatGPT](https://www.agent200.com/connectors/harvest/framework/chatgpt.md): Use ChatGPT to build a separate read-only Harvest assistant with Agent200. Ground the recorded-hours briefing in returned source data.
- [Harvest + Claude Code](https://www.agent200.com/connectors/harvest/framework/claude-code.md): Use Claude Code to build a separate read-only Harvest assistant with Agent200. Ground the recorded-hours briefing in returned source data.
- [Harvest + Muse](https://www.agent200.com/connectors/harvest/framework/muse.md): Read time entries with Muse and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.
- [Harvest + Grok Bot](https://www.agent200.com/connectors/harvest/framework/grok-bot.md): Read time entries with Grok Bot and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.
- [Harvest + OpenAI Dots](https://www.agent200.com/connectors/harvest/framework/openai-dots.md): Use OpenAI Dots to build a separate read-only Harvest assistant with Agent200. Ground the recorded-hours briefing in returned source data.
- [Harvest + Claude Duet](https://www.agent200.com/connectors/harvest/framework/claude-duet.md): Read time entries with Claude Duet and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.
- [Harvest + Hermes Agent](https://www.agent200.com/connectors/harvest/framework/hermes-agent.md): Read time entries with Hermes Agent and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.
- [Harvest + OpenClaw](https://www.agent200.com/connectors/harvest/framework/openclaw.md): Read time entries with OpenClaw and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.

## FAQ

### 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](https://help.getharvest.com/api-v2/projects-api/projects/projects/).

### 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](https://help.getharvest.com/api-v2/reports-api/reports/time-reports/).

### 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.

## Related connectors

- [GitHub](https://www.agent200.com/connectors/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/connectors/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Bitbucket](https://www.agent200.com/connectors/bitbucket.md): List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
- [Jira](https://www.agent200.com/connectors/jira.md): Search, create and transition Jira issues for the connected user.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
