# Linking Apify Dataset as a source - Docs

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

[Learn more](/wizard.md)

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

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Apify Dataset connector syncs the rows of an Apify dataset into PostHog, so you can analyze the output of your Apify Actors and web scrapers alongside your product data.

## Prerequisites

You need an Apify account with an API token that has read access to the dataset's storage, and the ID of the dataset you want to import.

## 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 Apify Dataset, you'll need:

-   **API token** – create one in your [Apify account settings](https://console.apify.com/settings/integrations). The token needs read access to the dataset's storage.
-   **Dataset ID** – find it in the [Apify Console](https://console.apify.com/storage/datasets), or use the `username~dataset-name` shorthand.

## 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](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

Apify datasets are full refresh only. The whole dataset is re-imported on every sync.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| API token | password | Yes |
| Dataset ID | text | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| dataset_items | The rows produced by the Apify dataset. Columns are defined by the Actor that produced them. Full refresh only — the whole dataset is re-imported on every sync. | Full refresh | — | — |

## Troubleshooting

-   If your API token is invalid or has expired, create a new token in your Apify account settings, then reconnect.
-   If your token cannot access the dataset, use a token with read access to the dataset's storage, then reconnect.
-   If the dataset could not be found, check that the dataset ID is correct and the token can access it.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/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.

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better