> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Cronitor as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/cronitor

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Cronitor connector syncs your monitors, their recent job invocations, and time-series reliability metrics into the PostHog Data Warehouse, so you can analyze scheduled-job reliability, run durations, and failure trends alongside your product data.

## Prerequisites

You need a Cronitor account and an API key with the `monitor:read` scope. Cronitor creates default API keys for every account, and you can create additional scoped keys at any time.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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 Cronitor, you'll need:

-   **API key** – find or create one under **Settings → API keys** in your Cronitor account. The key needs the `monitor:read` scope.

## 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

The `monitors` and `invocations` tables have no server-side time filter in the Cronitor API, so they always sync as a full refresh. The `invocations` table is a snapshot of each monitor's most recent runs; for long-term trends, use the `metrics` table, which syncs incrementally over time windows using its `stamp` field.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `monitors` | A Cronitor monitor: a cron job, heartbeat, or uptime check, with its configuration and current read-only state. | Full refresh | — | — |
| `invocations` | Recent invocations (runs) of each job monitor, from the monitor detail's latest\_invocations. A snapshot of recent history, refreshed each sync. | Full refresh | — | — |
| `metrics` | Time-series reliability metrics per monitor, from the Metrics API. One row per monitor, dimension, and timestamp. | Incremental, Full refresh | stamp | — |
| `groups` | A group of Cronitor monitors, used to organize related monitors and to act on them together. | Full refresh | — | — |
| `issues` | An incident or maintenance event tracked in Cronitor, with its severity, lifecycle state, and the monitors and status pages it affects. | Full refresh | — | — |
| `sites` | A Real User Monitoring site, collecting web vitals, performance metrics, and JavaScript errors from a web application. | Full refresh | — | — |
| `site_errors` | JavaScript errors collected from RUM sites, grouped by error. One row per error per site. | Full refresh | — | — |

## Troubleshooting

-   If you see an authentication error, your API key is invalid or has been revoked. Create a new key in your Cronitor account's API settings, then reconnect.
-   If you see a permissions error, the key is missing the `monitor:read` scope. Update the key's scopes, then reconnect.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.