Greenhouse Recruiting's integration with Dover allows users to track candidates through all stages of the hiring process and prevent duplicate outreach by automatically adding Dover candidates to Greenhouse and excluding candidates already in Greenhouse from Dover outreach.

Create a Harvest API key for the Greenhouse Recruiting / Dover integration

To configure the Greenhouse Recruiting / Dover integration, you'll need to create a Harvest API key.

Follow the steps in this article to create the key, and verify that the credentials and permissions below are selected.

Credentials

In the Create New Credential box, make the following selections:

  • API type: Harvest
  • Partner: Dover
  • Description: Dover Harvest API Key

Permissions

Verify that the following permissions are selected for the Dover integration:

Applications

  • Select all

Candidates

  • Select all

Note: DELETE permissions are optional.

Tags

  • Select all

Users

  • Select all

Note: DELETE permissions are optional.

Scheduled interviews

  • Select all

Activity Feed

  • Select all

Jobs

  • Select all

Note: DELETE permissions are optional.

Job stages

  • Select all

Rejection reasons

  • Select all

Sources

  • Select all

Prospect pool

  • Select all

When finished, click Save.

Your Harvest API key for the integration is created and configured to be provided to Dover in a later step.

Create a Dover source in Greenhouse Recruiting

In order to tell which candidates in Greenhouse Recruiting were added by Dover, you'll need to create a custom source for Dover.

To create a Dover custom source in Greenhouse Recruiting, click the Configure Configure icon icon on your navigation bar, then select Custom Options on the left.

Screenshot of Configure > Custom Options button

Select Sources on the left, then click Create New Source.

Select Other from the dropdown menu and enter Dover as the source.

Check out this article for more information: Add custom source.

Enable the Dover integration

Navigate to Dover > Setup > Company and select ATS Settings.

Dover integration image

Select Greenhouse from the dropdown under Which ATS do you use?

Follow the steps listed to configure your integration:

  1. Provide the correct subdomain (for instance, if your Greenhouse URL says app3.greenhouse.io, enter app3. into this field)
  2. Confirm you have created a Dover source as detailed above.
  3. Enter the Harvest API Key you created in Greenhouse Recruiting earlier.
  4. Confirm Dover has the correct permissions as detailed above

Dover integration image

Once you have completed the setup, you'll see the following confirmation screen:

Dover integration image

To set up individual jobs, navigate to Dover > Jobs and click Setup next to the job you're onboarding.

Navigate to ATS Settings and select the Greenhouse Recruiting job name and the user we should post on behalf of from the dropdown menus. The user you select must have full access to the job. Dover will use the selected user ID to add and make all edits to candidates.

Dover integration image

When finished, click Save.

Use the Dover integration on Greenhouse Recruiting

Accessing Greenhouse Recruiting from the Dover app is easy. If a candidate has been added to Greenhouse Recruiting, you'll find a link to their profile in your Greenhouse at Dover > Pipeline and on the candidate thread in Slack.

Dover integration image

By default, candidates will be added to your Greenhouse Recruiting when they are interested and you approve them in Dover. Candidates are added to the stage in your Greenhouse Recruiting that corresponds to the first stage of your interview plan, and you can select the appropriate stage during onboarding.

Note: It may take up to one hour for candidates to sync to Greenhouse Recruiting.

Once an interview has been scheduled through Dover, you'll see the event details listed under Interviews on the candidate's profile in Greenhouse Recruiting.

Dover also has the option to add all candidates that we contact as prospects. Speak with your Dover engagement manager if you're interested in this option.

Candidate exclusion

Dover won't reach out to anyone that has had any activity in Greenhouse Recruiting for the previous year, regardless of the job they were sourced for. This applies to prospects as well.

How are candidates tracked?

Dover will track candidates across stages in Greenhouse Recruiting. If a candidate stage is updated in Dover, the candidate will be moved in Greenhouse Recruiting – and vice versa.

  • Recruiter screen / Initial call → Initial Call
  • Hiring manager screen/ Technical phone screen → Pre-onsite
  • Onsite / Face-to-face → Onsite
  • Offer → Offer

If the candidate was rejected or marked as withdrew in Dover, they will be rejected in Greenhouse Recruiting.

Additional resources

Links in Dover are not working

If Dover is adding candidates to Greenhouse Recruiting but the links in Slack or Email aren't working, it means Dover is probably pointing to the wrong Greenhouse Recruiting subdomain. If this is happening, reach out to Dover Support and provide the URL you see when you login to Greenhouse Recruiting.

Examples include:

Unable to find correct job in Dover

When onboarding a new job through Dover, if the dropdown on the ATS Settings page in the Dover app is showing some results but not the one you're looking for, be sure the job is active in Greenhouse Recruiting. Dover only shows active jobs.

Note: Dover uses the internal job name from Greenhouse Recruiting. The internal job name (visible inside Greenhouse Recruiting) and external job name (shown to candidates on your job boards and careers pages) may be different.

If you have more than 100 active jobs or users, please follow the steps below to provide Dover Support with your job name and ID so they can correct the error:

To find the job ID:

Navigate to Greenhouse Recruiting and click on Jobs > select or search for your job > copy the # from the URL in your browser.

Additional help

For information or troubleshooting not covered here, reach out to support@dover.com or contact your Dover Support owner in Slack.