Linking Catchpoint Systems 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 Catchpoint Systems connector syncs your synthetic monitoring configuration data – tests, nodes, products, folders, and divisions – into PostHog, so you can analyze your monitoring setup alongside your product data.
Note: This source syncs monitoring configuration. Alert history and performance results are not included.
Prerequisites
You need a Catchpoint Systems account with an API key. To create one:
- In Catchpoint, go to Settings > Integrations > REST API.
- Click Add Consumer to generate an API key.
The key's contact permissions and client or division scope control which data the connector can access. Keys can expire or be revoked – if a sync starts failing with an authorization error, check that your key is still valid.
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 Catchpoint Systems, you'll need:
- API key – the key created in Catchpoint under Settings > Integrations > REST API > Add Consumer.
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 Catchpoint tables use full refresh because the Catchpoint API does not support server-side timestamp filters for incremental syncing. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
tests | Synthetic monitoring tests and their configuration. | Full refresh | — | — |
nodes | Monitoring nodes across all network types. | Full refresh | — | — |
products | Top-level containers that organize tests and define shared settings. | Full refresh | — | — |
folders | Folders that organize tests within products. | Full refresh | — | — |
divisions | Account divisions accessible to the API consumer. | 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 in Catchpoint under Settings > Integrations > REST API, then reconnect the source.
If a table syncs no rows, the API consumer may not have permission to access that data. Check the key's contact permissions and division scope, then try again.
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.