HR & hiring · wired today
Drive Rippling with governed agents
People data is the most sensitive read an agent will ever make. The Rippling connector is one of 205 executable connectors and gives agents 13 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Rippling
| Tool | What it does |
|---|---|
get_me | Get the Rippling user the API key or access token belongs to (id, work email, company id) — the cheapest way to confirm which account and company a credential reaches |
get_current_company | Get the company this Rippling credential can access (name, primary email, phone, head office address) |
list_employees | List active employees provisioned in Rippling (name, work email, title, department, level, manager, employment type) |
list_employees_including_terminated | List Rippling employees including terminated ones (adds endDate), optionally scoped to one EIN |
get_employee | Get one Rippling employee by ID (identity, role, department, level, manager, work location, custom fields) |
list_departments | List Rippling departments for the company (id, name, parent department) |
list_teams | List Rippling teams for the company (id, name, parent team) |
list_levels | List Rippling levels, the set positions in the organization such as Manager or Executive (id, name, parent level) |
list_work_locations | List Rippling work locations for the company (id, nickname, city, state, country) |
list_leave_requests | List Rippling leave requests, optionally filtered by employee role, status, leave policy, exact leave dates or an overlapping date range |
list_company_leave_types | List the company's Rippling leave types (id, leave type, name, description, whether unpaid), optionally filtered by which system manages them |
list_leave_balances | List Rippling leave balances per employee role and company leave type (balances are in minutes) |
list_company_activity | List Rippling company activity events (who did what and when) for an audit trail, paged by cursor; the window must be within the last 90 days |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Rippling connector needs
You provide API key from your Rippling account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Rippling's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Rippling API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Rippling integration FAQ
What can Quox agents do with Rippling?
Agents can run 13 read-only tools against Rippling: get me, get current company, list employees, list employees including terminated, get employee and more. Every call is receipted in the evidence trail.
What does the Rippling integration need?
You provide API key from your Rippling account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Rippling credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Rippling connector?
This connector was blind shape-proven against the real Rippling API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.