With HRIS Link, you can programmatically import offices and departments to sync changes from your HRIS to Greenhouse Recruiting.
To import offices / departments, you'll need to construct a RaaS (report as a service) in your HRIS that meets Greenhouse Recruiting specifications. You'll need to create standalone reports for both offices and departments if you intend to import both.
Note: HRIS Link relies on an exact match of the report column header; in most cases, you will need to update / override the default value when adding the column to your Workday report.
Report specification: Offices
Note: HRIS Link currently only supports Workday.
Use the table below to create your HRIS Link office import report. The primary business object in your report should be Location.
Once constructed, enter the report URL and your ISU credentials in HRIS Link.
Report column header |
Workday field | Greenhouse Recruiting field |
name
✓ Required field |
Location name | Office name |
external_id
✓ Required field |
Reference ID | Office external ID |
external_parent_id |
Parent Location Reference ID |
Parent office external ID See the changelog for further information about integration behavior. |
Sample report output (offices)
Once built, here’s an example of a valid report entry in SimpleXML:
<wd:Report_Data>
<wd:Report_Entry>
<wd:Name>New York City</wd:Name>
<wd:External_ID>NYC</wd:External_ID>
</wd:Report_Entry>
<wd:Report_Entry>
<wd:Name>Brooklyn</wd:Name>
<wd:External_ID>BRK</wd:External_ID>
<wd: external_parent_id>NYC</wd: external_parent_id>
</wd:Report_Entry>
<wd:Report_Entry>
<wd:Name>Los Angeles</wd:Name>
<wd:External_ID>LA</wd:External_ID>
</wd:Report_Entry>
</wd:Report_Data>
Report specification: Departments
Use the table below to create your HRIS Link office import report. The primary business object in your report may vary (such as Business unit, Cost center, etc.).
Key
- * = required field
- † = case-sensitive column header
Report column header | Workday field | Greenhouse Recruiting field |
name
✓ Required field |
HRIS Department Name (will vary) |
Department name |
external_id
✓ Required field |
Reference ID | Department external ID |
external_parent_id |
Parent Department Reference ID |
Parent department external ID See the change log for further information about integration behavior. |
Sample report output (departments)
Once built, here’s an example of a valid report entry in SimpleXML:
<wd:Report_Data>
<wd:Report_Entry>
<wd:Name>Finance</wd:Name>
<wd:External_ID>FIN</wd:External_ID>
</wd:Report_Entry>
<wd:Report_Entry>
<wd:Name>Sales</wd:Name>
<wd:External_ID>SLS</wd:External_ID>
<wd: external_parent_id></wd: external_parent_id>
</wd:Report_Entry>
<wd:Report_Entry>
<wd:Name>SDR</wd:Name>
<wd:External_ID>SDR</wd:External_ID>
<wd: external_parent_id>SLS</wd: external_parent_id>
</wd:Report_Entry>
</wd:Report_Data>
Commonly seen mapping
- Cost center / Supervisory org / Job family
Recommended filters
- Exclude inactive offices / departments