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

# Linking Appcues as a source

**Alpha release**

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

![](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 Appcues connector syncs your experience settings, segments, and tags from [Appcues](https://www.appcues.com) into the PostHog [data warehouse](/docs/data-warehouse.md). Appcues is a user onboarding and product adoption platform.

## Prerequisites

You need an Appcues account with API credentials. To create them:

1.  In Appcues Studio, go to **Settings** > **Integrations** > **API Keys**.
2.  Create a new API key and give it read access to the experiences you want to sync.
3.  Copy the **API key**, **API secret**, and your **Account ID** from the account settings.

## 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 then click **Link** next to Appcues.
3.  Enter your credentials:
    -   **API key** – the API key from Appcues Studio.
    -   **API secret** – the API secret from Appcues Studio.
    -   **Account ID** – your numeric account ID from Appcues settings.
    -   **Account region** – select **United States (US)** or **European Union (EU)** depending on where your Appcues account is hosted.
4.  Click **Next**.
5.  Select the tables you want to sync, then click **Import**.

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

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |
| `API secret` | password | Yes |
| `Account ID` | text | Yes |
| `Account region` | select | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `flows` | Onboarding flows and their publication settings. | Full refresh | — | id |
| `flows_v2` | Flows 2.0 and their experience settings. | Full refresh | — | id |
| `segments` | User segments and their creation details. | Full refresh | — | id |
| `tags` | Tags used to organize experiences. | Full refresh | — | id |
| `pins` | Persistent in-app messages and their steps. | Full refresh | — | id |
| `mobile` | Mobile experiences and their steps. | Full refresh | — | id |
| `launchpads` | Launchpad experiences and their settings. | Full refresh | — | id |
| `banners` | Banner experiences and their settings. | Full refresh | — | id |
| `embeds` | Embedded experiences and their settings. | Full refresh | — | id |
| `nps` | NPS 2.0 experiences and their settings. | Full refresh | — | id |
| `checklists` | Onboarding checklists and their completion conditions. | Full refresh | — | id |

## Sync limitations

-   All tables use **full refresh** syncing. Incremental sync isn't supported because the Appcues API doesn't expose timestamp filters or pagination on its list endpoints.
-   **Event exports** aren't available. The Appcues API docs don't define the completed job result field needed to retrieve event data.
-   **User and group profiles** aren't available. The Appcues API has no list endpoints for profiles.

### Still have questions?

Ask PostHog AI

### Was this page useful?

HelpfulCould be better