---
title: "When not to build a custom agent — Kiweely"
description: "Use a Workday-built agent, Sana Enterprise, or an external agent before you build a custom agent in Workday Extend."
url: https://kiweely.com/blog/when-not-to-build-workday-custom-agent
---

# 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
-   November 16
-   7 min read

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 |
| --- | --- | --- |
| Suggest case type, assign some new Help cases, summarize the thread | Case Agent | Re-rank a queue from email-created cases. Assignment does not cover email, business process, or Create Case Advanced. |
| Ask questions about an Advanced report you have open | Core Reporting Agent | Analyze Matrix, scheduled, or background reports. The skill will not. |
| Pull procure-to-pay audit samples | Financial Audit Agent | Read HCM files or samples older than 45 days in a non-Production tenant. |
| Draft a customer contract from a PDF | Revenue Contract Agent | Skip Contract Intelligence, the intake form, or Customer Contract Event approval. |
| Explain Adaptive numbers, or submit plan changes | Planning Agent for Ask Workday exploration; Decision Intelligence for what-if and submit-to-plan | Treat Data Exploration as a long-term skill. Workday plans to retire it in November 2026. |
| Grade contingent applicants or rediscover VNDLY talent | Contingent Sourcing Agent | Give vendor users the agent UI. Workday says vendors cannot use it. |
| Time off, personal data, goals, team learning, policy articles | Self-Service Agent | Serve contingent workers, proxies, or additional jobs. Those are documented exclusions. |
| Book travel | Travel Agent | Invent a booking flow beside the shipped agent until you have checked the travel setup guide. |
| Payroll questions | Payroll Agent | Assume it is Self-Service Agent. They can show two different chat bubbles. |
| Survey comments | Talent Sentiment Agent | Expect it to update worker records. The reference describes ranked insight cards and follow-up questions. |
| Release impact in Preview | Adoption Agent | Run that skill in Production. Registration is in Preview. |
| Business process recommendations | BP Optimize Agent | Treat recommendations as already configured. |
| Implementer Q&A and tenant inspection | Deployment Agent | Put 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](https://kiweely.com/) 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](https://kiweely.com/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.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 16 ### Sana custom agents vs the desktop Workday chat](https://kiweely.com/blog/sana-custom-agent-vs-desktop-workday-copilot)
-   [November 16 ### Workday Agent Gateway, MCP, and A2A](https://kiweely.com/blog/workday-agent-gateway-mcp-a2a-explained)
-   [November 16 ### Case Agent and HR service delivery](https://kiweely.com/blog/workday-case-agent-hr-service-delivery)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [AI Agents That Edit Workday Studio XSLT Safely: Diff, AUnit, Then Deploy](https://kiweely.com/guides/ai-agents-edit-workday-studio-xslt-safely)
-   [Best AI Agent Setup for Workday Security Policy and Pay-Access Audits](https://kiweely.com/guides/best-ai-agent-setup-for-workday-security-audits)
-   [Forecasting Workday Flex Credits for HCM Agents vs Financials Workloads](https://kiweely.com/guides/forecasting-workday-flex-credits-hcm-vs-financials)
-   [Best AI Agent Setup for Workday Orchestrate for Integrations](https://kiweely.com/guides/best-ai-agent-setup-for-workday-orchestrate)
-   [Chargeback Models for Workday Flex Credits Across HR, Finance, and IT](https://kiweely.com/guides/workday-flex-credits-chargeback-hr-finance-it)
-   [Build a Workday UI Test Charter an AI Agent Can Run Without Brittle CSS](https://kiweely.com/guides/workday-ui-test-charter-for-ai-agents)
-   [Best AI Agent Setup for Workday Studio and XSLT Work](https://kiweely.com/guides/best-ai-agent-setup-for-workday-studio)
-   [Best AI Agent Setup for Workday Extend Apps in 2026](https://kiweely.com/guides/best-ai-agent-setup-for-workday-extend-apps)

## 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.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## 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.
