Linking Harvey as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Harvey connector syncs audit logs, usage history, query history, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Harvey API token to pull audit logs, usage and query history, client matters, and Vault project metadata.
Create an API token in Harvey workspace settings under API Tokens (if you don't see that section, ask your Harvey Customer Success Manager to enable API access).
Each token carries a per-endpoint permissions list - grant access for the endpoints you want to sync: audit logs, history exports, client matters, and Vault.
You'll be asked for:
- API token
- Region: choose between US (api.harvey.ai), EU (eu.api.harvey.ai) and AU (au.api.harvey.ai).
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Harvey tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
audit_logs | Immutable audit trail of every action taken in the Harvey workspace - logins, admin changes, user activity, and API access. | Append only, Full refresh | timestamp | — |
usage_history | Only syncs the last year on initial sync (Harvey API limit) | Incremental, Full refresh | utc_time | — |
query_history | Only syncs the last year on initial sync (Harvey API limit) | Incremental, Full refresh | utc_time | — |
client_matters | Full refresh only | Full refresh | — | — |
vault_projects | Full refresh only | Full refresh | — | — |
vault_project_users | Full refresh only | Full refresh | — | — |
vault_project_files | Full refresh only | Full refresh | — | — |
review_tables | Full refresh only | Full refresh | — | — |
review_table_rows | Full refresh only. Makes one request per file in each review table | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.