What does Rig sync from Rippling?

Workers, users, companies, departments, teams, levels, tracks, work locations, employment types, compensations, leave requests and types, schedules, shift assignments, time cards, time entries, headcount positions and priorities, job requisitions, candidates and applications.

Can I limit what Rig sees?

Yes. Each Rippling scope gates one table, and a token only sees what its owner can see. A stream whose scope you do not grant is skipped.

What happens if a field is hidden from the token owner?

It arrives empty, and Rig records it in a redacted-fields table so you can tell a hidden field from one with no data.

Does the token expire?

Rippling revokes a token unused for more than 30 days, so a scheduled sync keeps it alive. Create a new token if the connection is paused for a month.

People & operations Supported

Rippling integration for Rig

The easiest way to connect Rippling to Claude and other AI tools

Rippling is a workforce platform that brings HR, payroll, time tracking and recruiting into one system.

Try Rig Book a demo

What Rig syncs from Rippling

Once connected, Rig models these objects so questions resolve to the right tables and joins:

Workers
Users
Departments and teams
Levels and tracks
Work locations
Employment types
Compensations
Leave requests and types
Time cards and entries
Headcount positions
Job requisitions
Candidates and applications

How Rippling connects to Rig

Rig Ingest syncs Rippling into your warehouse on a schedule, with one table per API scope. You grant only the scopes you want shared, and streams without a scope are skipped.

Read the step-by-step Rippling setup guide

Report on headcount and org structure

Headcount is the count of workers by team, location and employment type at a point in time. Rig reads workers with their departments, teams, levels and work locations, so org questions resolve from one source.

Ask Rig

How many workers are in each department and location?
What is the split between employees and contractors?
Which teams have grown the most this year?

Understand leave and working time

Leave and time data show how much capacity the business really has. Rig reads leave requests, leave types, schedules, shift assignments, time cards and time entries.

Ask Rig

How much leave was taken last month by team?
Which leave types are used most?
How many hours were logged by team this week?

Track hiring against headcount plans

A headcount plan lists the positions the business intends to fill. Rig reads headcount positions and priorities beside job requisitions, candidates and applications, so open roles can be checked against plan.

Ask Rig

Which approved positions have no open requisition?
How many candidate applications does each requisition have?
Which headcount priorities are still unfilled?

Analyse compensation by level

Compensation by level shows whether pay bands match the organisation chart. When you grant the compensation scope, Rig reads compensations and joins them to workers, levels and tracks.

Ask Rig

What is the pay range at each level?
How does average compensation differ by department?
Which workers sit outside the range for their level?

Ask your Rippling data in Claude, ChatGPT or Cursor

Rig serves your Rippling data to AI assistants over MCP. Once Rippling is synced into your warehouse, you can ask questions in plain English from the tool you already use, and every answer is backed by validated, governed SQL.

Frequently asked questions

What does Rig sync from Rippling?: Workers, users, companies, departments, teams, levels, tracks, work locations, employment types, compensations, leave requests and types, schedules, shift assignments, time cards, time entries, headcount positions and priorities, job requisitions, candidates and applications.
Can I limit what Rig sees?: Yes. Each Rippling scope gates one table, and a token only sees what its owner can see. A stream whose scope you do not grant is skipped.
What happens if a field is hidden from the token owner?: It arrives empty, and Rig records it in a redacted-fields table so you can tell a hidden field from one with no data.
Does the token expire?: Rippling revokes a token unused for more than 30 days, so a scheduled sync keeps it alive. Create a new token if the connection is paused for a month.