> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Freshchat as a source Canonical URL: https://posthog.com/docs/data-pipelines/sources/freshchat > **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links). ## On this page - [Prerequisites](#prerequisites) - [Adding a data source](#adding-a-data-source) - [Sync modes](#sync-modes) - [Configuration](#configuration) - [Supported tables](#supported-tables) - [Troubleshooting](#troubleshooting) ![](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 Freshchat connector syncs agents, users, groups, and more into the PostHog data warehouse, so you can analyze them alongside your product data. ## Prerequisites Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough. ## Adding a data source 1. In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section. 2. Click **\+ New source** and click **Link** next to this source. 3. Enter your credentials (see [Configuration](#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. Enter your Freshchat account domain and API token to pull your Freshchat messaging data. Your **account domain** is the host of your Freshchat account - e.g. `acme.freshchat.com`. Use the regional API host if your account lives in a specific data center (e.g. `api.eu.freshchat.com`). Your **API token** is generated by an account admin under **Admin settings → API tokens**. It is sent as a Bearer token. You'll be asked for: - **Freshchat account domain**: for example `acme.freshchat.com`. - **API token** ## 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them. All Freshchat tables are full refresh. Each sync replaces the contents of the table. ## Configuration | Option | Type | Required | | --- | --- | --- | | `Freshchat account domain` | text | Yes | | `API token` | password | Yes | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `agents` | A team member (agent or admin) in your Freshchat account who handles conversations. | Full refresh | — | id | | `users` | An end user (contact) who has interacted with your Freshchat messaging. | Full refresh | — | id | | `groups` | A group of agents used to route and organise Freshchat conversations. | Full refresh | — | id | | `channels` | A topic (channel) that users can start a conversation under. | Full refresh | — | id | | `roles` | A role configured in your Freshchat account, resolving the role IDs carried on agents. | Full refresh | — | id | | `accounts_configuration` | Account-level Freshchat configuration for your app. | Full refresh | — | app\_id | | `user_conversations` | Links each user to the conversations they take part in. Freshchat lists conversations only per user, so this table is the way to enumerate them. | Full refresh | — | user\_id, id | | `conversation_messages` | A single message posted to a conversation by a user, agent, bot or the system. | Full refresh | — | conversation\_id, id | ## Troubleshooting - If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source. - If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source. If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.