Oyster Integrations

Oyster does not publish a total integration count, and that absence is informative.

Where Deel pushes “200+ integrations” as a marketing line, Oyster lists a tighter catalogue: BambooHR, HiBob, Personio, Workday, TriNet, ADP Workforce Now on the HRIS side; Greenhouse, Ashby and BambooHR ATS for ATS; NetSuite, QuickBooks Online and Xero for accounting; Okta and Slack for identity and notifications; Carta for equity; Expensify and Concur for expense; Zapier as the catch-all. WhichPayroll’s 2025 integration audit of 17 EOR providers found Oyster’s BambooHR connection performs reliably for employee-profile sync but does not support real-time payroll-run data passing. Teams that need live payroll visibility in BambooHR must use the Oyster dashboard directly or wait for the nightly batch export.

The list is shorter than Deel pricing by an order of magnitude.

Whether that matters depends entirely on which tools your stack actually contains.

The mechanics under the catalogue follow the same event-triggered model that Remote and Deel use. A new hire created in BambooHR or accepted in Greenhouse flows into Oyster on hire.

A salary change made in Workday three months later triggers an auto-generated contract amendment in Oyster for review before it is applied.

A compensation revision needs to be entered manually in Oyster before the next payroll run, or it will not be paid. This is not a bug of Oyster specifically; it is the structural reality of EOR-to-HRIS sync in the current market.

The honest question is whether the catalogue covers your tools and whether the gaps it leaves are acceptable for your finance and people teams.

Two things make Oyster’s integration story distinct rather than a smaller copy of Deel’s. First, Carta is in the catalogue, which matters for venture-backed companies issuing options across borders and trying to keep equity administration aligned with international payroll.

Second, Oyster Embedded gives Oyster a partnership channel: SaaS vendors can embed EOR functionality into their own products.

That is not a feature most direct buyers will use, but it shapes the company’s product priorities.

For the full platform context, see the Oyster review. For shortlist comparison, see the best employer of record providers.

If your shortlist is Oyster against Remote, the integration story is close to a tie, and the decision will turn on owned-versus-partner entity coverage rather than connector depth. If it is Oyster against Deel, you are trading catalogue breadth for a tighter set with one or two distinctive entries.

If Rippling is in the picture, the comparison is no longer like-for-like, and we say so plainly below.

What tools does Oyster integrate with?

Oyster pricing catalogue groups into seven categories: HRIS, ATS, accounting, identity and SSO, expense, equity, and a Zapier bridge for everything else.

The named native connectors are BambooHR, HiBob, Personio, Workday, TriNet and ADP Workforce Now for HRIS; Greenhouse, Ashby and BambooHR ATS for ATS; NetSuite, QuickBooks Online and Xero for accounting; Okta and Slack for identity and notifications; Expensify and Concur for expense; and Carta for equity.

There is also a REST API, although the public documentation for it is thinner than Deel’s equivalent.

What is not in the catalogue is more informative than the count. There is no Lever, no Workday Recruiting, no Teamtailor on the ATS side.

There is no Rippling-style unified IT provisioning. Oyster does not publish a total native integration count on its own site; third-party reviewers cite around 19, which is modest for a vendor of Oyster’s scale.

The Zapier link covers the gaps where volume is low and tolerance for asynchronous sync is high; it does not cover them where reliability matters.

One feature that does not show up in catalogue lists but shapes Oyster’s product road map is Oyster Embedded.

This is the white-label channel through which other SaaS vendors embed Oyster’s EOR engine into their own products: a benefits platform, for example, can offer EOR hiring without building the entity network themselves.

For direct EOR buyers this is irrelevant.

For buyers evaluating an HR platform that quietly runs Oyster behind the scenes, it explains why Oyster’s connector priorities sometimes look unusual: the customer is the embedding vendor, not you.

Scenario rule: if every tool in your current stack appears in the named catalogue above, Oyster’s integration set is fit for purpose.

If even one critical tool is missing, check whether Zapier covers it acceptably before assuming a native integration is forthcoming.

How deep are Oyster’s HRIS integrations?

The five HRIS connectors share one mechanism: event-triggered sync at hire.

When a new employee is created in BambooHR, HiBob, Personio, Workday, TriNet or ADP Workforce Now and routed to Oyster, the core record flows across. For most connectors, post-hire changes do not propagate automatically. The Workday connector is an exception: salary or title changes in Workday trigger an auto-generated Oyster contract amendment for review; HiBob also syncs time-off changes.

Compensation changes, role changes, manager changes, and cost centre updates made in the HRIS after onboarding do not propagate to Oyster automatically.

They have to be re-entered in Oyster before the affected payroll runs, or the change does not happen.

This is the same model Remote uses and the same model Deel uses for its non-Deel-HR connectors. It is not a defect specific to Oyster.

The difference is that Deel offers Deel HR, a proprietary HRIS module that eliminates the external-HRIS sync problem because there is no external HRIS to sync from. Oyster has no equivalent.

If you stay on BambooHR, HiBob or Personio, you are committing to a manual reconciliation step every pay cycle for any employee whose record has changed.

For most buyers most of the time, the volume of post-onboarding compensation changes is low enough that the manual step is tolerable.

Quarterly raises affecting a known list of employees is a calendar reminder, not a process risk.

Where this becomes a problem is companies running frequent equity refreshes, mid-cycle promotions, or commission-driven role changes.

In those scenarios the manual reconciliation either becomes a payroll error source or absorbs more People Ops time than the integration was supposed to save.

For deeper context on how event-triggered sync plays out in the comparable provider, see Remote integrations.

Scenario rule: if HRIS-to-payroll changes happen monthly or less, Oyster’s HRIS sync is acceptable. If they happen weekly, plan for the reconciliation cost or look at Rippling.

Which ATS platforms connect to Oyster?

Three: Greenhouse, Ashby, and BambooHR ATS. Lever, Workday Recruiting and Teamtailor are not on the native list.

Buyers using any of those three either route hire data through Zapier, push it into the HRIS first and let the HRIS connector pick it up, or enter offer details into Oyster manually.

The Greenhouse integration itself is competent. On hire decision, the offer record flows to Oyster: candidate name, title, start date, department, and compensation if the offer was built in Greenhouse Offers.

What does not flow is everything that sits outside Greenhouse’s offer schema: right-to-work documentation, country-specific contract addenda, benefits selections, and any non-standard term negotiated in the closing process.

Those still go through Oyster’s onboarding flow manually.

Compared with Deel, which integrates Greenhouse, Lever, Ashby, Workday Recruiting and Teamtailor, Oyster’s ATS coverage is narrower. Compared with Remote, the position is similar; neither has the breadth Deel does.

The decision rule is simple: if your recruiting team has standardised on Greenhouse, Ashby, or BambooHR ATS, the gap is invisible. If you are on Lever or Workday Recruiting, you are doing manual entry, and that is a real recurring cost.

For a head-to-head on connector depth, see Deel integrations.

Scenario rule: Oyster works well for teams on Greenhouse, Ashby, or BambooHR ATS. Outside those three, treat the ATS connector as absent.

Does Oyster sync payroll data with accounting software?

Three accounting connectors: NetSuite, QuickBooks Online, and Xero. The mechanism is the same for all three: post-run, summary-level export.

After each payroll cycle closes, a summary of gross wages, taxes, and Oyster’s fees is pushed to the connected accounting system.

There is no real-time sync, no journal-level line-item mapping in the standard connector, and no per-employee cost centre breakdown confirmed for enterprise plans.

For a finance team that wants payroll expenses to reconcile cleanly to general ledger lines by department, employee, project, or cost centre, that is a meaningful gap.

The summary export hits the GL as a small number of consolidated entries that have to be reclassified manually if the finance team wants the analytical detail.

Larger companies typically build a side spreadsheet to do this reclassification each cycle, which works but is one more thing to maintain.

Rippling Payroll handles this differently and the difference is structural rather than cosmetic.

A Rippling payroll run posts journal entries with department, cost centre and employee dimensions natively, because Rippling owns the HRIS, the payroll engine, and the accounting connector and can carry the metadata across.

Oyster, like every EOR with summary-level export, posts the totals and lets you sort out the analytics later. This is the part of the comparison where the EOR model and the unified-platform model diverge.

For the unified-platform side of that argument, see Rippling integrations.

Scenario rule: if your finance team accepts a monthly reclassification step, the summary export is fine.

If month-end close depends on automatic dimensional posting, Oyster’s accounting connector is not enough on its own.

What does the Oyster API cover?

Oyster has a REST API. That is confirmed. What is less clear is what it covers in detail, because the public documentation is not as complete as Deel’s.

The endpoints we can verify support core HR record retrieval, employment status queries, and document fetching. What is not publicly documented is the webhook schema: which events fire, what payloads they carry, and how reliably they deliver. Deel publishes its webhook event list openly.

Oyster does not.

For most direct EOR buyers this gap does not bite.

The native HRIS, ATS and accounting connectors cover the volume use cases, and the buyers who would otherwise build custom workflows on top of webhooks are usually small in number.

For platform engineering teams trying to build something custom on Oyster, however, the lack of a published webhook schema is a real obstacle.

The integration is possible, but you are negotiating its details with Oyster’s solutions team rather than reading them off a page.

Oyster Embedded sits next to the API conversation but answers a different question. Embedded is for SaaS vendors offering EOR-as-a-feature inside their own products.

The pricing is separate, the contract structure is partnership rather than buyer-vendor, and the implementation is bespoke. If you are a finance ops team picking an EOR for your own employees, Embedded is not relevant.

If you are a product team at a SaaS company evaluating EOR as a build-versus-partner decision, it is one of the few options on the market and worth a separate conversation.

For the broader onboarding mechanics that the API ultimately serves, see Oyster onboarding.

Scenario rule: trust Oyster’s native integrations for standard workflows. If you need custom webhook-driven workflows, get the webhook schema from Oyster in writing before signing.

When do Oyster’s integrations fall short?

Four scenarios, in order of how often they come up in our shortlist conversations.

The first is non-native ATS. If your recruiting team is on Lever, Workday Recruiting or Teamtailor and standardisation is not on the table, every Oyster hire is a manual offer entry. Deel covers all five major ATS platforms; Oyster covers three (Greenhouse, Ashby, BambooHR ATS).

This is the most common reason a shortlist that includes Oyster narrows to Deel.

The second is journal-level accounting. Finance teams that have built their close process on dimensional GL postings will not get them from Oyster’s summary export.

They will get them from Rippling Payroll, but only by adopting the Rippling stack more broadly.

If finance has a hard requirement and HR is willing to migrate, that is a real platform decision rather than an integration tweak.

The third is partner-market reliability. Oyster operates a hybrid entity model: some markets are owned, some are partner-served. Integration sync between Oyster’s platform and the underlying payroll provider is structurally less direct in partner markets than in owned ones.

This is not officially documented, but it is implied by the architecture and worth asking about for any market that matters to you.

Remote, which uses fully owned entities, does not have this asymmetry.

For the owned-entity comparison, see Oyster alternatives.

The fourth is the absence of a proprietary HRIS.

If you do not yet have an HRIS and are weighing whether to buy one, Deel HR makes the decision easier for Deel buyers because the EOR provider doubles as the system of record.

Oyster has no equivalent. You will run an external HRIS alongside Oyster, and you will accept the event-triggered sync that comes with it.

Scenario rule: Oyster’s integration set is good enough for the BambooHR-plus-Greenhouse-plus-Xero buyer (or equivalent stack using Ashby or BambooHR ATS) with quarterly comp reviews and tolerable manual reconciliation.

Outside that profile, the gaps are real and the right answer is often a different provider.