I will configure workday studio, eib, core connector, and API integrations


About this gig
Senior Workday Integration Consultant (8+ years, 30+ enterprise clients).
I design, build, and support Workday integrations and reporting end-to-end discovery, technical design, development, testing, cutover, and handoff. I work as a hands-on consultant with your Workday team: clear specs, practical security, and builds that operations can support.
What I cover
Workday Web Services (REST/SOAP), ISU/security setup guidance, and API-first designs when Studio isnt needed
Studio, EIB, Core Connectors (CCW/CCB), Document Transformation / XSLT
HCM, Payroll, Benefits, and Time Tracking integration surfaces
Advanced reports and calculated fields that feed or validate integrations
Common third-party connections (HR, payroll, identity, ATS, e-sign, finance, and compliance vendors)
Packages
Basic 60-min consult + written next steps
Standard client-ready design / spec
Premium scoped build or fix in your sandbox + runbook
Work happens in your sandbox/UAT with your approvals. Larger or multi-week programs available via custom offer or hourly.
Get to know Stuart Ssali
Workday integration architect,APIs,HCM,Studio, AI systems and automations
- FromUnited States
- Member sinceMay 2026
Languages
English
My Portfolio
FAQ
Do you need access to our Workday tenant?
Yes — typically sandbox or UAT with an Integration System User (or equivalent). I don’t provide a personal Workday tenant. Production access only if you require it for go-live support.
What kinds of Workday work do you take?
Studio, EIB, Core Connectors, Web Services (REST/SOAP), Document Transformation / XSLT, advanced reports and calculated fields, and third-party / vendor integrations across HCM, Payroll, Benefits, and Time Tracking. If you’re unsure which path fits, start with Basic.
What’s included in each package?
Basic = 60-min consult + written next steps. Standard = design/spec (approach, security notes, field map, test cases). Premium = scoped build or fix in your sandbox + handoff runbook. Extra scope is a custom offer or hourly.
Can you work with our internal Workday team?
Yes. Many engagements are consult + spec + short working sessions while your team (or partner) implements. I’m comfortable as the integration SME on calls.
Studio vs EIB vs API — which should we use?
Depends on volume, transforms, the other system, and supportability. I’ll recommend the simplest pattern that meets the requirement — including API-first when Studio or a packaged connector isn’t needed.
What do you need from me to start?
Integration goal, systems involved, sandbox access status, and any error logs / sample payloads / draft specs. Use the Requirements form when you order.
Do you guarantee Workday or vendor outcomes?
I own the Workday-side design/build within the agreed scope and hours. I can’t guarantee third-party vendor SLAs, licensing, or tenant limitations outside our control.
Revisions and timeline?
Revision counts apply to clarifying the delivered artifacts in that package — not unlimited new scope. Delivery times assume timely access and answers from your side.
Languages / time zones?
English. US-based; flexible for scheduled calls across common client time zones.
Larger projects?
Yes — multi-integration programs, multi-week onboarding, or hypercare via custom offer or hourly after we align on scope.

