Set up a Rippling connector

Capabilities
Gather Rippling credentials
Generate an API token
Configure the Rippling connector

Capabilities

Resource	Sync	Provision
Accounts
Teams

Gather Rippling credentials

Each setup method requires you to pass in credentials generated in Rippling. Gather these credentials before you move on.

A user with the user permissions to view all users and teams in Rippling must perform this task.

Generate an API token

In Rippling, navigate to Company Settings > API Tokens.

Give the new token a name, such as “C1”, and set the token’s unique identifier and API version.

Configure the scopes for the API token, giving it the permission to view all Rippling users and teams.

Create the token, then carefully copy and save the token value.

That’s it! Next, move on to the connector configuration instructions.

Configure the Rippling connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Rippling credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Integrations > Connectors and click Add connector.

Search for Rippling and click Add.

Choose how to set up the new Rippling connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

Find the Settings area of the page and click Edit.

Enter your token into the API token field.

Optionally, configure additional sync settings:

Expand department: Include department data in worker sync. Requires the departments.read scope.
Expand employment type: Include employment type data. Requires the employment-types.read scope.
Expand level: Include level data. Requires the levels.read scope.
Expand work locations: Include work location name and address. Requires the work-locations.read scope.
Custom fields: A list of custom field names to sync from the Rippling Workers endpoint. Only fields with names matching this list (case-insensitive) will be included in user profiles. For example, to sync scrum team data, enter Scrum Teams and Scrum Team Code. Requires the custom_fields.read scope.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Rippling connector is now pulling access data into C1.

Follow these instructions to use the Rippling connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Configure the Rippling connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Rippling connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Rippling connector deployment:

Secrets configuration

# baton-rippling-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-rippling-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Rippling credentials
  BATON_API_TOKEN: <Rippling API token>
  
  # Optional: sync specific custom fields from worker profiles
  # BATON_CUSTOM_FIELDS: "Scrum Teams,Scrum Team Code"

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-rippling.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-rippling
  labels:
    app: baton-rippling
spec:
  selector:
    matchLabels:
      app: baton-rippling
  template:
    metadata:
      labels:
        app: baton-rippling
        baton: true
        baton-app: rippling
    spec:
      containers:
      - name: baton-rippling
        image: ghcr.io/conductorone/baton-rippling:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-rippling
        envFrom:
        - secretRef:
            name: baton-rippling-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Rippling connector to. Rippling data should be found on the Entitlements and Accounts tabs.

That’s it! Your Rippling connector is now pulling access data into C1.

Set up a RingCentral connector

Set up a Rootly connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Rippling connector

Capabilities

Gather Rippling credentials

Generate an API token

Configure the Rippling connector

Resources

Step 1: Configure the Rippling connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

​Capabilities

​Gather Rippling credentials

​Generate an API token

​Configure the Rippling connector

​Resources

​Step 1: Configure the Rippling connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Rippling credentials

Generate an API token

Configure the Rippling connector

Resources

Step 1: Configure the Rippling connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector