Troubleshooting the Greenhouse integration

This section covers a series of potential issues you may run into when setting up or configuring your Greenhouse ATS app in ChartHop, as well as their recommended solutions.

Why creating a job might fail

In case a jobs fails to be properly created, you can check for the following:

  1. Confirm that your API and Webhook credentials are correct.
  2. Confirm that your Hiring Manager and Recruiter have accounts in both ChartHop and Greenhouse with the same email address.
  3. Only Private and Standard levels are supported for Job Admins. Custom levels are not supported.
    • Also ensure that the Job Admin: Standard and Job Admin: Private levels have not been removed or renamed.
  4. Ensure that your departments and teams match between ChartHop and Greenhouse.
  5. Confirm that your Job Templates names are an exact match between ChartHop and Greenhouse.
  6. Check whether you have changed the standard required fields in Greenhouse (e.g., if you have set a non-standard default or custom field to be required for job creation)
    • If you have changed the required fields, contact support so that they may ensure that your fields get mapped and passed in correctly.

Employment Type Settings

Greenhouse comes with a set of default options for Employment types, if these need to be changed in any way, please contact support@charthop.com in order to configure them appropriately.

Why hiring might fail

In the case a hiring fails, you can check the following:

  1. Confirm that an email has been provided for the candidate
  2. Ensure that the Greenhouse Job ID field is mapped to the correct job. You can contact support@charthop.com if you need assistance with this.
  3. Be aware that we do not support internal transfers.

Harvest API key troubleshooting

If you're having trouble with Harvest API Key permissions, or believe you accidentally changed a default option, please refer to the table below for a complete list of necessary permissions.




GET: Retrieve Application

GET: List Applications


GET: Retrieve Candidate

GET: List Candidates


GET: Retrieve User

GET: List Users

GET: List User Future Job Permissions

GET: List User Job Permissions

GET: List Pending Approvals

PUT: Add a job permission


GET: List Application's Offers

GET: Retrieve Application's Current Offer

GET: Retrieve Offer

GET: List Offers


GET: Retrieve Department

GET: List Departments

POST: Create a new department

PATCH: Update a department


GET: Retrieve Job

GET: List Jobs

PATCH: Update Job

POST: Create a new job

PUT: Replace hiring team

Job posts

GET: List Job Posts

GET: Retrieve Job Post for Job

GET: List Job Posts for Job

PATCH: Update job posts

Job stages

GET: Retrieve Job Stage

GET: List Job Stages

GET: List Job Stages for Job

Job openings

GET: List Openings For a Job

POST: Create openings

DELETE: Delete openings

PATCH: Edit openings


GET: Retrieve Office

GET: List Offices

POST: Create a new office

PATCH: Update an office

User roles

GET: List user roles

If you are still unable to complete this step after attempting the troubleshooting options above, reach out to support@charthop.com.

Permissions Review

There are two access levels in ChartHop specifically designed for Recruiters

  1. Recruiting Editor: These users are allowed to view and make changes to open jobs, including target compensation levels and sensitive jobs. They are not allowed to make changes to, or access sensitive data about current employees, other than those they manage. This permission is generally intended for Recruiting roles or those managing the ATS.
  2. Recruiting View: These users are allowed to view sensitive information about open jobs only, including target compensation levels and viewing all sensitive jobs. They are not allowed to make changes to the primary timeline, or access sensitive information about current employees other than those they manage.

Other access levels with the ability to open roles: 

Primary Editor: These users are allowed to view all information, and make official, permanent changes to the primary timeline. This access should be restricted tightly and limited to a few authorized individuals in HR, Finance, or similar roles.

Owner: These users are allowed full access to everything, including the ability to change user permissions, configure integrations, and alter organization-wide settings. Because of the scope involved, this access should be tightly restricted

Updated 11 May 2022
Did this page help?