---
title: "Custom Agent first POC checklist — Kiweely"
description: "A first custom-agent proof of concept: Developer Agent or manual artifacts, Save and Deploy limits, ASOR activate, and what Workday says you get in Sana."
url: https://kiweely.com/guides/workday-custom-agent-first-poc-checklist
---

# Workday Custom Agent First POC Checklist for Implementers

A first Custom Agent POC is Build → Save and Deploy to Development, IMPL, or Sandbox → Configure Agent → Activate in ASOR. Once registered you cannot delete it. Workday says the agent is A2A-ready and available in Sana.

-   **Checked** against Workday on November 18
-   Applies to **Workday Extend AI**
-   5 min read
-   Published November 18
-   By Kiweely

A first Custom Agent proof of concept is: describe the job in **Developer Agent** (or hand-build `.agent` / `.agentskills`), **Save and Deploy** to Development, IMPL, or Sandbox, then **Configure Agent** and **Activate** in Agent System of Record. Workday auto-registers in dev environments; once registered you cannot delete the agent.

-   Checked against Workday on November 18, 2026
-   Applies to Workday Extend AI
-   8 min read

## POC outcome to agree up front

| Outcome | What Workday documents |
| --- | --- |
| Runtime | Custom Agents run on Workday’s AI platform (Trusted Agent Platform / Agent Harness in Workday’s Extend AI materials) |
| Data actions | Can read, write, and take actions in Workday on behalf of the user |
| Mode | Delegate mode only |
| Surfaces after activate | Self-Service Agent chat panel, Sana, business process framework, A2A, agent tool protocol |
| Side effect | Automatically A2A-ready and available in Sana |

Do not promise Production Save and Deploy from App Builder—Workday’s step note limits Save and Deploy to Development, IMPL, and Sandbox. Higher environments use **App Manager** → **Update Agents**.

## Prerequisites checklist

-   Development tenant connected on the Developer Site
-   **Set Up Agent System of Record** completed in that tenant
-   Flex Credits model understood for the account (Workday states AI agents use Flex Credits; Rate Card lines meter Developer Agent, Custom Agent invocations, and Agent-Ready Tool calls)
-   If the POC uses Custom Agent Actions, those orchestrations are configured first
-   Browse available tools in Workday’s tool explorer before you lock the prompt

Agent apps are a dedicated app type: they support the subset of Extend components needed for agents, do **not** include PMD or Model components, and Workday says they do not count against Extend app entitlements.

## Build path A — Developer Agent (preferred for speed)

1.  On the Workday Developer Site home page, click **Build an Agent**.
2.  Select **Build with Developer Agent** (or create via other Create Agent options and iterate in App Builder).
3.  Prompt the use case (Workday’s example: “Build me an agent that gets my worker info.”).
4.  Review the suggested Custom Agent (`.agent` definition plus `.agentskills` capabilities). You cannot create agents with the same name.
5.  Optionally prompt skill edits (example: add a skill to view available time off).
6.  **Apply Changes** → **Confirm**.
7.  Optionally open **Skills** → Code view to edit `.agentskills`. When APIs appear in Custom Agent Actions, include the API WID exactly—Workday warns that any space in a WID prevents the tool from registering.
8.  **Save and Deploy**.

Developer Agent can discover Agent-Ready Tools capabilities, look up deployed Custom Agent Actions, compose a formatted skill file, and include bundled scripts.

## Build path B — Manual artifacts

Define your own `.agent`, `.agentskills`, and tools. Skill files must include `allowed-tools` and `tool-wids` (tool names and WIDs). Files use YAML frontmatter and markdown instructions. Agents can carry multiple skill files; ASOR aggregates tools into a single skill registration.

## ASOR gate — configure and activate

After deploy:

1.  Select **View Agent Registry**.
2.  Open the Custom Agent.
3.  **Configure Agent**.
4.  In the **Status** column, enable the relevant skill.
5.  In **Available To**, select security groups that may access the agent. Runtime checks **both** agent access and API/tool permissions—align groups using **View Security for Agent Skill**.
6.  **Activate**. Note: once registered, you cannot delete it.

In development environments ASOR registers automatically on Save and Deploy. ASOR is the strict gate for Workday Chat Panel visibility: before configuration and activation the agent stays hidden from end users.

On first activate with a security group assigned, Workday creates an **Agent System User (ASU)** named for the agent. Redeploys keep the same ASU; deactivating the agent deactivates the ASU. User permissions and ASU permissions are separate: a user can invoke an agent that performs actions the user cannot do directly, and the reverse.

## Promote beyond the POC tenant

For higher environments:

1.  Open **App Manager** in Workday.
2.  **Configure** the Agent app.
3.  On **Configuration** → Agent card, select **Update Agents** to register in ASOR.
4.  Confirm in **Update Extend Agents**, then finish ASOR security configuration and activation in that tenant.

## POC test script (evidence, not vibes)

1.  Invoke from the Self-Service Agent chat panel as a user in Available To.
2.  Repeat as a user outside Available To—expect no access.
3.  Exercise one read tool and one write tool covered by the skill; confirm audit identity under the ASU model Workday describes.
4.  If Sana is in scope for the customer, confirm the agent appears there only after ASOR activation (Workday: automatically available in Sana once the platform path succeeds).
5.  Open **Agent Traces** for failed tool calls before you widen Available To.

## Flex Credits to watch on a POC

From the Flex Credits Rate Card (last updated November 5, 2026):

| Meter | Credits (as published) |
| --- | --- |
| Developer Agent Invocation | 2 per invocation (footnote: annual entitlement of 50,000 invocations before Flex Credits consume) |
| Custom Agent Invocation | Base 1 / Standard 2 / Premium 3 per invocation |
| Agent-Ready Tool — base tool call | 5 per 100 calls when used by Custom Agents; 10 per 100 when used by non-Custom Agents |

Workday does not publish dollar prices on the Rate Card PDF itself—only credit meters.

## Honest stop-conditions

-   Stop if ASOR is not enabled in the POC tenant.
-   Stop if the only ask is a hard-coded integration: Workday says Agent-Ready Tools are for AI agent use, not hard-coded integrations.
-   Stop before Production promises: App Builder Save and Deploy is limited to Development, IMPL, and Sandbox.
-   Stop if stakeholders expect ambient (non-delegate) custom agents—Workday documents Custom Agents as Delegate mode only.

## Frequently asked questions

### Which tenants can I Save and Deploy a Custom Agent to?

Workday’s build guide says you can only deploy to Development, IMPL, and Sandbox tenants from App Builder Save and Deploy.

### Can I delete a Custom Agent after it is registered in ASOR?

No. Workday’s activate step notes that once a Custom Agent is registered, you cannot delete it.

### Where can users invoke a Custom Agent after activation?

Workday lists the Self-Service Agent chat panel, Sana, the business process framework, Agent-to-Agent (A2A), and the agent tool protocol. Custom agents are Delegate mode only.

## Frequently asked questions

### Which tenants can I Save and Deploy a Custom Agent to?

Workday’s build guide says you can only deploy to Development, IMPL, and Sandbox tenants from App Builder Save and Deploy.

### Can I delete a Custom Agent after it is registered in ASOR?

No. Workday’s activate step notes that once a Custom Agent is registered, you cannot delete it.

### Where can users invoke a Custom Agent after activation?

Workday lists the Self-Service Agent chat panel, Sana, the business process framework, Agent-to-Agent (A2A), and the agent tool protocol. Custom agents are Delegate mode only.

## Sources checked

-   [Build and Deploy Custom Agents](https://developer.workday.com/documentation/GUID-c2e04f80-557a-4968-8957-9f1210156908-enHYPHENus/BuildandDeployCustomAgents)
-   [Custom Agents on Workday's AI Platform](https://developer.workday.com/documentation/GUID-c3910467-0fd6-4f27-b78e-436cfe0a3147-enHYPHENus)
-   [Set Up Agent System of Record](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/set-up-agent-system-of-record.html)
-   [Workday Flex Credits Rate Card](https://forms.workday.com/content/dam/web/en-us/documents/legal/flex-credits-rate-card.pdf)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Workday Developer Agent and Agent-Ready Tools for Implementers Developer Agent turns a plain-language use case into .agent and .agentskills artifacts that select Agent-Ready Tools. Those tools are for AI agents only, gated by ASOR, and metered on the Flex Credits Rate Card.](https://kiweely.com/guides/workday-developer-agent-and-agent-ready-tools)
-   [### Register Workday-Built Agents and Activate Skills in Agent Management Hub After ASOR is on, Workday-built agents still sit on the Unregistered tab until you register them, toggle skills, assign security groups, and activate. This guide is the implementer checklist for that path.](https://kiweely.com/guides/workday-asor-register-activate-agent-skills)
-   [### A Workday custom agent’s lifecycle, from first deploy to Production App Builder deploys a custom agent to Development, Implementation and Sandbox tenants, where ASOR registers it and you activate it. Production takes an app promotion, Update Agents in App Manager, and ASOR security and activation set up again in that tenant.](https://kiweely.com/guides/workday-custom-agent-lifecycle-promotion)
-   [### How to build your first Workday custom agent, step by step Yes, Workday Extend supports custom agents. Build your first in six steps: describe one job, generate it with Developer Agent, review its tools, deploy to Development, test as each user, then, for customer work, promote. A free personal tenant is enough to start.](https://kiweely.com/guides/build-first-workday-custom-agent)

### More guides on Custom agents and Workday AI

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

-   [Workday First-Party Agent Tenant Prerequisites for Implementers](https://kiweely.com/guides/workday-first-party-agent-tenant-prerequisites)
-   [Deployment Agent in Customer Central vs Implementation tenants](https://kiweely.com/guides/workday-deployment-agent-customer-central-vs-implementation-tenant)
-   [Workday Agent Passport for Implementers: Read Stamps Before You Activate Skills](https://kiweely.com/guides/workday-agent-passport-for-implementers)
-   [Ask skill on but answers feel generic: use CRAFT and “in my tenant”](https://kiweely.com/guides/ask-skill-enabled-still-generic)
-   [Deployment Agent missing? Register it from Unregistered Workday Agent](https://kiweely.com/guides/deployment-agent-not-registered)
-   [Keep Deployment Agent Ask alive across Sandbox refreshes](https://kiweely.com/guides/workday-deployment-agent-ask-after-sandbox-refresh)
-   [Workday Deployment Agent: Q&A Task vs Ask Skill Setup](https://kiweely.com/guides/workday-deployment-agent-qa-vs-ask)
-   [How do I secure Workday RaaS access for an internal LLM or AI agent?](https://kiweely.com/guides/workday-raas-for-ai-agents-security)

### From the blog on Custom agents and Workday AI

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

-   [A hybrid Workday build: people, Deployment Agent, and a desktop agent](https://kiweely.com/blog/hybrid-workday-delivery-ai-agents)
-   [How a client can test Workday when an agent is in the room](https://kiweely.com/blog/workday-client-uat-with-ai-agents)
-   [Workday Deployment Agent vs a desktop Workday agent](https://kiweely.com/blog/deployment-agent-vs-desktop-workday-copilot)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

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

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
