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

# Linking Pluralsight Flow as a source

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

> **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 Pluralsight Flow connector syncs users, teams, commits, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

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

Import commits, pull requests, tickets, and coding/collaboration metrics from Pluralsight Flow (formerly GitPrime). Generate an API key in Flow under Settings > API keys. Coding metrics and Collaboration metrics need the **Metrics API** permission on that key; the other tables only need the key itself.

You'll be asked for:

-   **Workspace**: the subdomain in your Flow URL, e.g. 'acme' for acme.appfireflow.com.
-   **API key**

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

All Pluralsight Flow tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Description |
| --- | --- |
| `Workspace` **Type:** text **Required:** True | The subdomain in your Flow URL, e.g. 'acme' for acme.appfireflow.com. |
| `API key` **Type:** password **Required:** True |  |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `Users` | A person tracked by Flow, aggregated from one or more git/ticket-host identities. | Incremental, Full refresh | last\_activity\_at | — |
| `Teams` | A group of Flow users, optionally nested under a parent team. | Incremental, Full refresh | created\_at | — |
| `Commits` | A raw git commit synced from an integrated repository. Does not exactly match the aggregated and filtered commit data shown in Flow reports. | Incremental, Full refresh | author\_date | — |
| `PullRequests` | An author's request to merge a set of commits into a repository branch. | Incremental, Full refresh | created\_at | — |
| `Repos` | A git repository imported into Flow from an integrated vendor. | Full refresh | — | — |
| `Tickets` | An issue filed in an integrated issue-tracking application. | Incremental, Full refresh | updated\_at | — |
| `UserAliases` | One identity (email address or user ID) under which a person shows up in an integrated vendor such as GitHub or Jira. Many aliases can merge into one apex user. | Incremental, Full refresh | created\_at | — |
| `TeamMemberships` | A relationship between a Flow user and a team. | Full refresh | — | — |
| `PullRequestProjects` | An entity that receives pull requests. Every pull request belongs to one pull request project, and a pull request project is usually bound to a repository. | Full refresh | — | — |
| `TicketProjects` | A project in an integrated issue-tracking application that contains tickets. Every ticket belongs to one ticket project. | Full refresh | — | — |
| `CodingMetrics` | Aggregate coding activity metrics (coding days, commits per day, impact, efficiency) for the requested date range. One row per sync, covering the trailing window. | Full refresh | — | — |
| `CollaborationMetrics` | Aggregate pull request collaboration metrics (time to merge, time to first comment, review thoroughness, PR count) for the requested date range. One row per sync. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

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.