Read-only worker directory sync from Rippling, started from Rippling's own app screen.
Last verified against our product: October 4, 2026
Availability
Connect flow built; availability depends on Rippling app approval
Ask us for the current status before planning around this one.
How an admin connects it
Installed from Rippling's own screen. No API key to copy or paste.
Who can set it up: Organization admin (and a Rippling admin able to install apps).
Start the install from the Mucho Gusto app inside Rippling and approve it.
In Rippling, use Access Rules to choose which employees are provisioned to the Mucho Gusto app. Only people in that provisioned group are synced.
The first sync runs and later changes arrive by webhook as well as the daily sync.
Permissions requested
Permission or scope
What it allows
(configured in Rippling's developer portal)
Rippling fixes the app's read permissions when the app is registered, and our authorization request carries no scope parameter.
Data we read
Read
Work email
Name
Job title
Manager's work email
Start date
End date
Worker status
Not read
Compensation, bonuses or pay-related fields
Government identifiers (SSN, tax ID, passport)
Date of birth
Home address or personal phone number
Bank or benefits information
Performance reviews or time-off records
Rippling is the one directory source that can automatically invite people who are not yet members; the other directory connections only match people who already have an account.
How the data is used
Seeds and refreshes your organization's org chart: job title, department and reporting line.
Records hire and termination dates so tenure and new-hire cohorts in the Connection Score are accurate.
Matches directory people to existing members by lowercased email address. A manager you have set by hand is never overwritten by a sync.
A sync never deactivates a seat or deletes a member account. Someone who disappears from the directory is marked as terminated in the employment history only.
Rippling is the only source where people provisioned in Rippling are invited to Mucho Gusto automatically.
Sync frequency
Automatically once a day (04:00 UTC), plus on demand with the admin console's sync button. Rippling employee events (created, updated, deleted, terminated) also trigger a resync.
Disconnecting and purging data
How: Admin console, Rippling card, Disconnect, or uninstall the app in Rippling (we remove our connection when Rippling reports the company was deleted).
Our stored Rippling connection is deleted.
Nightly syncs and webhook-driven resyncs for your organization stop.
Disconnecting removes our stored connection. We do not call the vendor to revoke the grant, so also revoke Mucho Gusto's access inside the vendor's own admin settings.
What remains: Disconnecting removes the stored connection only. Org-chart entries, titles, reporting lines and employment dates already imported stay in your organization's workspace, and member accounts are not deleted. To have previously synced data removed as well, email [email protected] and we will handle it case by case; there is no self-service purge today.