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

# Linking Arcade as a source

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

> **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 Arcade connector syncs data from your [Arcade](https://arcade.software) interactive demo platform into the PostHog data warehouse, so you can analyze demo engagement alongside your product data.

## Prerequisites

-   An **Arcade Enterprise** workspace. API access isn't available on other plans.
-   An API key created in **Settings > Advanced** in your Arcade dashboard.
-   The API key needs different permissions depending on which tables you sync:

| Tables | Required permission |
| --- | --- |
| `teams`, `users` | **User provisioning** enabled on the API key |
| `flow_engagement`, `company_leads`, `total_plays`, `flow_views`, `flow_dropoff`, `authenticated_views` | **Insights** access enabled on the API key |

## 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.

You need the following to connect Arcade:

-   **API key** – create one in your Arcade dashboard under **Settings > Advanced**.

-   **Arcade team ID** – the ID of the team you want to sync. You can find this from Arcade's `GET /teams` API response. See the [Arcade REST API docs](https://docs.arcade.software/kb/leverage/advanced-features/rest-api) for details.

-   **Engagement start date** – a date in `YYYY-MM-DD` format. Flow engagement data syncs totals from this date through the time of each sync.

## 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.

All Arcade tables use full refresh. Each sync replaces the contents of the table. Arcade's aggregate date filters don't provide a reliable row modification cursor, so incremental syncing isn't supported.

## Configuration

| Option | Description |
| --- | --- |
| `API key` **Type:** password **Required:** True |  |
| `Arcade team ID` **Type:** text **Required:** True | Use the team ID from Arcade's GET /teams API response. |
| `Engagement start date` **Type:** text **Required:** True |  |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `teams` | Active teams and their active members in the Arcade workspace. | Full refresh | — | — |
| `users` | Active users in the Arcade workspace. | Full refresh | — | — |
| `flow_engagement` | Engagement totals for each flow during the requested period. | Full refresh | — | — |
| `company_leads` | Companies that played flows, with company details and engagement metrics. | Full refresh | — | — |
| `total_plays` | Engagement totals across every flow in the team during the requested period. | Full refresh | — | — |
| `flow_views` | Unique viewers of each flow during the requested period. | Full refresh | — | — |
| `flow_dropoff` | Step dropoff for each flow during the requested period. | Full refresh | — | — |
| `authenticated_views` | Identified viewers of each flow during the requested period, with completion status. | Full refresh | — | — |

> **Note:** The per-flow tables (`flow_views`, `flow_dropoff`, `authenticated_views`) only include flows that have engagement during the requested time window. Flows with no plays in the selected period won't appear in these tables.

## Troubleshooting

-   **Authentication error** – Arcade rejected your API key. Create a new key in **Settings > Advanced** in your Arcade dashboard, then reconnect the source.

-   **Plan error** – Arcade API access requires an Enterprise workspace. Check your plan with Arcade.

-   **Permission error for teams or users** – Enable **User provisioning** on your Arcade API key, then reconnect.

-   **Permission error for engagement data** – Enable **Insights** access on your Arcade API key, then reconnect.

-   **Rate limiting** – Arcade limits requests to 100 per minute per IP. The connector handles retries and `Retry-After` headers automatically.

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.