Linking Crisp as a source

Alpha release

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

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

The Crisp connector syncs your customer messaging data from Crisp into the PostHog data warehouse. Import conversations, contact profiles, operator details, and helpdesk content so you can join support data with your product analytics.

Prerequisites

You need a Crisp workspace with a website-tier API token. The connector authenticates with HTTP Basic using a website token – user-tier tokens aren't required.

Adding a data source

In PostHog, go to the Sources tab of the data pipeline section.
Click + New source and click Link next to this source.
Enter your credentials (see Configuration below) and click Next.
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 Crisp, you need:

Website ID – your Crisp website identifier
Token identifier – the identifier from a Crisp website token (used as the HTTP Basic username)
Token key – the key from a Crisp website token (used as the HTTP Basic password)

To get these:

Log in to your Crisp dashboard.
Go to Settings > Website Settings > Tokens.
Create a new website token following the Crisp website token guide.
Copy the website ID, token identifier, and token key into PostHog.

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 Crisp tables use full refresh. Each sync replaces the contents of the table. The Crisp API doesn't expose reliable timestamp filters for incremental sync on any table.

Conversations, people, and operators sync by default. Enable the other tables during setup or in the source settings.

Configuration

Option	Description
`Workspace UUID` Type: text Required: True	Find this in Crisp Settings > Workspace Settings > Setup Instructions.
`Token identifier` Type: password Required: True
`Token key` Type: password Required: True

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`conversations`	Support conversations in the workspace, including conversations without messages.	Full refresh	—	session_id
`messages`	Messages from each conversation, including operator notes and events.	Full refresh	—	session_id, fingerprint
`people`	Contact profiles with personal information, company information, and segments.	Full refresh	—	people_id
`people_events`	Events recorded for each contact profile.	Full refresh	—	—
`operators`	Joined operators and plugin developers in the workspace. Pending invitations are excluded.	Full refresh	—	user_id
`visitors`	Visitors on the website at the time of the sync. This table contains no visitor history.	Full refresh	—	session_id
`helpdesk_locales`	Helpdesk locales with public URLs and content counts.	Full refresh	—	locale_id
`helpdesk_articles`	Published article titles and URLs for each helpdesk locale. Article bodies and drafts are excluded.	Full refresh	—	locale, entity_id

Troubleshooting

Invalid credentials – check that your token identifier and token key belong to a website-tier token, not a user-tier token. Recreate the token if needed, then reconnect the source.
Missing campaigns – the Crisp API restricts campaign listing to user-tier tokens, so campaigns aren't available through this connector.
Empty visitors table – the visitors table only contains visitors on the website at the time of the sync. It doesn't include historical visitor data.

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.