All Collections
Connecting Greenhouse & Juro - debugging errors
Connecting Greenhouse & Juro - debugging errors

Bypass any errors you may encounter when using Juro's Greenhouse integration

Sharen Gill avatar
Written by Sharen Gill
Updated over a week ago

Introduction πŸ‘‹

It can be frustrating to receive a Greenhouse error when you think everything is ready to go.

In this article, we'll look at how you can resolve some of the most common errors that you may encounter when using Greenhouse together with Juro. First, let's get a better idea of what these errors, and the individual fixes for them, are ⛑️

Common Errors 🌩️

Below, we've compiled a table of the most common errors that we've seen our customers encounter when using our Greenhouse integration. Most of them can be resolved very quickly by following the guidance for relevant errors in the Resolution column.



Template was not published

  1. Publish the Juro template

  2. Retry the contract creation from Greenhouse.

Mandatory field was left empty

  1. Go to Greenhouse

  2. Fill the data into the affected field

  3. Retry the contract creation from Greenhouse.

Incorrect field input for a choice field. (Juro will specify which field and what value it was expecting vs what it received from Greenhouse)

  1. Crosscheck the Greenhouse dropdown options for the single-select field against the choice field options within the Juro smartfield: these must be a character-for-character match, including any spacing and capitalisations

  2. Once updated, publish the template

  3. Retry the contract creation from Greenhouse.

API permissions are inaccurate

This means that API permissions are not providing sufficient access to Juro:

  1. Go to the Greenhouse Dev Centre > API Credential Management

  2. Select to edit the API key created for the Juro integration

  3. Crosscheck the permissions of this API against Step 1 of our integration guide here

  4. Click Update

  5. Refresh the browser page in Juro and check if the error persists.

The PDF did not pass back due to insufficient permissions

When a document is fully signed, Juro will pass the PDF back to the application. There are 2 reasons this may fail:

  1. If the API permissions are not set to allow us to update and add attachments to the Application: please crosscheck against Step 1 of our integration guide to ensure this is selected

  2. If Greenhouse user permissions aren't valid: Juro queries the email addresses of members added to Juro and uses one as a gateway to upload a file back to Greenhouse. If the account used is not a Greenhouse Admin, an error may occur. If this happens frequently, please speak with your Customer Success Manager.

The contract owner in Juro is incorrect

To rectify this, you'll need to confirm:

  1. That the member has been added to Juro and has completed the sign-up registration process

  2. That the member has been added to the team where the relevant Greenhouse integration is

  3. The email addresses on each platform are a character-for-character match.

Seeing errors in Juro πŸš€

Organisation Admins in Juro can view errors in each team's integration log, and see a detailed description of why the error has occurred.

To open your integration log in Juro:

  1. Go to Settings for the relevant team

  2. Select Integrations

  3. Select the Greenhouse panel

  4. Click Open Integrations log.

No errors shown πŸ˜•

If the contract did not create from Greenhouse and no errors are shown in the Juro integration log, we can troubleshoot further to find if the issue is with the API permissions, with the webhook or with the custom field:

Area to check


Step 1: Were you able to successfully complete the field mapping in the Juro template?

If yes: the API permissions are correct, you can proceed to Step 2.

If no: the API permissions are not allowing Juro to access fields and pull data through. Please reference Step 1 of our integration guide and ensure the correct permissions are selected. Once this has been completed, retry the offer creation from Greenhouse to trigger contract creation.

Step 2: Was the webhook correctly set up in Greenhouse?

  1. Check the webhook URL to ensure it is a like-for-like match, without any additional spaces (at the beginning and end of the field) or any characters missed.

  2. Check that the correct webhook event was selected for this e.g. Offer Created or Offer Approved

  3. Check the same secret key was used in Juro AND Greenhouse

If all of the above are correct, please proceed to Step 3. Otherwise, adjust the above and then retry creating the offer to trigger contract creation.

Step 3: Could there be an issue with the custom field created for template selection?

In Greenhouse, checking Dev Centre > Custom Options > Offers and the field created for the Juro template selection. Scrolling to the bottom, does the immutable field key at the bottom of this page begin with "juro_template_name" (the ending of this is flexible)?

If it doesn't, please delete this field and recreate it with the label "Juro Template Name" as this will set the correct immutable field key that will allow Juro to reference this field and use it for template creation.

πŸ’β€β™€οΈ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.

Alternatively, you can email your query to πŸš€

Did this answer your question?