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

# Linking tawk.to as a source - Docs

Copy page

# Linking tawk.to as a source - Docs

![](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`

[Learn more](/wizard.md)

![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

**Alpha release**

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

The tawk.to connector syncs your live chat and support data – chats with their message transcripts, tickets, properties, and property members – into the PostHog Data warehouse, so you can analyze support conversations alongside your product data.

## Prerequisites

tawk.to's REST API is available by request. Submit the [REST API Access Request Form](https://help.tawk.to/article/rest-api) and wait for approval (usually under 24 hours). Once approved, generate an API key in your tawk.to dashboard under **Edit Profile → REST API Keys**.

## 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.

When linking tawk.to, you'll need:

-   **API key** – generated under **Edit Profile → REST API Keys** in your tawk.to dashboard after your REST API access request is approved. The key needs read access to properties, chat history, tickets, and members.
-   **Property ID** (optional) – the ID of a single property to sync. Leave it blank to sync data from every property your API key can access.

## 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](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All tawk.to tables are full refresh only.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| API key | password | Yes |
| Property ID | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| properties | A tawk.to property (site) on the account, the container for widgets, chats, tickets, and members. | Full refresh | — | — |
| chats | A live-chat conversation on a property, including its message transcript. | Full refresh | — | — |
| tickets | A support ticket raised on a property, created from missed chats or the ticket form. | Full refresh | — | — |
| members | An agent who is a member of a property, with their role and status. | Full refresh | — | — |

## Troubleshooting

If the connection fails with an authentication error, check that your REST API access request was approved and that the API key is active in **Edit Profile → REST API Keys**. Keys are rejected with an `auth_error` until access is granted.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/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.

### Was this page useful?

HelpfulCould be better