Overview
Security questionnaires and RFPs constantly ask about headcount, team structure, job functions, and where your people work. Connecting Rippling ties those answers to your live HR system, so they stay current automatically as your company hires, reorganizes, and opens new locations.What we sync
All data is read-only. Wolfia cannot modify, create, or delete any data in your Rippling account.- Workers – Employee profiles and employment details
- Companies – Company-level information
- Departments – Organizational department structure
- Teams – Team assignments and hierarchy
- Levels – Job levels and career ladder data
- Titles – Job title information
- Employment types – Full-time, part-time, contractor, etc.
- Work locations – Office and remote work location data
- Job functions – Functional area classifications
- Functions – Business function definitions
- Job dimensions – Additional job classification dimensions
- Worker custom fields – Employee custom fields from Data Manager
Prerequisites
Before setting up the integration, you’ll need:- Admin access to your Rippling account with the ability to manage API tokens
- A Rippling plan that supports API access
Setup instructions
Step 1: Create an API token in Rippling
Follow the instructions in the Rippling API reference to create an API token. When creating the token, give it a descriptive name (e.g.,Wolfia Integration).
Step 2: Configure API permissions
Assign the following 12 read-only scopes to the API token:| Scope | Description |
|---|---|
workers.read | Read workers data |
companies.read | Read companies data |
departments.read | Read departments data |
teams.read | Read teams data |
levels.read | Read levels data |
titles.read | Read titles data |
employment-types.read | Read employment types data |
work-locations.read | Read work locations data |
job-functions.read | Read job functions data |
functions.read | Read functions data |
job-dimensions.read | Read job dimensions data |
workers.custom-fields.read | Read custom field values for workers |
All scopes are read-only. Wolfia does not require any write permissions to your Rippling data.
Step 3: Generate and copy the token
- Review the selected scopes to ensure all 12 permissions are enabled
- Click Create to generate the API token
- Copy the token value immediately
Step 4: Configure Wolfia
Connect Rippling to Wolfia using the API token.- Log in to your Wolfia account
- Go to the Expert Assignment settings page
- Find Rippling in the list of available integrations
- Click Connect Rippling
- Paste your API token in the provided field
- Click Save to complete the integration
- Wolfia will validate the connection and begin the initial sync
What happens after setup
Once configured, Wolfia will:- Import organizational data – Sync workers, departments, teams, and other HR data from Rippling
- Continuous sync – Automatically refresh data on a recurring schedule
- Enrich context – Use Rippling data to provide more accurate, company-specific responses to security questionnaires and RFPs
Managing the integration
Viewing sync status
- Go to the Expert Assignment settings page
- Find Rippling in the connected integrations
- View last sync time, record counts, and any errors
Disconnecting Rippling
- Go to the Expert Assignment settings page and find Rippling
- Click Disconnect
- Confirm the disconnection
- Your data in Rippling remains unchanged
Security considerations
- The integration uses a scoped API token with read-only permissions
- Wolfia cannot modify, create, or delete any data in Rippling
- All data transmission is encrypted using HTTPS/TLS
- API tokens are stored encrypted at rest and never exposed in logs
- You can revoke the token at any time from Rippling’s API settings
Troubleshooting
Common issues
Connection failed- Verify the API token is correct and has not been revoked
- Ensure all 12 required scopes are assigned to the token
- Check that the relevant scopes are enabled (e.g.,
departments.readfor department data) - Verify that the data exists in your Rippling account
- Review sync logs in Wolfia for specific error messages
- Confirm the API token has not expired or been revoked in Rippling
- Re-check that all required scopes are assigned

