--- title: Greenhouse Field Mappers slug: greenhouse-field-mappers docTags: createdAt: 2022-10-17T16:35:52.000Z --- # Built in field mappers ### Mapped job data between ChartHop and Greenhouse The following fields are used during an inbound or outbound job data flow: | **ChartHop field** | **Greenhouse field** | | ------------------ | ------------------------------------------------------------------------------------ | | req | opening.opening\_id | | recruit | opening.status | | createdate | opening.opened\_at | | title | job.name | | employment | job.custom\_fields.employment\_type | | department | job.departments | | location | job.offices | | hiremgr | job.hiring\_team.hiring\_managers\[0].id, job.hiring\_team.hiring\_managers\[0].name | | recruiter | job.hiring\_team.recruiters\[0].id, job.hiring\_team.recruiters\[0].name | ### Mapped new hire data from New Hire Webhook The following fields are used during a new hire webhook data flow: | **ChartHop field** | **Greenhouse field** | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | name.first | candidate.first\_name | | name.last | candidate.last\_name | | contact.homeemail | candidate.email\_addresses\[?(@.type == 'personal' \|\| @.type == 'other')].value.first() | | contact.workemail | candidate.email\_addresses\[?(@.type == 'work')].value.first() | | contact.mobilephone | candidate.phone\_numbers\[0].value | | startdate | offer.starts\_at | | currency | offer.custom\_fields.salary.unit | | base | offer.custom\_fields.salary.value, offer.custom\_fields.salary | | variable | offer.custom\_fields.bonus.value, offer.custom\_fields.bonus, offer.custom\_fields.variable\_compensation.value, offer.custom\_fields.variable\_compensation, offer.custom\_fields.variable.value, offer.custom\_fields.variable | | grantshares | offer.custom\_fields.stock\_option.value, offer.custom\_fields.stock\_option, offer.custom\_fields.equity.value, offer.custom\_fields.equity | | userid | user.id | | name | user.name | | email | user.primary\_email\_address | :::hint{type="info"} You must include the country code as a part of any international number for it to be recognized as such within ChartHop. When you are syncing phone numbers from an external system, such as a payroll system or ATS, be sure the country code is included in the phone number that is listed in the external system. This also applies when updating data through a spreadsheet. ::: # Custom field mappers Custom field mappers can be used to map additional custom fields between Greenhouse and ChartHop.  :::hint{type="info"} You can use custom field mappers to override the default field mappings. For example, you can pull a custom field into a ChartHop default field. Similarly, you can disable default field mappers. For more information about managing custom fields, please contact your ChartHop implementation specialist. ::: ![You can use custom field mappers to override the default field mappings.](https://api.archbee.com/api/optimize/CXAjUAezd9VEEVQBIYmdw/wj9HjHXzgilrk5LQarspy_group-25.png "You can use custom field mappers to override the default field mappings.") To create a custom field mapper, follow these steps: 1. In ChartHop, from the left sidebar, select **Apps & Bundles**. 2. From the sub-menu, select **Apps**. 3. Select the **Installed Apps** tab. 4. Scroll the list down to the **Greenhouse** app. 5. Select the **Greenhouse** app. 6. From the ChartHop **Greenhouse** app settings page, scroll down and select the **Inbound Field Mapper **page. 7. Enter your Greenhouse custom field code name under **Remote Fields**, appended with the correct endpoint. - To ensure that your Greenhouse field parses correctly, your **Remote Fields** must be preceded by the correct endpoint (job., offer., etc.), and structured as follows: - The endpoint (such as job) + custom\_fields. + your Greenhouse Immutable Field. 8. In the **ChartHop Field**, enter the field or Carrot expression you wish to map to the previously entered Greenhouse custom field. 9. (Optional) You can overwrite an existing default ChartHop field with your custom field. We recommend that you contact your ChartHop Implementation Specialist before trying this. As an example, if you wanted to map a ChartHop custom field like *targetSalary* to the Greenhouse custom field *targetBase*, then you’d want to set up your field mapper like in the image below: ![The custom ChartHop Field: targetSalary is mapped to the custom Greenhouse Remote Field: targetBase.](https://api.archbee.com/api/optimize/CXAjUAezd9VEEVQBIYmdw/MgH8s0IoC9pwgn17tnpFc_group-26-1.png "The custom ChartHop Field: targetSalary is mapped to the custom Greenhouse Remote Field: targetBase.") :::hint{type="info"} To avoid failed mappings, be sure to double-check the names of the custom fields you are using. ::: ## Set new hire announce dates When candidates are hired and they are created in ChartHop, you have a choice about when you want them to show up publically to your organization Under the option **New Hire Webhook Announce Date **select one of the following: - **Start date** - The new hire will not be org public until their start date. - **Today** - The new hire will be displayed immediately on the day of the sync - **Earlier of start date and today (Default)**