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

# Linking Intercom as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/intercom

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](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 Intercom connector syncs your Intercom workspace data into PostHog, including contacts, conversations, companies, tickets, activity logs, and more.

## Adding a data source

1.  Go to the [Data pipeline page](https://app.posthog.com/data-management/sources) and the **Sources** tab in PostHog.
2.  Click **\+ New source** and select Intercom.
3.  Select the Intercom workspace you want to link and click **Connect**.
4.  *Optional:* Add a prefix to your table names.
5.  Select the tables you want to import.
6.  Click **Import**.

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

## Available tables

| Table | Sync mode | Description |
| --- | --- | --- |
| admins | Full refresh | Workspace admins |
| teams | Full refresh | Teams |
| tags | Full refresh | Tags |
| segments | Full refresh | Customer segments |
| companies | Full refresh | Companies |
| company\_segments | Full refresh | Segments associated with each company |
| articles | Full refresh | Help center articles |
| company\_attributes | Full refresh | Custom company-level data attributes |
| contact\_attributes | Full refresh | Custom contact-level data attributes |
| contacts | Incremental (`updated_at`) | Contacts and leads |
| conversations | Incremental (`updated_at`) | Customer conversations |
| tickets | Incremental (`updated_at`) | Support tickets |
| activity\_logs | Incremental (`created_at`) | Admin activity logs |
| conversation\_parts | Incremental (`updated_at` via parent) | Individual messages within conversations |

## Sync modes

Intercom tables support both full refresh and incremental syncing depending on the table:

-   **Full refresh** – Re-imports all records from Intercom on every sync. Used for tables where Intercom's API doesn't support server-side filtering by timestamp (admins, teams, tags, segments, companies, company\_segments, articles, company\_attributes, contact\_attributes).

-   **Incremental** – Only imports records modified since the last sync. Available for contacts, conversations, tickets, activity\_logs, and conversation\_parts. These tables use a server-side `updated_at` or `created_at` filter, so only changed data is fetched.

When you enable incremental sync for a supported table:

1.  The first sync performs a full import to establish a baseline.
2.  Subsequent syncs only fetch records modified since the last sync.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Intercom workspace` | oauth | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `admins` | A teammate (admin) in the Intercom workspace who can reply to and manage conversations. | Full refresh | — | — |
| `teams` | A team of admins in the Intercom workspace. | Full refresh | — | — |
| `tags` | A tag used to label conversations, contacts, and companies in Intercom. | Full refresh | — | — |
| `segments` | A segment grouping contacts that match a set of conditions in Intercom. | Full refresh | — | — |
| `companies` | A company (account) in Intercom that contacts can be associated with. | Full refresh | — | — |
| `contacts` | A contact in Intercom — a user or lead you communicate with. | Incremental, Full refresh | updated\_at | — |
| `conversations` | A conversation between a contact and your team in Intercom. | Incremental, Full refresh | updated\_at | — |
| `tickets` | A ticket in Intercom tracking a customer request through to resolution. | Incremental, Full refresh | updated\_at | — |
| `articles` | A help center article in Intercom. | Full refresh | — | — |
| `activity_logs` | An entry in the admin activity log recording an action taken in the Intercom workspace. | Incremental, Full refresh | created\_at | — |
| `company_attributes` | A data attribute (built-in or custom) defined on the company model in Intercom. | Full refresh | — | — |
| `contact_attributes` | A data attribute (built-in or custom) defined on the contact model in Intercom. | Full refresh | — | — |
| `conversation_parts` | An individual part (message, note, or assignment) within an Intercom conversation. | Incremental, Full refresh | updated\_at | — |
| `help_centers` | A Help Center site in the workspace. Help Centers contain the collections that group articles. | Full refresh | — | — |
| `collections` | A Help Center collection, the top level container that groups articles. | Full refresh | — | — |
| `ticket_types` | A ticket type, defining the category and data fields captured on tickets of that type. | Full refresh | — | — |
| `ticket_states` | A ticket state, defining a stage a ticket can be in and how that stage is labelled. | Full refresh | — | — |
| `subscription_types` | A subscription type customers can opt in or out of, letting them mute non-essential messages. | Full refresh | — | — |
| `news_items` | A news item, used to announce product updates, company news, promotions, and events to customers. | Full refresh | — | — |
| `newsfeeds` | A newsfeed, the collection of news items shown to a targeted audience. | Full refresh | — | — |
| `company_segments` | The link between a company and a segment it belongs to in Intercom. | Full refresh | — | — |
| `conversation_attributes` | A custom data attribute defined on conversations, including archived ones. | Full refresh | — | — |
| `macros` | A macro (saved reply) that teammates use to answer conversations. | Incremental, Full refresh | updated\_at | — |
| `audiences` | A saved audience: rules that define which contacts a message or piece of content targets. | Full refresh | — | — |
| `content_snippets` | A content snippet: a short piece of knowledge that Fin and Copilot use to answer questions. | Full refresh | — | — |
| `contact_activities` | A contact lifecycle event in the workspace, such as a contact being created, changing role, merged, or deleted. | Full refresh | — | — |
| `deleted_contacts` | A contact that is no longer active in the workspace, with the reason it is inactive. | Full refresh | — | — |
| `folders` | A folder that organizes articles and other content into a hierarchy. | Full refresh | — | — |
| `dynamic_contents` | Reusable Help Center content with a variation per locale, and optionally per brand, that articles reference. | Full refresh | — | — |
| `conversation_hitl_events` | An event from a Fin human-in-the-loop consultation, where Fin asks a teammate before it replies in a conversation. | Incremental, Full refresh | created\_at | — |