Linking Concord as a source
This source is currently in alpha. The interface and available tables may change.
The Concord connector pulls your contract lifecycle data into the PostHog Data warehouse, so you can analyze your contracts alongside your product data.
Prerequisites
You need a Concord account on a paid plan so you can generate an API key.
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.
When linking Concord, you'll need:
- API key – generate one in your Concord account settings (API key generation requires a paid plan). Concord sends it as an
X-API-KEYheader. - Environment – choose Production or Sandbox to match the Concord environment your API key belongs to.
- Organization ID – optional. Leave it blank to use the first organization your API key can access.
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.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Environment | select | Yes |
Organization ID | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
organizations | Organizations (companies/workspaces) the API key can access. | Full refresh | — | — |
agreements | Contracts and templates in the organization, with stage, parties, tags and key dates. | Incremental, Full refresh | modifiedAt, createdAt | — |
members | Members of the organization, including their role and group memberships. | Full refresh | — | — |
groups | User groups (teams) defined in the organization. | Full refresh | — | — |
folders | Folder tree of the organization, flattened to one row per folder. | Full refresh | — | — |
clauses | Active clauses in the organization's clause library. | Full refresh | — | — |
tags | Tags defined in the organization for classifying agreements. | Full refresh | — | — |
reports | Saved reports in the organization. | Full refresh | — | — |
approvals | Company-level approval workflows configured in the organization. | Full refresh | — | — |
events | Organization audit log. Requires the Administrator role. Append only. | Incremental, Full refresh | createdAt | — |
Troubleshooting
- If you see an authentication error, your API key may be invalid or revoked. Generate a new key in your Concord account settings, then reconnect.
- If a table fails with a permission error, your key may be missing the required access. The events log requires the Administrator role. Adjust the key's access, then reconnect.
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.