.png)
OysterHR has no native connector in the Rippling App Shop — but a custom integration is possible, and thePeopleStack has built one in production. Sync PTO, leave data, and employee lifecycle events between Oyster and Rippling without manual handoffs.
Because there is no App Shop connector, the integration starts with a scoping conversation: what data needs to flow between Oyster and Rippling, in which direction, and at what frequency? For most clients, the priority syncs are PTO and leave events (Oyster → Rippling and Google Calendar) and employee lifecycle events (hire, termination, role change in Oyster → IT provisioning triggers in Rippling).
We design the connector architecture based on those requirements, build it using Oyster's API and Rippling's REST API, and deploy it to a hosted environment (Vercel or equivalent) with logging, error handling, and RBAC. We obtain Rippling's confirmation that the private integration is approved before go-live — a step that matters given the competitive sensitivity between the two platforms.
Before deploying to production, we test the connector against a staging environment, validate every sync event, and document the integration for the client's engineering team so it can be maintained independently after handoff.
OysterHR is particularly relevant for US and Canadian companies with EOR workers distributed across EMEA, APAC, and Latin America. For US companies, the most common scenario is running Rippling for domestic employees and IT, while Oyster manages EOR workers in countries outside Rippling's native entity coverage. For Canadian companies in the same position, Rippling handles Canadian payroll natively while Oyster covers ROW EOR. The critical gap in both cases is IT provisioning — Oyster workers need app access and devices managed through Rippling, but the lack of a native connector means this sync requires a custom-built solution.
No. OysterHR cannot be listed in the Rippling App Shop due to Oyster's competitive positioning relative to Rippling in the EOR market. Rippling's App Shop Director has confirmed that the connector cannot be published publicly. Any integration between Oyster and Rippling must be built as a private custom integration — deployed and hosted outside the App Shop. thePeopleStack has designed and built exactly this type of connector for a production client.
The most operationally impactful sync is PTO and leave data. Oyster manages leave approvals for EOR workers, but those leave events need to be visible in Rippling for IT workflows, calendar management, and manager visibility. Without a connector, HR teams are manually updating Rippling with Oyster leave data — which breaks down quickly as EOR headcount grows. A secondary sync is employee status and lifecycle events: hires, terminations, and role changes in Oyster need to trigger IT provisioning and deprovisioning in Rippling to avoid access gaps and orphaned accounts.
thePeopleStack designed and built a custom Oyster-to-Rippling connector for a production client with approximately 20 EOR workers on Oyster across multiple countries. The connector syncs PTO and leave events from Oyster to Rippling, and surfaces those leave events in Google Calendar for employee and manager visibility. It is deployed on Vercel with logging, role-based access control, and error handling. Rippling's App Shop Director confirmed the integration could not be listed publicly but approved it as a private integration for the client's use.
The Vercel-deployed connector we built uses Oyster's API to poll for leave and PTO events, then pushes those events to Rippling via Rippling's REST API and to Google Calendar via the Calendar API. The connector runs on a scheduled trigger, includes error logging and retry logic, and uses RBAC to control which Rippling and Google accounts have access. The architecture is straightforward but requires custom development work — there is no off-the-shelf connector available.
Yes — this is one of the few Rippling integrations where thePeopleStack has direct production experience that no off-the-shelf connector can replicate. We designed and built the connector architecture, obtained Rippling App Shop Director approval for the private integration, and deployed it to production. If your organization runs Oyster for EOR and Rippling for domestic HR and IT, we can scope and build a private connector tailored to your specific sync requirements.
