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

# Linking Vitally as a source

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

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

- [Custom object records](#custom-object-records)
- [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 Vitally connector can link accounts, conversations, notes, tasks, and more to PostHog.

To link Vitally:

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.

2.  Click **\+ New source** and then click **Link** next to Vitally.

3.  Next, you need a secret token from Vitally. To start, click on your account logo in the top left, then **Settings**. Next, under **Operations**, select **Integrations**. Choose **Vitally REST API**, enable the integration with the toggle, and copy the secret token.

4.  Back in PostHog, paste the token in the `Secret token` field, choose your Vitally region, and add a prefix for your tables if you want. Once all this is entered, click **Save**.

5.  On the next page, set up the schemas you want to sync and modify the method and frequency as needed. Once done, click **Import**.

Once the syncs are complete, you can start using Vitally data in PostHog.

## Custom object records

In addition to the standard schemas (accounts, conversations, notes, etc.), PostHog automatically discovers any [custom objects](https://docs.vitally.io/pushing-data-to-vitally/rest-api/custom-objects) in your Vitally workspace and creates a separate schema for each one. These schemas are named `Custom_Object_<machineName>` (e.g., `Custom_Object_featureRequest`) and sync the actual records, not just the definitions.

To sync custom object records, refresh your source schemas. Each custom object appears as a toggleable schema. Once synced, the data lands in a table named `vitally_custom_object_<name>` (e.g., `vitally_custom_object_featurerequest`), which you can query directly in PostHog SQL. Incremental sync is supported via the `updatedAt` field.

> **Note:** The existing `Custom_Objects` schema still syncs custom object definitions (metadata). The new `Custom_Object_<machineName>` schemas sync the underlying records for each object.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Secret token` | password | Yes |
| `Vitally region` | select | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `Organizations` | A customer organization (company) tracked in Vitally. | Incremental, Full refresh | updated\_at | — |
| `Accounts` | A customer account in Vitally, the primary unit customer success is managed against. | Incremental, Full refresh | updated\_at | — |
| `Users` | An end user (a person at a customer account) tracked in Vitally. | Incremental, Full refresh | updated\_at | — |
| `Conversations` | A support or success conversation logged against a Vitally account or user. | Incremental, Full refresh | updated\_at | — |
| `Notes` | A note recorded against a Vitally account, user, or other object. | Incremental, Full refresh | updated\_at | — |
| `Projects` | A project (e.g. onboarding or a success plan) tracked against a Vitally account. | Incremental, Full refresh | updated\_at | — |
| `Tasks` | A task assigned to a team member in Vitally, often part of a project or playbook. | Incremental, Full refresh | updated\_at | — |
| `NPS_Responses` | An NPS (Net Promoter Score) survey response collected in Vitally. | Incremental, Full refresh | updated\_at | — |
| `Custom_Objects` | A definition of a custom object type configured in Vitally. | Incremental, Full refresh | updated\_at | — |
| `Messages` | An individual message within a Vitally conversation. | Incremental, Full refresh | conversation\_updated\_at | — |