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

# Linking Drip as a source

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

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

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](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

Enter your Drip API token and account ID to pull your Drip email marketing data – subscribers, campaigns, broadcasts, workflows, forms, and goals – into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Drip.
3.  Next, gather your Drip credentials:
    -   **API token** – found in Drip under **Settings → User Settings → API**.
    -   **Account ID** – found under **Settings → Account → General Info** (it's the numeric ID in your Drip dashboard URL).
4.  Back in PostHog, enter the credentials and click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Drip data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `subscribers` | Subscribers in your Drip account | Full refresh |
| `campaigns` | Email campaigns | Full refresh |
| `broadcasts` | One-off broadcast emails | Full refresh |
| `workflows` | Automation workflows | Full refresh |
| `forms` | Signup forms | Full refresh |
| `goals` | Conversion goals | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

All Drip tables are full refresh only. Drip's only documented server-side timestamp filter is `subscribed_after` on subscribers, which filters on subscription date and would silently miss updates to existing records, so it isn't used as an incremental cursor.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |
| `Account ID` | text | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `subscribers` | A person on a Drip account's email list, with their contact details and engagement state. | Full refresh | — | — |
| `campaigns` | An email series (drip campaign) that subscribers are enrolled into. | Full refresh | — | — |
| `campaign_subscribers` | Membership of an email series campaign: one row per subscriber per campaign, across active, unsubscribed and removed statuses. | Full refresh | — | — |
| `broadcasts` | A one-time email blast sent to a segment of subscribers. | Full refresh | — | — |
| `workflows` | An automation workflow that moves subscribers through a series of triggers and actions. | Full refresh | — | — |
| `forms` | A signup form used to capture new subscribers into the account. | Full refresh | — | — |
| `goals` | A conversion goal that tracks when subscribers complete a defined action. | Full refresh | — | — |
| `tags` | Every tag used in the account. Tags are the labels Drip segmentation and automation trigger on. | Full refresh | — | — |
| `custom_field_identifiers` | Every active custom field key used on subscriber records in the account. | Full refresh | — | — |