Before you start
You need a Workday security administrator. Workday secures the Create Integration System User task with the Integration Security domain, and the Create Security Group and Activate Pending Security Policy Changes tasks with the Security Configuration domain.
You need Workday Recruiting. Metaintro connects to your tenant's Recruiting web service as an integration system user, a Workday account made only for integrations.
You will paste five things into Metaintro:
Your web services host, such as wd5-services1.myworkday.com
Your tenant name
The integration system user's user name
That user's password
The reference ID of a recruiting source named Metaintro
Create the credential in Workday
These steps follow Workday's own guides: Set Up Live Data Query ISU Authentication, Steps: Set Up Workday Integration and Set Up Domains in Security Group for Workday Integration. Those guides are written for other Workday products, but the user, group and permission tasks are the same.
Get access to the Recruiting domains that cover job requisitions and candidates, so Metaintro can list your requisitions and find existing candidates.
Put access to the Recruiting domains that cover candidates and job applications, so Metaintro can add candidates and apply them to a requisition.
Put access to Candidate Data: Attachments. Workday's Put Candidate Attachment reference requires this domain to add attachments.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose Workday Recruiting.
In Workday web services host, enter the host only, such as wd5-services1.myworkday.com. Leave out https:// and any path.
In Tenant name, enter your tenant name.
In Integration System User, enter the user name. Metaintro adds @ and your tenant name for you. If you enter the full name with @ already in it, Metaintro uses it as written.
In Integration System User password, enter the password.
In Applicant source reference ID, enter the Metaintro source's reference ID.
Select Connect.
Metaintro checks the connection by reading one job requisition. Then map your jobs, set your rules and preview before you go live.
What Metaintro sends and reads
Metaintro only sends people who chose to share their profile with you for a specific job.
Candidate. Metaintro looks for a Workday candidate with exactly the same email address. If it finds one, it uses that candidate. If not, it creates one with the person's first name, last name and email address, and adds their Metaintro proof card link as a website. It doesn't send their phone number.
Job application. The candidate is applied to the requisition you mapped, in the Review stage, with your Metaintro source. If they already have an application on that requisition, Metaintro uses it.
Résumé. When the person shared a résumé, it is attached to the job application.
Note. Workday's Recruiting web service has no notes, so Metaintro attaches a short text file to the job application. It says the person shared through Metaintro with consent, links their proof card, and includes their summary when they have one.
Jobs. Metaintro reads your job requisitions so you can map them.
Stages. Metaintro checks each application's stage and disposition in Workday regularly. Workday doesn't send updates to Metaintro.
Limits
Metaintro can't move candidates between stages. Your job application business process does that in Workday.
Stage updates come from regular checks, so they can lag behind Workday.
Every candidate needs an email address. People who shared without one aren't sent.
If your job application setup requires extra fields, Workday rejects applications from Metaintro until those fields are optional for web services.
If more than one Workday candidate has the same email address, Metaintro doesn't guess which one to use and doesn't send that person.
Workday doesn't publish rate limits. Metaintro paces its calls and waits when Workday asks it to slow down.
If something goes wrong
The user name or password is rejected. Check the user name, tenant name and host. Check that the password hasn't expired. If your tenant uses authentication policies, check that the security group may sign in with a user name and password.
Workday says the user doesn't have permission. Check the group's Get and Put permissions from step 4, then run Activate Pending Security Policy Changes again. Connecting fails if the user can't read job requisitions.
Applications are rejected. Check that the source reference ID matches your Metaintro source and that your job application doesn't require fields Metaintro doesn't send.
Workday is busy or limiting calls. Metaintro tries again later on its own. You don't need to do anything.
The password changed. Reconnect Workday in Settings > Integrations with the new password.