Three ways to integrate
Pick the depth that fits your needs — start light, grow when ready.
Outbound — skaills enriches Workday
Planned~2-3 weeks for the first connector. No Workday-side custom work if REST APIs are enabled.
Bidirectional — Workday drives, skaills executes
Planned~6-8 weeks. Requires Workday-side configuration (Studio integrations, custom fields, SAML/SCIM if SSO).
Workday Marketplace — skaills as certified partner
Roadmap9+ months including Workday certification, security review, partner-program enrollment.
What this looks like in practice
Concrete flows triggered by events in Workday.
| Trigger in Workday | What skaills does | What flows back to Workday |
|---|---|---|
| New candidate applies to a Workday Recruiting requisition | skaills generates a personalized evaluation link, sends to candidate, computes multi-dimensional score on completion | Score + competency profile + skills tags mapped to Skills Cloud appear on the candidate's Workday record |
| Manager identifies an employee for development in Workday Talent Review | skaills runs AI-Readiness + Career Path Navigator + Personal Growth Plan | Development plan, suggested paths, and learning recommendations populated in Workday Career Hub |
| CHRO launches org-transformation initiative | skaills generates Org Transformation Plan from aggregated Workday data (structure, headcount, Skills Cloud distribution, Adaptive Planning data) | CHRO-grade roadmap with capability heatmap + tracks + KPIs delivered as skaills dashboard, exportable to Workday as plan |
| Workday Skills Cloud needs verification of declared skills | skaills evaluates the employee on relevant skills via adaptive assessment, validates or adjusts the reported level | Skills Cloud receives a "verified" flag + measured level on the employee profile |
Technical architecture
The integration uses Workday REST APIs (Staffing, Recruiting, Talent, Learning) and Workday Studio for orchestrated flows. Authentication via OAuth 2.0 with a dedicated Integration System User (ISU) from your Workday tenant, with security groups granting only the necessary domains. Data transits via HTTPS (TLS 1.2+); skaills never stores Workday credentials, only short-lived access tokens. For bidirectional flows, we configure Workday Outbound EIBs or Studio integrations that trigger a dedicated skaills Cloud Function (`workdayWebhook`) with signature verification. All skaills-side logic is serverless, with no additional infrastructure for your team to operate.
Implementation timeline
1
Week 1
Define which Workday modules are in-scope (Recruiting, Talent, Skills Cloud, Career Hub, Learning), which events trigger the flow, and what data travels each direction. Identify the project sponsor, the customer-side Workday admin, and the assigned skaills team.Kickoff and scope
Deliverable:Scope document signed by both parties
2
Weeks 2-3
Create the Integration System User (ISU) in Workday with minimum security groups and domains. Configure the REST APIs we consume and Workday Studio if applicable. First end-to-end test with a synthetic candidate: applies to a requisition → skaills evaluation triggers → score injects into Workday with Skills Cloud mapping.Technical setup
Deliverable:E2E test passing with synthetic candidate; technical integration functional
3
Week 4
Deploy to one real recruiting team, with 5-10 real candidates flowing through end-to-end. We monitor completion rate, latency, score quality, correct Skills Cloud mapping, recruiter satisfaction. 15-minute daily standup.Controlled pilot
Deliverable:Pilot report with real-world metrics
4
Week 5
Apply adjustments based on pilot feedback. Internal documentation for your teams: how the flow operates, where to check logs, who to contact for issues. Handoff session with your Workday / HRIT team.Adjustments and documentation
Deliverable:Operational runbook + completed handoff session
5
Week 6+
Extension of the flow to your full organization. Gradual activation by team or business unit, with weekly check-ins during the first month. After that, ongoing support at the cadence we agree on (typically monthly).Full rollout
Deliverable:Integration running in production for all in-scope units
For deeper bidirectional integrations with Workday Studio, add 2-4 weeks for Studio integration design and custom field mapping. For Workday Marketplace listing, add ~9 months for certification.