Skip to content
KiweelyKiweelyKiweely

When not to build a Workday custom agent

Workday already ships agents for help-desk cases, Advanced-report questions, procure-to-pay audit packages, customer-contract drafts, Adaptive Planning analysis, and VNDLY contingent sourcing. A custom Extend agent is the wrong first build when one of those skills matches the job.

  • By Kiweely
  • 7 min read
On this page

A custom agent in Workday’s admin guide means an agent you build in Workday Extend. It is one of five types in Agent System of Record, next to Workday-built, external (self-built), partner, and Sana user agents. Most “we should build an agent” requests fail the first test: Workday already ships a skill for that job, or the job is a Sana Enterprise workflow, or the job should stay a business process with no model in the loop.

Building does not relax security. Every skill’s tools are Workday APIs. The user needs a security group on the skill and a security group on the API. Proxy and “do this as my manager” are already unsupported on Self-Service Agent. A custom agent you hope will bypass that is a second project with the same domain policies underneath.

Start with the shipped row

The Workday-Built Agents reference, updated 2026-09-04 on that page, already covers:

If the job is Use the shipped agent Do not build a custom agent to
If the job isSuggest case type, assign some new Help cases, summarize the thread Use the shipped agentCase Agent Do not build a custom agent toRe-rank a queue from email-created cases. Assignment does not cover email, business process, or Create Case Advanced.
If the job isAsk questions about an Advanced report you have open Use the shipped agentCore Reporting Agent Do not build a custom agent toAnalyze Matrix, scheduled, or background reports. The skill will not.
If the job isPull procure-to-pay audit samples Use the shipped agentFinancial Audit Agent Do not build a custom agent toRead HCM files or samples older than 45 days in a non-Production tenant.
If the job isDraft a customer contract from a PDF Use the shipped agentRevenue Contract Agent Do not build a custom agent toSkip Contract Intelligence, the intake form, or Customer Contract Event approval.
If the job isExplain Adaptive numbers, or submit plan changes Use the shipped agentPlanning Agent for Ask Workday exploration; Decision Intelligence for what-if and submit-to-plan Do not build a custom agent toTreat Data Exploration as a long-term skill. Workday plans to retire it in November 2026.
If the job isGrade contingent applicants or rediscover VNDLY talent Use the shipped agentContingent Sourcing Agent Do not build a custom agent toGive vendor users the agent UI. Workday says vendors cannot use it.
If the job isTime off, personal data, goals, team learning, policy articles Use the shipped agentSelf-Service Agent Do not build a custom agent toServe contingent workers, proxies, or additional jobs. Those are documented exclusions.
If the job isBook travel Use the shipped agentTravel Agent Do not build a custom agent toInvent a booking flow beside the shipped agent until you have checked the travel setup guide.
If the job isPayroll questions Use the shipped agentPayroll Agent Do not build a custom agent toAssume it is Self-Service Agent. They can show two different chat bubbles.
If the job isSurvey comments Use the shipped agentTalent Sentiment Agent Do not build a custom agent toExpect it to update worker records. The reference describes ranked insight cards and follow-up questions.
If the job isRelease impact in Preview Use the shipped agentAdoption Agent Do not build a custom agent toRun that skill in Production. Registration is in Preview.
If the job isBusiness process recommendations Use the shipped agentBP Optimize Agent Do not build a custom agent toTreat recommendations as already configured.
If the job isImplementer Q&A and tenant inspection Use the shipped agentDeployment Agent Do not build a custom agent toPut it in Production chat. The reference limits that inspection to non-Production tenants.

If your sentence matches the middle column, register that agent. Custom code starts when the middle column is empty.

Four builds that are not “an Extend agent”

  1. Turn a skill on. Register and configure in Agent Management Hub. Available To is the access list. Activation also activates the Agent System User. That is administration, not a build.
  2. Sana Enterprise agent builder. You describe the agent in natural language, trigger it manually, on a schedule, or from a third-party event, and administrators can publish it. Sana Core does not include this. Those agents are Sana user agents in ASOR, not Extend custom agents.
  3. External agent. You build it on another platform and register it through an API. It calls Workday through Agent Gateway as an Agent System User. Choose this when the workflow lives in that platform and Workday is one system it must update.
  4. Partner agent. A certified partner ships it. You govern it in the hub. You do not rewrite it in Extend to “own” it unless the partner has no skill you can configure.

When a custom Extend agent is the wrong engineering bet

  • You need a human’s security, not a service account. Delegate mode uses the worker’s permissions. Ambient mode uses the agent’s own permissions and does not ask for an interaction group. If the audit question is “which employee approved this,” an ambient bot is the wrong shape even if Extend can call the API.
  • The process is already a business process. Case assignment and customer-contract creation both end in Workday’s existing assignment or Customer Contract Event. An agent that files a second approval path will disagree with the business process.
  • You need heavy data movement. Workday’s orchestration course manual says to use orchestrations for small transactional data, not heavy processing, and lists runtime caps: 5 minutes synchronous, 20 minutes asynchronous, 25 seconds when a presentation page launches a synchronous orchestration, 20 MB launch message, 20 MB concurrent memory, 500 MB response message, 500 MB concurrent disk. The manual says the Developer site is the current source for limits. Those caps are a reason not to hide a warehouse sync inside an Extend agent.
  • You need Production before the agreements. Workday-built agents need UMSA in non-Production and Production. Flex Credits policy is required to register and use agents in Production. Self-built agents do not need UMSA in non-Production. None of that is optional because the agent is “internal.”
  • You need usage proof for a business case. Session and unique-user reports in Agent Management Hub are documented for Workday-built agents. A custom agent will not automatically fill those tiles. Plan a different measure before you promise an executive dashboard.
  • You are trying to fix Sandbox. Self-Service article extraction is not supported in Sandbox. Financial Audit Agent returns 45 days in non-Production. Building a custom agent does not widen those windows.
  • The user population is contingent workers in employee chat. Self-Service Agent excludes them. A custom agent still needs a supported tool and a security group that can see contingent data. Write that design down before anyone opens an Extend app.

A short decision

Answer in order:

  1. Is there a Workday-built row whose published limitations still fit? Register it.
  2. Is the gap “schedule this and confirm with the employee”? Price Sana Enterprise before Extend.
  3. Does the logic already run in another agent platform that must call Workday? Register an external agent.
  4. Is a certified partner already selling the skill? Govern theirs.
  5. Only then brief an Extend custom agent, with delegate versus ambient chosen up front, API domains named, and orchestration size checked against the course-manual caps.

Kiweely Vine is the desktop agent consultants use to build Extend apps and Studio integrations. It does not remove the need for the decision above. Kiweely Bridge, coming next, is for employees calling Workday as themselves from Claude, ChatGPT, or Gemini. That is also not a custom Workday agent.

Frequently asked questions

Are custom agents free of Flex Credits?

Workday ties Production registration and use of agents to the Flex Credits policy on the setup pages. Do not assume Extend agents are unmetered. Read the Rate Card inside Platform Consumption Console for your agreement version.

Can we prototype in Sandbox without UMSA?

For self-built agents, Workday says UMSA is not required in non-Production. Workday-built agents still need UMSA there. Confirm which type you are prototyping before you skip the agreement.

What if the shipped agent is close but the channel is wrong?

Prefer a gap note over a rebuild. Example: Case Agent will not assign email-created cases. The fix may be to stop creating those cases from email, not to train a new classifier.

Sources checked

About Workday Agents, Workday-Built Agents, Sana Workspace, Register and Configure Workday-Built Agents, and the Extend orchestrations course manual, fetched 2026-11-16.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.