Docs / Data sources / Rippling

Rippling

Business software

Built when you ask for it

Sync Rippling employee, department, leave request, and payroll data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Rippling connector syncs your HR, IT, and finance platform data into analytics-ready tables in your data warehouse. Pull employees, departments, leave requests, and payrolls from the Rippling API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Employees
  • Departments
  • Leave requests
  • Payrolls

How it gets built

  1. Choose Rippling when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Rippling's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Rippling itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API token (Bearer). Generate the token inside your Rippling account under Tools > Developer > API Tokens.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Rippling connector?
Not as a finished connector yet. Ingest builds it from Rippling's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
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, MySQL / generic SQL and Snowflake, in an account you own.
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.

Rippling API documentation: https://developer.rippling.com

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, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Rippling