Provision new employees into an identity provider via SCIM triggered by HRIS hire events using the Rippling SCIM integration framework
domain: developer.rippling.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register your application in the Rippling App Shop and configure SCIM 2.0 endpoint URL and bearer token for inbound provisioning
Implement the SCIM /Users POST handler to create user accounts in your IdP when Rippling POSTs a new hire provisioning event
Map Rippling SCIM user attributes (userName, name, emails, phoneNumbers, title, department) to your IdP's user schema
Implement /Users PATCH with SCIM replace operations to handle employee profile updates such as manager changes, role changes, and location transfers
Implement /Users DELETE or active:false PATCH to deprovision access when Rippling sends a termination event
Known gotchas
Rippling SCIM provisioning is push-only from Rippling to your app; you cannot pull SCIM data from Rippling on demand without a separate API call
Rippling may retry failed SCIM requests; your endpoint must be idempotent and handle duplicate POSTs for the same externalId without creating duplicate users
Custom attributes beyond the SCIM core schema require Rippling's custom attribute mapping feature, which must be configured in the App Shop developer console before they appear in payloads
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?