Get out of the woods with
our BambooHR integration
The Application Object is used to represent a candidate's journey through a particular Job's recruiting process. If a Candidate applies for multiple Jobs, there will be a separate Application for each Job if the third-party integration allows it.
The Candidate object is used to represent profile information about a given Candidate. Because it is specific to a Candidate, this information stays constant across applications.
The Job object can be used to track any jobs that are currently or will be open/closed for applications.
The JobInterviewStage object is used to represent a particular recruiting stage for an Application. A given Application typically has the JobInterviewStage object represented in the current_stage field.
The Office object is used to represent an office within a company. A given Job has the Office ID in its offices field.
The Employee object is used to represent any person who has been employed by a company.
The Employment object is used to represent a job position at a company. Please note: When there is a change in pay or title, integrations with historical data will create new Employment objects while integrations without historical data will update existing ones.
The Group object is used to represent any subset of employees, such as PayGroup or Team. Employees can be in multiple Groups.
The Location object is used to represent an address that can be associated with an employee.
The Team object is used to represent a subdivision of the company, usually a department. Each employee will be grouped into one specific Team.
Stop diverting your engineers to yet another integration and let them get back to work.
Manage your simplified integration issues in a single pane. No therapist required.
Launch integrations in days, not quarters. Your sales team will thank you.
”Working with Merge’s Unified API and beautiful React component took less than a sprint to integrate, test, and release.”