Using Greenhouse to open jobs
Packages: Basic | Standard* | Premium
* Available as an add-on
In an inbound job data flow, Greenhouse open job data flows to ChartHop.
Job status migration
Greenhouse jobs/openings migrate to ChartHop if the Opening status is set to Open. As a result, any changes to open roles in ChartHop are not reflected in Greenhouse.
For example, if a mapped Greenhouse role is changed to Closed and the department is updated, the job in ChartHop updates to an Inactive status and the department in ChartHop is updated.
If multiple Hiring Managers or Recruiters are specified in Greenhouse, ChartHop takes the first one specified.
The following table describes how the Greenhouse integration handles its response to changes in a Greenhouse job and opening status. This assumes that the Greenhouse job is not yet mapped to an existing ChartHop job:
Greenhouse Job Status | Greenhouse Opening Status | ChartHop Result |
Open | Open | Created as Active |
Open | Closed | Nothing gets created |
Draft | Open | Created as Active |
Draft | Closed | Nothing gets created |
Close | Closed (open is not possible) | Nothing gets created |
It’s important to note that inbound job data flows only pull in Openings with a status of Open from your ATS into ChartHop.
Open roles must have a Hiring Manager set in Greenhouse, which will be referenced in Charthop as both the manager and hiring manager. Open roles without a manager set in Greenhouse do not migrate over. Additionally, while a recruiter is not required in Greenhouse, if a recruiter is set in Greenhouse and the recruiter does not exist in ChartHop, the jobs also do not sync over.
Job status mappings
Greenhouse communicates its hiring status to ChartHop using the following mappings:
Greenhouse Opening Status | Data flow | ChartHop Status |
Open | → | Active |
Closed | → | Inactive |
