> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Churnkey as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/churnkey > **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) ![](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 Churnkey connector pulls your cancel-flow session data into the PostHog Data warehouse, so you can analyze churn, retention, and cancellation behavior alongside your product data. ## Prerequisites You need a Churnkey account and a Data API key. The Data API key is distinct from your Cancel Flow API key and is requested from Churnkey support at [support@churnkey.co](mailto:support@churnkey.co). ## 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 Churnkey, you'll need: - **Data API key** – request one from [support@churnkey.co](mailto:support@churnkey.co). This is distinct from your Cancel Flow API key. Once issued, it is shown in Churnkey under **Settings → Account**. - **App ID** – shown in Churnkey under **Settings → Account**. ## 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. This source is full refresh only. ## Configuration | Option | Type | Required | | --- | --- | --- | | `Data API key` | password | Yes | | `App ID` | text | Yes | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `Sessions` | A single cancel-flow session: one customer's pass through Churnkey's cancellation flow, including the offers presented, what they accepted, and the eventual outcome. | Full refresh | — | \_id | ## Troubleshooting - If you see an authentication error, check your Data API key and App ID under **Settings → Account**, then reconnect. - If you see a forbidden error, confirm you are using a Data API key and not a Cancel Flow key, then reconnect. - If your App ID is not recognized, check the App ID under **Settings → Account**, 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.