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

# Linking Gusto as a source

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

> **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 Gusto connector syncs companies, locations, employees, 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.

Pull your Gusto payroll and people data.

Company data is only readable through an authorization-code OAuth grant, so you bring your own Gusto developer app: register it in the [Gusto Developer Portal](https://dev.gusto.com), authorize it against your company as a payroll admin, then enter the app's client ID and secret along with the resulting refresh token.

Gusto rotates refresh tokens, so the token you paste here is exchanged on every sync. If syncs start failing with an authorization error, generate a fresh refresh token and update this connection.

You'll be asked for:

-   **Environment**: choose between Production and Demo.
-   **Client ID**
-   **Client secret**
-   **Refresh token**

## 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 Gusto tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Environment` | select | Yes |
| `Client ID` | text | Yes |
| `Client secret` | password | Yes |
| `Refresh token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `companies` | A company the connected Gusto account administers, with its legal identity, entity type, and current onboarding status. | Full refresh | — | — |
| `locations` | A work or mailing address belonging to a company. Employees are assigned to a work location, which drives their state and local tax jurisdiction. | Full refresh | — | — |
| `employees` | An employee of a company, with their identity, work email, onboarding status, and current jobs. | Full refresh | — | — |
| `jobs` | A job held by an employee: the title, hire date, work location, and whether it is the employee's primary job. | Full refresh | — | — |
| `contractors` | A contractor engaged by a company, either an individual or a business, with their type and start date. | Full refresh | — | — |
| `pay_schedules` | A pay schedule defining how often a company pays a group of employees, including the anchor pay period and check dates. | Full refresh | — | — |
| `payrolls` | A payroll run for a company, covering one pay period: its check date, processing state, and per-employee compensation totals. | Incremental, Full refresh | check\_date | — |
| `pay_periods` | A pay period on one of a company's pay schedules, and whether a payroll has been run for it. | Incremental, Full refresh | end\_date | — |
| `contractor_payments` | A single payment to a contractor, flattened out of Gusto's per-contractor payment grouping. | Incremental, Full refresh | date | — |
| `tax_payments` | A tax payment Gusto has made, or scheduled, to a tax agency on behalf of a company. | Full refresh | — | — |
| `departments` | A department within a company, with the employees and contractors assigned to it. | Full refresh | — | — |
| `company_benefits` | A benefit a company offers its employees, tying a Gusto-supported benefit type to the company's own offering of it. | Full refresh | — | — |
| `ach_transactions` | An ACH bank transfer Gusto made or collected for a payroll or contractor payment, with its settlement status. | Full refresh | — | — |
| `recurring_reimbursements` | An active reimbursement paid to an employee on every payroll, separate from one-off reimbursements already paid. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the client secret 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.