Integrations can be messy, which is why Merge aims to take the mystery out of them and empower our customers to seamlessly integrate their customers' system with their product! There are, however, some integrations that require a bit more insight from the Merge team or working directly with the underlying system. As such, we want to prepare our customers for what to expect when integrating, which is why we've put together this list!
Self-Serve Integrations
These are integrations you can expect your customers to be able to onboard without needing to reach out to Merge or a third-party platform.
Freshteam
Gusto
HR Cloud
HR Partner
Hibob
Humaans
Justworks
Lano
Nmbrs
Personio
Rippling
Sage HR
Sapling
Square Payroll
Zenefits
ApplicantStack
Ashby
Breezy HR
Clockwork
Comeet
Greenhouse
Homerun
JazzHR
Jobsoid
Lever
Recruitee
SmartRecruiters
TalentLyft
Teamtailor
Workable
Wrk
Integrations Requiring System Involvement
These are integrations that will require your customer to engage directly with the system provider to acquire credentials necessary to authenticate an integration.
Paylocity: Paylocity requires end users to reach out to their team directly for API key access, which we outline the steps for in this guide
TriNet: TriNet requires end users provision their client ID and secret with access to certain data directly with their team, which we explain in this guide
Recruiterflow: Recruiterflow requires end users leverage the chat button in the lower right to request an API key from their support team
Integrations with Recommended Merge Guidance
Paychex: Paychex sometimes presents issues related to permissions associated with Oauth credentials, so we made a step-by-step guide to ensure we have all the access we need
SAP SuccessFactors: SAP has a substantial number of steps to generate the necessary credentials to authenticate, so we recommend providing your end users with our guide
UKG Pro: UKG Pro is another platform with very specific permissions, which is why we have a guide to note the minimum scopes
UKG Ready: UKG Ready, like Pro, has some specific permissions, which is why we have a guide to note the minimum scopes
Workday: Workday requires adding a specific integrations user with selected permissions who will be used to authenticate the integration, which we cover in a guide
Oracle Taleo: Taleo is particular about URL format, which is https://<zone_name>.taleo.net:443/enterprise, where zone_name is included in the initial welcome email or can be obtained from Oracle support