Workday Extend
Custom apps, orchestrations and AI-ready extensions made with Workday Extend, set up so work that happens outside Workday moves inside it, with Workday's own security and data.
An Extend app is only as useful as the data it can reach, and connecting Workday to other systems is the work Hazeberg knows best, with more than 200 integrations behind it.
One place to work
Side apps and spreadsheets moved into Workday
Security already in place
Apps follow Workday's roles and permissions
Safe through releases
Built on supported Workday tools, tested each update
Ready for AI
Designed to work with Workday's agent tools
Extend capabilities
Every organization has work that happens next to Workday: a tracker in a spreadsheet, a form in another tool, an approval by email. When configuration can't bring it in, Extend can. We help you decide which of those to build, then build them so they feel like part of Workday.
01 / 06
Decide
Extend is the right tool when configuration runs out, not before.
Configuration options checked first
Use cases scored on value and effort
Extend Essentials or Professional, sized to need
A clear build or skip recommendation
02 / 06
Design
Designed with the people who will use it, in Workday's own look.
Workshops with the people doing the work today
New data objects for information Workday doesn't hold
Screens that follow Workday's design standards
Security roles mapped before build begins
03 / 06
Build
Built with Workday's own tools, so it behaves like the rest of Workday.
App Builder pages, in visual or code mode
Business processes and approvals for the new work
Reports and dashboards on app data
Code reviewed against Workday's guidelines
04 / 06
Connect
Data from other systems, pulled in at the moment the app needs it.
Workday Orchestrate flows across Workday and other systems
Calls to external APIs and services
Events that trigger the next step automatically
Workday data read and written under its own security
05 / 06
Assist
Ready for the agents Workday is building, and the ones you will.
AI widgets inside Extend apps
Agents built with Workday's agent tools
Connections to your own AI assistant
Agent actions governed by Workday security
06 / 06
Run
Custom apps need looking after like everything else in Workday.
Testing before each deployment
Checks in the preview window before every Workday release
Documentation your team can own
Who it's built for
A custom app changes the working day for everyone who used to work around the gap. Here is what changes for each of them.
Requests, approvals and records in Workday instead of side tools.
Apps shaped around how the work is really done.
Steps that used to need an email or rekeying run on their own.
App data sits in Workday, ready for reports and dashboards.
Side apps and spreadsheets retired as their work moves into Workday.
Apps follow Workday's roles and permissions without a separate setup.
Supported Workday tools instead of custom code running outside it.
Documentation and handover, so your team can maintain what we build.
Apps that look and work like the rest of Workday.
New tasks and approvals arrive where everything else already does.
Approvals that progress without chasing anyone by email.
Assistants that act within each person's own Workday access.
How we engage
The right route depends on whether you are building your first Extend app, improving apps already live, or need a team to keep them running.
Where Extend fits
Good candidates share a pattern: work that depends on Workday data but happens somewhere else. These are the patterns that come up most often.
Equipment, access or policy-exception requests that currently live in email.
Certifications, licenses, conflicts of interest or grant conditions kept in spreadsheets.
Recognition, mentoring or volunteering programs tied to the worker record.
Team capacity or project staffing pictures built on live Workday data.
Credential checks in healthcare, faculty duties in universities, staff attestations in financial services.
Skills, leave or policy questions answered in chat, with the action completed in Workday.
Send us the workaround your team relies on most, and we'll tell you whether configuration, an integration or an Extend app is the right fix.
Questions
Only once configuration runs out. Many requests can be met with business processes, custom fields or reports, which cost less to run. Extend is the answer when you need new data, new screens or a process Workday doesn't offer. Saying so when configuration will do is part of the job at Hazeberg.
Extend runs on Workday's own platform, which Workday designs to be update safe, so a release shouldn't break an app the way it can break code running outside Workday. Every app is still tested during Workday's preview period before each release goes live.
Yes. Workday Orchestrate connects apps to external APIs and services, so an app can fetch or send data elsewhere as part of its process.
It depends on what you plan to build. Workday sells Extend in tiers, and some capabilities, such as Workday's newer agent-building tools, need the Professional tier. We size the license to the apps on your roadmap before you commit.
Your team, ours or both. We document each app and hand it over, or look after it through AMS alongside the rest of your Workday.