Connector library

Implemented source Enterprise, ERP & HR APIs

Rippling connector.

Read Rippling companies, departments and worker metadata through four named REST v2 actions with managed bearer credentials, bounded cursor pagination and explicit field-redaction metadata.

Connector download

Download Rippling

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Package size
11 KB
SHA-256
81899cd0cfa9937291c1862bbea3478839ce3343b3a09098e7b81f99dbdf4fc4

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Read Rippling companies, departments and worker metadata through four named REST v2 actions with managed bearer credentials, bounded cursor pagination and explicit field-redaction metadata.

  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical readable HTTP scaffold.

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List companies

Read visible company names and legal-entity reference metadata.

List departments

Read visible department names, parent IDs and reference codes.

List workers

Read visible worker IDs, status, title and organization references.

Get worker

Read selected metadata for one exact worker ID.

Vendor API

API and access

Implementation considerations
  • Organization lookups: Read visible company names and department references for connected workflows.
  • Worker metadata: Look up worker IDs, status, title and organization references by exact ID or bounded list.
  • Permission-aware results: Keep known field-redaction metadata separate from unknown or empty business values.
  • Use scheduled flows for directory reads; no webhook trigger is included.
  • Select an issued API/OAuth bearer token with companies.read, departments.read or workers.read for the actions used.
  • The token owner's permission profile and token scopes limit visible rows and fields. Null fields do not establish empty business values.
  • The package pins REST v2 contract date 2024-08-01 and reads selected organization metadata; hiring, termination and payroll changes are outside its scope.

Support

Need help with Rippling?

Tell us what you need to connect or change.