> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/hris/gusto.md).

# Gusto

Connect Gusto to Siit to sync your US workforce — employees and contractors — and use Gusto's lifecycle events to drive onboarding and offboarding workflows.

### What you get

* **Live People directory** — Gusto employees and contractors appear in Siit with role, department, manager, and worker type.
* **Lifecycle triggers** — Start date, Termination date, and Birthday flow into Siit as workflow triggers.
* **Manager resolution** — Gusto's reporting structure powers auto‑selected approvers.
* **Employee + contractor coverage** — both worker types sync, with the type preserved as a Siit attribute.

### What syncs from Gusto

| Category        | Fields                                                         |
| --------------- | -------------------------------------------------------------- |
| Identity        | First name, last name, preferred name, work email, employee ID |
| Role            | Job title, department                                          |
| Org structure   | Manager, work location, company / legal entity                 |
| Employment      | Worker type (Employee / Contractor), status                    |
| Lifecycle dates | Start date, termination date, date of birth                    |

Work email is the canonical identifier. Compensation, payroll, tax, and benefits data are not synced into Siit.

### Before you connect

* A Gusto admin account with permission to authorize third‑party apps.
* Work email populated on every active worker. Gusto sometimes leaves this blank for contractors — fill it in first.

### Connect Gusto

1. In Siit, go to **Settings → Workspace → Integration library**, find **Gusto** in the HRIS section, and click **Connect**. You'll be redirected to Gusto.
2. Sign in with your Gusto admin account.
3. Approve the requested read scopes (employees, contractors, departments, locations, jobs).
4. Gusto redirects you back to Siit, which runs an initial import.
5. Review field mapping (including Worker Type → Employment Type) and click **Finish setup**.

Need a more detailed walkthrough? Reach out to support via the in‑app chat.

> **Tip** — If your Gusto admin policy restricts third‑party app installs, ask your account owner to approve Siit before running the connection flow.

### After the connection

* Confirm your **People list** matches Gusto's active workforce.
* In **Settings → Context management → People fields**, set Gusto as the source of truth for HR‑owned fields if you're also connected to an IdP.
* Most Gusto customers start with offboarding automation driven by termination date.

### Sync frequency

Gusto data refreshes automatically every few hours.

### Common workflows

**Day‑1 onboarding.** *Trigger: Start date. Actions: create IdP account, assign apps by department, ship equipment if Worker Type = Employee, DM manager.*

**Offboarding on termination.** *Trigger: Termination date. Actions: revoke sessions, remove app access, equipment pickup, notify manager.*

**Contractor onboarding.** *Trigger: Start date, Condition: Worker Type = Contractor. Actions: create limited IdP account, contractor app bundle only.*

### Troubleshooting

**Workers missing.** Only active workers and upcoming hires sync by default. Confirm status and work email in Gusto.

**Contractor vs employee mis‑labeled.** Open **Settings → Workspace → Integration library → Gusto → Mapping** and check Worker Type → Employment Type.

**Manager field empty.** In Gusto, confirm the worker has a reporting manager set on their profile.

**Connection shows "needs reauthorization".** OAuth tokens can be revoked or expire. Reconnect from **Settings → Workspace → Integration library → Gusto**.

**Multi‑company Gusto setups.** If you manage multiple companies in Gusto, reach out via in‑app chat — we'll confirm the right setup for your tenant.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/integrations/hris/gusto.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.