Linking RudderStack as a source

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

The RudderStack connector syncs your customer data platform configuration into PostHog, including sources, destinations, connections, transformations, tracking plans, catalog data, audit logs, and Reverse ETL syncs. Use it to analyze your RudderStack workspace alongside your product data.

Prerequisites

You need:

• A RudderStack account
• A workspace Service Access Token or Personal Access Token with read access to the resources you want to sync
• Optional: An organization Service Access Token for audit logs (requires the RudderStack Enterprise plan)

You can create tokens in the RudderStack dashboard under Settings → Access Management.

Adding a data source

1. Go to the sources tab of the data pipeline section in PostHog.
2. Click + New source and then click Link next to RudderStack.
3. Enter your Workspace access token – a workspace Service Access Token or Personal Access Token with read access to the selected resources.
4. Optional: Enter an Organization access token if you want to sync audit logs. This requires an organization Service Access Token and the RudderStack Enterprise plan.
5. Select your Region – US or EU – to match where your RudderStack account is hosted.
6. Click Next.
7. Select the tables you want to sync and configure sync frequency as needed.
8. Click Import.

Configuration

Supported tables

• sources – Event sources configured in your RudderStack workspace.
• destinations – Destinations configured to receive RudderStack events.
• connections – Connections between event sources and destinations.
• transformations – Published transformations that modify events before delivery.
• libraries – Published code libraries used in RudderStack transformations.
• tracking_plans – Tracking plans that define expected event schemas.
• catalog_events – Event definitions in the RudderStack data catalog.
• catalog_properties – Property definitions and validation rules in the data catalog.
• catalog_categories – Categories used to organize catalog events.
• audit_logs – Organization audit logs. Requires an organization Service Access Token and the Enterprise plan. Not synced by default.
• retl_connections – Reverse ETL connections that send warehouse data to destinations. Not synced by default.
• retl_syncs – Reverse ETL sync history, status, and delivery metrics for each connection. Not synced by default.

Token requirements

Most tables use the workspace access token. The audit_logs table requires a separate organization access token.

If you don't provide an organization access token, audit logs show a permission error but all other tables sync normally.

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 RudderStack tables currently use full refresh sync only. Each sync reloads the entire table from the RudderStack API.

Troubleshooting

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.