Greenhouse DSR integration

Missing an action you need, or an integration we don't support yet? Contact your Customer Success Manager.

This integration automates privacy requests for candidates in your Greenhouse account. MineOS looks up the Greenhouse candidate that matches the requester's email address, then lets you preview, anonymize or copy the candidate record. This helps you meet deadlines for access and erasure requests under regulations such as GDPR (Articles 15 and 17) and CCPA.

To scan Greenhouse for personal data, see Greenhouse data classification integration.

Choose the right integration type

⚠️

Move to Greenhouse v3

If you see the error "Harvest V1 and V2 are no longer available for this organization," your requests are running on the deprecated Greenhouse integration type. Set up Greenhouse v3 below, then replace the original integration in your privacy request workflows.

How It Works

• Preview: before MineOS anonymizes or copies anything, you can preview the candidate it found for the requester.
• Anonymize: deletion requests anonymize the candidate record in Greenhouse instead of removing it. If no candidate matches, the task is reported as not found.
• Get a copy: MineOS sends the requester a copy of their Greenhouse candidate record.

Greenhouse v3

Before You Start

• Make sure your MineOS plan supports automatic integrations.
• Only a Greenhouse admin can create Harvest v3 credentials. Ask your admin to create them, or make sure you have permission to create API credentials.

Setting Up

Step 1: Add the integration in MineOS

1. Log in to MineOS. On the left sidebar, click Inventory → Add data source. Search for Greenhouse and click Add. If Greenhouse is already in your inventory, skip this step.
2. In Inventory, open Greenhouse and go to the DSR & integrations tab.
3. If you already have a Greenhouse integration, click Add instance.
4. Under Action for fulfilling requests, select Integration.
5. In the Integration Type dropdown, select Greenhouse v3. Don't select Greenhouse, which is the deprecated version.
6. Click Set up integration to open the setup wizard.

Step 2: Get Harvest v3 credentials from your Greenhouse admin

Ask your Greenhouse admin to:

1. In Greenhouse, click the gear icon (Configure), then go to Dev Center → API Credential Management.
2. Click Create New API Credentials.
3. For the API type, select Harvest v3 (OAuth).
4. Under permissions, enable only GET Candidates (List Candidates) and PATCH Anonymize Candidates. Limiting the credentials to these two permissions keeps their risk low.
5. Save, then click I have stored the client credentials to reveal the Client ID and Client Secret.

📘

Keep your credentials safe

Greenhouse shows the Client Secret only once, so copy it right away. Share it through a password manager or secure share, not regular email or chat.

Step 3: Complete the setup wizard

1. Enter the Greenhouse Client ID and Greenhouse Client Secret. All other settings are preconfigured.
2. Click Finish to activate the integration.

Test the connection

Send a Preview, Get a copy or Delete test request for a candidate email address that exists in Greenhouse, and check that it succeeds.

Greenhouse (deprecated)

The original Greenhouse integration type connected with a Harvest API key over Harvest v1/v2. Greenhouse has retired those API versions, so this type can no longer connect, and requests that use it fail with "Harvest V1 and V2 are no longer available for this organization."

If you still have it set up:

1. Set up Greenhouse v3 using the steps above. Greenhouse v3 needs new credentials (Client ID and Client Secret); your old API key won't work.
2. Add Greenhouse v3 to every workflow that uses the original Greenhouse integration.
3. Remove the original Greenhouse integration from those workflows, so each request runs on Greenhouse v3 only.

Using the Integration in Requests

To handle requests automatically, add the Greenhouse v3 integration to the workflows of each privacy right it should handle, for example access, erasure and portability.

Troubleshooting

• "Harvest V1 and V2 are no longer available for this organization": the request ran on the deprecated Greenhouse integration type. Add Greenhouse v3 to the workflow and remove the original integration.
• Requests fail on Greenhouse v3: the most common cause is an incorrect Client ID or Client Secret. Check both with your Greenhouse admin.
• Deletion requests fail but access requests succeed: check that the credentials include the PATCH Anonymize Candidates permission.

Need Help?

If you need any help with this integration, please contact your Customer Success Manager. They will be happy to assist you!