Rippling
Hr
Ready to use
Rippling data, published as Rippling publishes it. Ingest delivers this data to a data warehouse you own as 8 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.
What you get
| Table | Each row is |
|---|---|
custom_fieldscustom_fields | The company's custom fields themselves, one row per field with its name, type, description and options, and no one's values (each person's values are in workers, under custom_fields). Re-read in full each run and merged on the custom field id. |
departmentsdepartments | Department list with parent linkage and hierarchy path. Re-read in full each run and merged on the department id. |
employment_typesemployment_types | Employment type catalog (label, type, compensation time period, amount worked). Re-read in full each run and merged on the employment type id. |
entitlementsentitlements | API entitlements available to the current token, with display name and description. Re-read in full each run and merged on the entitlement id. |
levelslevels | Compensation levels with rank, track and level descriptions. Re-read in full each run and merged on the level id. |
teamsteams | Teams with optional parent team. Re-read in full each run and merged on the team id. |
usersusers | Rippling user accounts linked to workers, with name, contact and locale details. Re-read in full each run and merged on the user id. |
workersworkers | One row per person per period of employment, current and terminated (a rehire gets a second row), with title, manager, department, level, start and end dates, status, and each person's custom field values in custom_fields, one item per field, which needs the workers.custom-fields.read scope. Any custom field can be hidden on its own. Re-read in full each run and merged on the worker id, so edits to existing workers are picked up. Fields the token's role or scopes do not permit come back redacted and are reported by the API under __meta.redacted_fields. |
How it works
- Choose Rippling. Connect your Rippling account once, from Ingest.
- Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 11 more, in an account you own.
- Pick a schedule. Daily is the default, and weekly and monthly are there too.
- Ingest runs it from then on. If a run fails, your dashboard shows which table and why.
Questions
- Do I need an account with Rippling?
- Yes. You connect your own Rippling account once, from Ingest, and the data comes from what that account can see.
- Which warehouses can Rippling data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL and Snowflake, in an account you own.
- How fresh is the data?
- As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 20 minutes are on the Enterprise plan.
- Will running it again create duplicate rows?
- No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference
Connector rippling, version 0.1.0, a REST source, status beta, authentication bearer.
Vendor documentation: https://developer.rippling.com
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
custom_fieldsThe company's custom fields themselves, one row per field with its name, type, description and options, and no one's values (each person's values are in workers, under custom_fields). Re-read in full each run and merged on the custom field id. | beta | full | merge | id | - |
departmentsDepartment list with parent linkage and hierarchy path. Re-read in full each run and merged on the department id. | beta | full | merge | id | - |
employment_typesEmployment type catalog (label, type, compensation time period, amount worked). Re-read in full each run and merged on the employment type id. | beta | full | merge | id | - |
entitlementsAPI entitlements available to the current token, with display name and description. Re-read in full each run and merged on the entitlement id. | beta | full | merge | id | - |
levelsCompensation levels with rank, track and level descriptions. Re-read in full each run and merged on the level id. | beta | full | merge | id | - |
teamsTeams with optional parent team. Re-read in full each run and merged on the team id. | beta | full | merge | id | - |
usersRippling user accounts linked to workers, with name, contact and locale details. Re-read in full each run and merged on the user id. | beta | full | merge | id | - |
workersOne row per person per period of employment, current and terminated (a rehire gets a second row), with title, manager, department, level, start and end dates, status, and each person's custom field values in custom_fields, one item per field, which needs the workers.custom-fields.read scope. Any custom field can be hidden on its own. Re-read in full each run and merged on the worker id, so edits to existing workers are picked up. Fields the token's role or scopes do not permit come back redacted and are reported by the API under __meta.redacted_fields. | beta | full | merge | id | - |
Where this lands, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL, Snowflake.
Get Rippling data into your warehouse
Last updated .