Greenhouse can work with Workday’s report writer to import a list of jobs you can use when creating a new position in Greenhouse. Simply generate a report of all jobs available for hire in Workday and expose the fields you’d like Greenhouse to import. You can take a look at the report format here.
How does Greenhouse adapt these values?
Please review the standard and custom field mapping sections below to understand how Greenhouse adapts Workday position and requisition values to Greenhouse jobs.
|Workday Concept||Greenhouse Equivalent Field||Required?||Notes|
|Internal_Job_Name||Internal and External Job Name||Yes||The Internal Job Name from Workday will populate both the internal and external job name values in Greenhouse. It is not possible to provide a separate External Job Name via the RaaS.|
|Level||Level||No||Maps to Level. As this is a select box, Greenhouse will attempt to look up a level setting in Greenhouse that is an exact, case-insensitive text match for the value from Workday. If it can not find one, this will be left blank. The Greenhouse default options are Entry-level, Mid-level, and Senior. To customize this, please reach out to your Greenhouse representative.|
|No_of_Openings||The number of job openings that will be created||Yes||The value must be at least 1.|
|Openings||Opening ID||No||Any number of Opening_ID elements can be placed inside of the Opening_IDs element. The No_of_Openings count should match the number of Opening_ID elements.|
|Requisition ID||Requisition ID||No||This is used to communicate back to Workday in a hired event. Also, once this Requisition ID is added to a job, Greenhouse will filter this ID out of any new job list being imported from Workday.|
|Employment_Type||Employment Type||No||Uses the same text match strategy as Level.|
|Office||Office||No||Uses the same text match strategy as Level. Only supports one office.|
Uses the same text match strategy as Level. Only supports one department.
Custom Field Mappings
Greenhouse allows you to import free-text and single-select custom fields. For free-text fields (number, long text, short text, URL, date), Greenhouse will attempt to find a Custom Field whose name exactly matches the XML element. The match will be case insensitive, and underscores will be replaced with spaces. That means the XML element <wd:Custom_Field_One> will match a custom field named Custom Field One or custom field one.
For single-select custom fields, Greenhouse will attempt to look up the custom field as described above, then look up a custom field option that exactly matches the value inside that element. When importing custom fields that include a date, please use the format MM/DD/YYYY.
Frequently Asked Questions (FAQ)
Where should this report be located?
Greenhouse can get this report from any URL.
How do I secure the report?
The report should be available on an HTTPS URL using HTTP basic authorization.
What do I have to supply Greenhouse?
Greenhouse only needs the report URL, username, and password required for access.
Can I control the order of these jobs?
Yes. Greenhouse will mirror the order of the report as it exists at the given URL, so whatever ordering you apply to the report in Workday will be reflected in Greenhouse.
Can I still use the “Start from a copy of an existing job” option?
Yes! In this case, Greenhouse will import all the relevant info from Workday like normal, but it will also copy over Greenhouse-specific fields like the interview plan, scorecard, approvals, and job post from the other job.
Am I required to select a job to import when creating a new job?
No. At the bottom of the list of jobs, you will find the option to skip the import step. Clicking this link will allow you to continue without selecting a job from Workday.
Can I search for the job I want?
Yes! In the upper left hand corner of the page, you will see a small text box that says Filter by name or req id:
This text box allows you to filter the entire list by the job name:
Or the requisition ID: