Linking Common Room 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

The Common Room connector syncs your community and signal data – contacts, organizations, activities, website visits, segments, tags, custom objects, and more – into PostHog, so you can analyze community engagement alongside your product data.

Prerequisites

You need a Common Room account with an API token. A Common Room admin can create one under Settings > API tokens.

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.

When linking Common Room, you'll need:

  • API token – create one in your Common Room workspace under Settings > API tokens. The token grants read access to all endpoints.

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.

The activities table supports incremental syncing on the activityTime field. Each incremental sync re-reads the last 3 days of activities because they can arrive late from connected signal sources. Duplicates are merged on id.

Configuration

OptionTypeRequired
API tokenpasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
contacts

People in your Common Room workspace, with their profiles, company, lead scores, segments and tags.

Full refresh——
organizations

Companies in your Common Room workspace, with firmographics, lead scores, segments and tags.

Full refresh——
activities

Activities that Common Room collected from your connected signal sources, such as posts, comments, issues and calls.

Incremental, Full refreshactivityTime—
website_visits

Page visits that the Common Room website tracking script recorded.

Full refresh——
segments

Segments (saved lists) of contacts, organizations or custom objects.

Full refresh——
tags

Tags (labels) that can be applied to contacts, organizations, activities and custom objects.

Full refresh——
topics

Topics that Common Room detects in activity content.

Full refresh——
providers

Signal sources (integrations) connected to the workspace.

Full refresh——
custom_fields

Custom field definitions for contacts, organizations and custom objects.

Full refresh——
lead_scores

Lead score definitions of the workspace.

Full refresh——
activity_types

Activity type identifiers and their display names.

Full refresh——
activity_categories

Activity category labels of the workspace.

Full refresh——
object_types

Custom object type definitions, with their associations to other entity types.

Full refresh——
objects

Custom object records of each custom object type.

Full refresh——

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.

Still have questions?

Was this page useful?