Field Guide

Harvest integration

Connect Harvest for bidirectional time tracking sync. Time entries flow between Field and Harvest automatically — log time in either system and it appears in both. Contacts and projects stay mapped so everything stays in sync.

What it does

The Harvest integration connects your existing time tracking workflow to Field's work and budget system. Time logged in Field pushes to Harvest. Time logged in Harvest pulls into Field. Client contacts are mapped between systems so hours land against the right budgets.

How to connect

Go to Integrations and find the Harvest card. You'll need two things from your Harvest account:

  • • Account ID — found in Harvest under Settings → Account
  • • Personal Access Token — generate one at id.getharvest.com/developers

Enter both values on the Integrations page. Field validates the connection immediately and shows your Harvest account name when successful.

Contact mapping

After connecting, Field lists your Harvest clients alongside your Field clients. Map each Harvest client to their Field counterpart. This is how Field knows which Harvest time entries belong to which client budget.

Unmapped Harvest clients are ignored during sync — their time entries won't appear in Field. You can map and unmap clients at any time from the Harvest integration settings.

Project setup

Each mapped client can have a Harvest project associated with it. When Field pushes time entries to Harvest, they land in the specified project. If no project is mapped, Field creates time entries under the client without a project association.

Bidirectional sync

Time flows in both directions:

Field → Harvest

When you log time on a work item in Field, the entry pushes to Harvest under the mapped client and project. The work item description becomes the Harvest note.

Harvest → Field

Time entries logged directly in Harvest for mapped clients pull into Field during sync. They appear as recorded time against the client's budget and show up in Settlement.

Sync runs periodically. Duplicate entries are detected by external ID — logging the same time in both systems won't create duplicates.

Time proposals in Inbound

When Harvest entries arrive for a client, they may appear as time proposals in your Inbound pipeline if they don't match an existing work item. This gives you a chance to associate the time with the right context before it settles against the client's budget.

Next: Stripe integration →