> ## Documentation Index
> Fetch the complete documentation index at: https://docs.toku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rippling Worker Sync

> How Toku syncs your worker roster from Rippling

Toku keeps its roster in sync with Rippling so stablecoin elections always map to the right person. Rippling models each person's HR and employment profile as a **worker**. Sync is read-only and runs automatically after every connection and on a rolling schedule.

## Endpoint

Toku reads workers through Rippling's workers resource:

```bash theme={null}
curl "https://rest.ripplingapis.com/workers" \
  -H "Authorization: Bearer <access_token>"
```

Individual workers are readable at `GET /workers/{id}`. A trimmed, representative example response:

```json theme={null}
{
  "results": [
    {
      "id": "wrk_3f8a1c9e5b21",
      "legal_name": {
        "given_name": "Ada",
        "family_name": "Lovelace"
      },
      "preferred_name": "Ada",
      "work_email": "ada@yourcompany.com",
      "status": "ACTIVE"
    }
  ]
}
```

This is representative, not an exhaustive schema. See Rippling's reference for the full shape: [List workers](https://developer.rippling.com/documentation/rest-api/reference/list-workers) (endpoint-level details require a Rippling developer sign-in).

## What Toku Reads

| Field                                                | Purpose                                                   |
| ---------------------------------------------------- | --------------------------------------------------------- |
| `id`                                                 | Stable identifier used to match the worker across systems |
| Legal and preferred name, work email                 | Roster display and worker-portal invitations              |
| `status`                                             | Marks departed workers inactive in Toku                   |
| Compensation (via Rippling's compensations resource) | Validates election limits against pay                     |

## Sync Behavior

* **New workers** appear in Toku automatically once they exist in Rippling.
* **Updates** (name, email, compensation) flow through on the next sync.
* **Departed workers** are marked inactive and stop receiving stablecoin payments.
* A manual sync can be triggered anytime from **Settings → Payroll Integrations** in Toku.

<Note>
  Worker sync never writes to Rippling. Toku does not modify worker records, compensation, or employment state.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="Payroll Sync" icon="calendar" href="/integrations/rippling/payroll-sync">
    How Toku tracks payroll runs and pay periods
  </Card>

  <Card title="The Toku Deduction" icon="money-bill-transfer" href="/integrations/rippling/deduction">
    How the Toku line item is reflected on the pay run
  </Card>
</CardGroup>