Rippling

How it works

MuchSkills reads from Rippling on a schedule. New starters, leavers, manager changes and department changes arrive at the next sync, with no manual work on either side. Nothing is written back to Rippling.

Before you start

• A Rippling administrator on your side, or your Rippling implementation partner.
• A list of who should be in MuchSkills: everyone, or a selection by country, company, department or worker type.
• Your field names. Rippling installations name custom fields differently, so have your field list to hand for the technical session.

Steps

In Rippling

Your Rippling administrator creates an API token in Rippling's Developer app. The token reads with the permissions of the person who creates it, so the choice of owner matters. The labels come from Rippling's developer documentation. Rippling documentation

1. Check that your Rippling account has API access. You need the Developer app under Tools and the permission Create and manage API Tokens. Rippling says time off data needs the API Tier 1 entitlement. If the app or the entitlement is missing, ask your Rippling account manager.
2. Choose who owns the token. The token sees only what its owner's permission profile allows, and Rippling revokes it automatically if that person leaves. Pick a long-standing administrator whose permission profile covers the people who should be in MuchSkills, for example The entire company or a narrower group, with basic rather than sensitive employment data. A Super Admin can set up such a profile under Settings › Permissions › New Permission Profile.
3. Create the token. Go to Tools › Developer › API Tokens and select Create API token. Name it MuchSkills, give it a unique identifier and choose the latest API version.
4. Select read-only scopes. Select workers.read, users.read, departments.read, work-locations.read and employment-types.read, plus teams.read if you use teams. Add leave-requests.read only if you share absence. Do not select compensations.read or any scope ending in read-write.
5. Copy the token. Click Create and copy the token straight away: Rippling shows it only once. Rippling then emails your admins that a new token was created, which is expected.
6. Note your connection details. The API token, the base URL https://rest.ripplingapis.com, the name of the token's owner and the scopes you selected.

With MuchSkills

1. Send us the connection details. The credentials and connection details from the steps above, your field list and your scope, through a secure channel we agree.
2. Join the technical session. Your Rippling administrator and our CTO map the fields and test the connection together.
3. Check a first sync. We sync a handful of people or one department. You check their names, managers, departments and any tags in MuchSkills.
4. Widen the scope. We switch the sync on for everyone in scope. From then on it runs every 5 hours.

Check it worked

• Team/Org › Members lists the people in scope.
• The people in scope have an invitation to create their MuchSkills profile.
• Managers see their direct reports in My Circle.

What you get

• Rippling stays the source of truth. People data is entered once, in Rippling, and MuchSkills follows.
• A skills layer on your HR system. Skills, certifications and project history sit next to the people records you already trust.
• Clean data for planning. Reporting lines, departments and tags arrive ready for filtering, gap analysis and Team Builder.

Important to know

What syncs. Only name and email are required. Sync as many of the other fields as you can, because each one makes MuchSkills more useful.

Data MuchSkills does not accept. These are blocked when data arrives and never stored, even if the source includes them: age or date of birth, salary or other compensation data, performance ratings, and political, religious or health data.

Who is included. Limiting what the integration user can see in Rippling is the preferred way, so nothing outside your scope leaves your system. The fallback is a country filter in MuchSkills; records outside it are ignored and not stored. Your security or compliance team decides which fits your rules.

Leavers are deactivated, not deleted. Project history and certificates stay on record.

Our IP addresses. MuchSkills always connects from the same two addresses: 13.51.77.53 and 16.170.107.61. If Rippling or your network limits access by IP address, add both to the allow list.

Troubleshooting