Linking Arcade as a source

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.

Learn more
PostHog Wizard hedgehog

Alpha release

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

The Arcade connector syncs data from your Arcade 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:

TablesRequired permission
teams, usersUser provisioning enabled on the API key
flow_engagement, company_leadsInsights access enabled on the API key

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see 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 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 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

OptionDescription
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

TableDescriptionSync methodIncremental fieldPrimary 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——

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. If that doesn't help, contact support – we're happy to help.

Still have questions?

Was this page useful?