Linking noCRM.io 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 noCRM.io connector syncs leads, activities, users, 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 noCRM.io account subdomain and API key to automatically pull your noCRM.io data.
Your subdomain is the first part of your noCRM.io URL - for acme.nocrm.io, enter acme.
You can create an API key as an account admin under Admin panel → API & Webhooks → API keys. The key is account-level and grants read access to leads, users, teams, pipelines and the other tables listed below.
You'll be asked for:
- Subdomain: for example
acme. - API key
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.
Some noCRM.io tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Subdomain | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
leads | Sales leads (opportunities) tracked in noCRM.io, including their pipeline step, status and value. | Incremental, Full refresh | updated_at | — |
activities | Activity types configured for the account, used to categorise lead activity. | Full refresh | — | — |
users | Users belonging to the noCRM.io account. | Full refresh | — | — |
teams | Teams configured in the noCRM.io account. | Full refresh | — | — |
steps | Pipeline steps (stages) a lead can move through. | Full refresh | — | — |
pipelines | Sales pipelines configured in the account. | Full refresh | — | — |
client_folders | Client folders that group leads by account/company. | Full refresh | — | — |
categories | Categories used to classify client folders. | Full refresh | — | — |
tags | Predefined tags that can be applied to leads. | Full refresh | — | — |
fields | Custom field definitions configured for leads and client folders. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key 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.