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

# Linking Gainsight CS as a source

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

> **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)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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 Gainsight CS connector syncs your customer success data into the PostHog Data warehouse: companies, people, relationships, timeline activities, CTAs, and success plans. You can then join account health and CSM activity to how those accounts actually use your product.

This is the connector for **Gainsight CS** (also sold as Gainsight NXT). Gainsight PX, the product experience tool, is a separate connector.

## Prerequisites

You need a Gainsight admin to generate an access key for your tenant. The key inherits the permissions of the admin who created it, and it doesn't expire.

## 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 Gainsight CS, you'll need:

-   **Gainsight domain** – the host you reach Gainsight on, for example `acme.gainsightcloud.com`. If your team uses a custom domain, enter that instead.
-   **Access key** – generate one in Gainsight under **Administration → Connectors**, on the **Gainsight API** tab.
-   **Custom objects** (optional) – a comma-separated list of extra object names to sync, for example `health_score__gc, renewal_forecast__gc`. Find the exact names on the Gainsight **Data Management** page.

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

Every Gainsight CS object is full refresh. The Read API documents a `where` clause with date operators, but its behavior alongside paging isn't verified, so the connector re-reads each object rather than risk skipping records on an incremental sync.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Gainsight domain` | text | Yes |
| `Access key` | password | Yes |
| `Custom objects (optional)` | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `company` | Customer companies tracked in Gainsight CS, the root object most other records hang off. | Full refresh | — | — |
| `company_person` | Links a person to a company — the external contacts associated with a customer company. | Full refresh | — | — |
| `relationship` | Relationship records, which track a distinct engagement, product, or team within a company separately from the company itself. | Full refresh | — | — |
| `relationship_person` | Links a person to a relationship — the external contacts associated with a relationship. | Full refresh | — | — |
| `gsuser` | Gainsight internal users, including the customer success managers assigned to companies. | Full refresh | — | — |
| `activity_timeline` | Timeline activities — the logged calls, meetings, emails, and updates recorded against a company or relationship. | Full refresh | — | — |
| `call_to_action` | Calls to Action (CTAs) — the tasks and risks raised against companies and relationships. | Full refresh | — | — |
| `cta_group` | Success Plans, which group related Calls to Action toward a customer objective. | Full refresh | — | — |
| `email_logs` | Log of emails sent from Gainsight. | Full refresh | — | — |
| `cta_configuration` | Company and global CTA picklist values: the types, statuses, priorities, and reasons a Call to Action can take. | Full refresh | — | — |
| `cta_task` | Tasks attached to Calls to Action, with their owners, due dates, and completion state. | Full refresh | — | — |

Each table's columns are discovered from your tenant, so any custom fields you've added to a standard object are synced along with the built-in ones. Date and datetime columns are converted from Gainsight's epoch-millisecond format to timestamps.

## Troubleshooting

-   If you see a **401** or **403** error, the access key is invalid, has been revoked, or belongs to an admin without access to the object. Generate a new key under **Administration → Connectors**, then reconnect.
-   If a table fails with **no fields for object**, the object name doesn't exist on your tenant or the key can't read it. Check the name on the **Data Management** page. Custom objects end in `__gc`.
-   If the domain is rejected, enter just the host (`acme.gainsightcloud.com`) rather than a full URL with a path.

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.