> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/time-tracking/harvest/faq.md).

# FAQ

<details>

<summary>What's the difference between "Time entries" and "Report: Time report"?</summary>

**Time entries** returns one row per individual log entry — with fields like hours, notes, user, project, and task. It's raw data, best for payroll inputs or custom calculations.

**Report: Time report** returns aggregated rows grouped by a dimension you choose (client, project, task, or team member). It's faster to work with for dashboards and summaries, and supports a date range filter via From and To fields.

</details>

<details>

<summary>How do I filter Time entries by the date work was done (not when it was last edited)?</summary>

The **"Changed after"** field in Time entries filters on `updated_at` — the last time the record was modified. To filter by the actual work date (`spent_date`), use the **Report: Time report** entity instead, which has explicit **From** and **To** date fields tied to when the work was performed.

</details>

<details>

<summary>Can I filter by team member, billable status, or other fields?</summary>

Yes — use **Advanced filters** in the data flow settings. For boolean fields like `billable` or `is_active`, make sure to enter values in lowercase (`true` or `false`). For filtering by team member, you can filter on `user.name` in Time entries, or choose "team member" as the report type in the Time report.

</details>

<details>

<summary>Why is my weekly_capacity showing a huge number instead of hours?</summary>

Harvest returns `weekly_capacity` in **seconds** via their API — this is documented behavior, not a Coupler.io bug. Divide the value by 3600 to get hours. You can add a calculated column in your destination spreadsheet or use a transformation step in Coupler.io to do this automatically.

</details>

<details>

<summary>How do I find a Project ID to use as a filter?</summary>

Open Harvest and navigate to the project. Look at the URL in your browser — the project ID is the number after the last slash. For example, in `https://couplerio3.harvestapp.com/projects/29290029`, the ID is `29290029`. Paste this into the **Project ID** field in Coupler.io. Note that you can only filter by one project at a time.

</details>

<details>

<summary>Can I combine data from multiple Harvest accounts?</summary>

Yes. Create a separate data flow for each account and use the **Append** transformation to combine them into one destination. This is useful for agencies or holding companies managing multiple Harvest accounts.

</details>

<details>

<summary>My data flow hits the row limit. How do I reduce my dataset size?</summary>

The most effective approaches are:

* Set a **From** and **To** date on Time report entities to limit the reporting window
* Use the **"Changed after"** filter on Time entries to pull only recently modified records
* Filter by **Project ID** to pull one project at a time
* Split your data across multiple data flows and use **Append** to combine them

{% hint style="info" %}
See [Common Issues](/sources/category/time-tracking/harvest/common-issues.md) for more on rate limits and timeouts.
{% endhint %}

</details>

<details>

<summary>Can I send Harvest data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including **ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw**. This is useful for generating narrative summaries of time reports, flagging over-budget projects, or creating client-ready writeups from raw billing data.

</details>

<details>

<summary>I only see my own data — why can't I see data for other team members?</summary>

Harvest API access is role-dependent. If you connected using a **Member**-level account, you'll only see your own records. To pull team-wide data, reconnect using an **Administrator** or **Manager** Harvest account.

{% hint style="info" %}
See [Common Issues → Permission errors](/sources/category/time-tracking/harvest/common-issues.md) for steps to reconnect.
{% endhint %}

</details>

<details>

<summary>Can I join Harvest data with data from another source?</summary>

Yes. Coupler.io's **Join** transformation lets you combine Harvest data with other sources in the same data flow. For example, you could join Harvest time entries with a project list from a project management tool, or combine Harvest invoices with payment data from your accounting software.

{% hint style="info" %}
For ideas on which entities to combine, see [Data Overview → Common metric combinations](/sources/category/time-tracking/harvest/data-overview.md).
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/time-tracking/harvest/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.