Linking OnePageCRM as a source
This source is currently in alpha. The interface and available tables may change.
The OnePageCRM connector syncs your CRM data – contacts, companies, deals, actions, notes, calls, meetings, users, statuses, and lead sources – into the PostHog Data warehouse, so you can analyze your sales pipeline alongside your product data.
Prerequisites
You need a OnePageCRM account with API access. The API key grants read access to every record your user can see.
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 OnePageCRM, you'll need:
- User ID – find it in OnePageCRM under Apps & Integrations → API.
- API key – shown in the same place as your User ID.
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.
Contacts, deals, actions, notes, calls, and meetings support incremental sync on the modified_at field. Companies, users, statuses, and lead sources are full refresh only.
Configuration
| Option | Type | Required |
|---|---|---|
User ID | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
contacts | People in the CRM — the core record actions, deals, notes, calls, and meetings hang off. | Incremental, Full refresh | modified_at | — |
companies | Organizations that contacts belong to. | Full refresh | — | — |
deals | Sales opportunities attached to contacts, tracked through pipeline stages. | Incremental, Full refresh | modified_at | — |
actions | Next actions and queued tasks assigned to users for specific contacts. | Incremental, Full refresh | modified_at | — |
notes | Notes logged against contacts, optionally linked to deals. | Incremental, Full refresh | modified_at | — |
calls | Call records logged against contacts, including results and notes. | Incremental, Full refresh | modified_at | — |
meetings | Meeting records logged against contacts. | Incremental, Full refresh | modified_at | — |
users | Users on the OnePageCRM account. | Full refresh | — | — |
statuses | Contact statuses configured on the account, with per-status contact counts. | Full refresh | — | — |
lead_sources | Lead sources configured on the account, with per-source contact counts. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your User ID or API key is invalid or has been revoked. Check both under Apps & Integrations → API in OnePageCRM, then reconnect.
- If you see a permissions error, the key is missing the access needed to sync this data. Check your OnePageCRM user's account permissions, 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.