Connect Rippling
Rippling connects from the Rippling side.- In Rippling, open the App Shop and find Pike.
- Install the Pike app and follow the prompts to connect your Pike workspace.
Import data
On the integration page, click Import data. The stepper runs entities in dependency order, so Pike reads departments before the employees who belong to them. It skips entities whose Read toggle is off, names them, and links to sync settings.What syncs
Provisioning
Rippling creates, updates, and deactivates Pike members, and maps Rippling groups to Pike teams. A deactivated member keeps their history.Send hours to payroll
When Send hours to payroll is on, approved Pike hours for hourly employees post to Rippling payroll. Only approved entries count.Time off
Approved leave from Rippling creates Pike time off of the mapped type. Defaults: vacation to Vacation, sick to Sick, parental to Parental, and other types to Vacation. That removes those hours from capacity, so allocations and utilization stay correct. Pending or rejected requests do not sync.Compensation
Sync compensation to cost profiles is off by default. Only admins and finance users can turn it on. When on, salary and pay period from Rippling set the member’s cost profile, with the effective date from Rippling.Source of truth
Once a record is linked, Rippling owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten. Rippling owns person fields.Schedule
Pike syncs with Rippling every 24 hours by default. Change the schedule in the integration settings. Import data and Refresh always run on demand.Sync settings
While Rippling is connected, the What syncs with Rippling card sits under the top button row on the integration page. Each entity has a Read toggle (Rippling to Pike) and, where supported, a Send toggle (Pike to Rippling). Toggles save immediately.
New connections start with Read on for everything and Send hours to payroll off.
Synced records
Every synced record shows the Rippling marker, “Last synced ” or “Not synced yet”, and a Refresh action. Refresh shows only while Read is on for that entity.Sync issues
Records that fail to sync appear in the Sync issues list on the integration page, with the record, the reason, and a Retry action. The integration never deletes Pike data on its own. A record removed in Rippling is marked “Removed in Rippling” in Pike, never deleted.Disconnect
Disconnecting Rippling stops syncing and keeps all imported data. Linked records keep their history.Permissions
Synced data respects Pike roles and private projects. A private project’s tasks never sync out to anyone who cannot see the project in Pike.Limits
- Salaried employees’ hours are not sent.
- Pike does not run payroll.
- Rippling connects from the Rippling App Shop, not from Pike.
Related
- Rippling integration overview: What syncs, how agencies use it, and FAQs.
- Gusto: Employees, time off, and hours to payroll.
- SCIM provisioning: Provision members from your identity provider.
- Workspace capacity: How time off and contracts set available hours.