Source connector

Harvest connector

Harvest integration for databases, warehouses and BI tools

Time tracking and project profitability for services teams. Datrise captures Harvest entities such as time entries, projects, clients, invoices, and utilization, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Harvest API v2 (REST, time tracking) authenticates with OAuth 2.0, personal access token, incremental runs key on updated_since query parameter (ISO-8601) on most list endpoints, e.g. time_entries, invoices, expenses, and Harvest caps calls at 100 requests per 15 seconds per access token for the core API; 100 requests per 15 minutes for the separate Reports API.

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `harvest_time_entries`) with a schema derived from the Harvest API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Harvest pipeline page, and join the waitlist to get the Harvest connector (Work management) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Harvest data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
time entries	harvest_time_entries	Upsert by primary key, incremental on updated-at
projects	harvest_projects	Upsert by primary key, incremental on updated-at
clients	harvest_clients	Upsert by primary key, incremental on updated-at
invoices	harvest_invoices	Append-only, incremental by timestamp
utilization	harvest_utilization	Upsert by primary key, incremental on updated-at

Harvest API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Harvest API v2 (REST, time tracking)
Authentication	OAuth 2.0, personal access token — Authorization: Bearer token (OAuth2 or a Personal Access Token) plus a required Harvest-Account-Id header identifying the account.
Pagination	page — page or cursor query params (mutually exclusive); per_page defaults to and caps at 2,000. Always follow the response body's links object (first/next/previous/last) rather than constructing URLs yourself.
Rate limit	100 requests per 15 seconds per access token for the core API; 100 requests per 15 minutes for the separate Reports API
Incremental cursor	updated_since query parameter (ISO-8601) on most list endpoints, e.g. time_entries, invoices, expenses
Webhooks	No
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Harvest

per_page defaults to and caps at 2,000 — unlike most REST APIs, requesting a smaller page doesn't reduce Harvest's per-request cost, so throttling comes from request count, not payload size.
The core API allows 100 requests per 15 seconds while the separate Reports API is capped at only 100 requests per 15 minutes; mixing report pulls into the same budget as core-entity polling throttles reporting far sooner than expected.
Every request must include a Harvest-Account-Id header alongside the Bearer token; omitting it fails even with a valid, unexpired access token.
Harvest v2 has no webhooks and no bulk-export or deleted-records endpoint, so a full incremental pipeline must poll updated_since on every entity and cannot detect hard deletes at all.

Compare this against every other documented API

Popular destinations for Harvest

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Harvest connector FAQ

What Harvest data does the connector extract?: 5 objects: time entries, projects, clients, invoices and utilization. Each lands in its own table with types preserved; history-style objects (1: invoices) load as append-only streams.
Is the Harvest integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Harvest data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Harvest → destination pair has its own page with the object-to-table mapping.

Related Work management sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Harvest pipeline with guided onboarding

Join the waitlist to get priority access for Harvest integrations with guided setup, schema-aware mapping, and production-grade incremental sync.