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

# Linking Census as a source

**Alpha release**

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

![](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 Census (Fivetran) connector syncs your reverse-ETL workspace metadata into PostHog, including syncs, sync runs, sources, and destinations.

## Adding a data source

1.  Go to the [Data pipeline page](https://app.posthog.com/data-management/sources) and select the **Sources** tab.

2.  Click **\+ New source** and select **Census (Fivetran)** by clicking the **Link** button.

3.  Select your **Workspace region** from the dropdown:

| Label | Connects to |
| --- | --- |
| US | `app.getcensus.com` |
| EU | `app-eu.getcensus.com` |

4.  Enter your **API access token**. This comes from your Census workspace settings (see [Getting your API access token](#getting-your-api-access-token) below).

5.  Click **Next**.

6.  Select the tables you want to import, set the sync method and frequency, then click **Import**.

The data warehouse then starts syncing your Census data. You can see details and progress in the [data pipeline sources tab](https://app.posthog.com/data-management/sources).

## Getting your API access token

To connect Census to PostHog, you need a workspace API access token:

1.  Log in to your Census workspace at [app.getcensus.com](https://app.getcensus.com) (or [app-eu.getcensus.com](https://app-eu.getcensus.com) for EU).

2.  Go to **Workspace settings** > **API Access**.

3.  Click **Create new token** (or use an existing one with appropriate permissions).

4.  Copy the token – you'll need it when linking the source in PostHog.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API access token` | password | Yes |
| `Workspace region` | select | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `syncs` | A Census sync: the configuration that moves data from a source model to a destination object, including its schedule, field mappings, and alerting. | Full refresh | — | — |
| `sync_runs` | A single execution of a Census sync, including its status, timing, and per-run record counts. | Full refresh | — | — |
| `sources` | A Census data source: a connected warehouse or database Census reads records from. | Full refresh | — | — |
| `destinations` | A Census destination: a connected SaaS tool or warehouse Census writes records to. | Full refresh | — | — |
| `datasets` | A Census dataset: the SQL query against a source connection that defines the records a sync reads. | Full refresh | — | — |
| `workspaces` | A Census workspace: the container that scopes an organization's sources, destinations, and syncs. | Full refresh | — | — |

## Sync modes

All Census tables use full refresh. Census's API does not expose a server-side filter for update time, so incremental syncing is not available.

| Table | Sync method |
| --- | --- |
| `syncs` | Full refresh |
| `sync_runs` | Full refresh |
| `sources` | Full refresh |
| `destinations` | Full refresh |

**Full refresh** syncs reload all data on each run.

## Available tables

| Table | Description |
| --- | --- |
| `syncs` | Census sync configurations that move data from a source model to a destination object, including schedule, field mappings, and alerting. |
| `sync_runs` | Execution records of Census syncs, including status, timing, and per-run record counts. |
| `sources` | Data sources connected to Census – warehouses or databases that Census reads from. |
| `destinations` | Destinations connected to Census – SaaS tools or warehouses that Census writes to. |

**Sensitive fields are stripped**

The `connection_details` field is automatically removed from the `sources` and `destinations` tables. This field contains warehouse account identifiers (account name, user, warehouse name) that shouldn't be accessible to all project members.

### Still have questions?

Ask PostHog AI

### Was this page useful?

HelpfulCould be better