---
title: "Pair custom and Workday-built agents — Kiweely"
description: "How FDEs combine first-party Workday agents and Custom Agents under one ASOR: shared security, different build paths, A2A, and Flex Credits meters."
url: https://kiweely.com/blog/pairing-custom-and-first-party-workday-agents
---

# Pairing Custom Agents with Workday-Built Agents in One Tenant

First-party agents register from Unregistered Workday Agent; Custom Agents deploy from App Builder and activate in ASOR. Pair them on purpose—shared governance, different meters—and use A2A when an outside client must call your Custom Agent.

-   By Kiweely
-   November 18
-   4 min read

Most tenants will not choose “only Workday-built” or “only custom.” They will run **both**: Self-Service Agent and other first-party skills for the common path, plus a handful of Custom Agents for processes Workday does not ship. Workday’s own Extend AI materials describe that blend—Custom Agents on the same Trusted Agent Platform fabric, automatically registered in Agent System of Record, visible in Sana, and callable over open protocols such as A2A.

Here is a pairing playbook that stays inside what Workday publishes.

## Two build paths, one control plane

|  | Workday-built (first-party) | Custom Agent |
| --- | --- | --- |
| How it enters ASOR |  **Unregistered Workday Agent** → Register | Save and Deploy (dev auto-register) / App Manager **Update Agents** in higher envs |
| Who builds skills | Workday | You (Developer Agent or manual `.agent` / `.agentskills`) |
| Typical invoke surfaces | Agent-specific tasks plus Everywhere / Sana where documented | Self-Service Agent chat panel, Sana, business processes, A2A, agent tool protocol |
| Mode notes | Per-agent (delegate and ambient exist in ASOR generally) | Delegate only |
| Delete after register | Deactivate / archive per ASOR lifecycle | Workday: cannot delete once registered |

ASOR is the shared gate: same hub, same Available To pattern, same recommendation to run **View Security for Agent Skill** before you widen access.

## When to keep a first-party agent

Use Workday-built agents when the Rate Card already meters the skill you need and Workday documents the surface (for example Self-Service Agent base vs advanced actions, Deployment Agent Ask, Adoption Agent release impact). You still owe UMSA, SKU entitlement, and per-tenant ASOR setup—but you do not owe a Custom Agent lifecycle.

## When to add a Custom Agent beside it

Add a Custom Agent when the gap is a **company-specific** multi-step flow that should still run inside Workday’s guardrails. Workday’s custom-agents announcement: Custom Agents run in the Agent Harness, inherit permissions, keep audit trails, and can pause for human approvals. Developer Agent can select Agent-Ready Tools and emit AgentSkills-format artifacts so you are not hand-wiring every tool call.

Pairing pattern that shows up in Workday’s examples: keep Self-Service Agent for everyday Q&A and writes, and put a specialized Custom Agent (Workday’s Internal Mobility Agent story) behind Gemini Enterprise or another client via A2A so managers stay in their front door while execution stays on Workday.

## A2A when the front door is outside Workday

Workday documents Agent-to-Agent for Extend Professionals: register a third-party agent definition in ASOR that references your Custom Agent as a tool, configure Available To and redirect URI, activate, then hand the Agent Card and OAuth details to the external platform. Workday recommends **one 3P agent definition per client system**, not one per Custom Agent. Prerequisites include ASOR, a deployed Custom Agent, and external-agent registration steps.

That is how you **pair** without duplicating business rules in the outside orchestrator: the outside agent discovers and calls; Workday still enforces tools and audit.

## Flex Credits: two meters on one program

The Flex Credits Rate Card (5 November 2026) prices first-party skills and Extend AI lines separately. A blended program burns:

-   First-party skill lines (for example Self-Service Agent 1 / 5 per request)
-   Custom Agent invocations (Base 1 / Standard 2 / Premium 3)
-   Agent-Ready Tool calls (per 100 calls, different rates for Custom vs non-Custom agents)
-   Developer Agent invocations while you are still building (2 per invocation, with the published annual entitlement footnote)

Forecast them as **separate burn charts**. Collapsing them into one “AI budget” hides which surface is expensive.

## Operating rhythm for an FDE-style engagement

1.  Inventory Unregistered Workday agents vs Custom Agents already in Agent Registry.
2.  For each first-party agent you will touch, finish UMSA/SKU/ASOR prerequisites before Available To grants.
3.  For each Custom Agent, run a Development/IMPL/Sandbox POC with a written Activate owner—remember you cannot delete after register.
4.  Decide surfaces (Workday chat, Everywhere, Sana, A2A client) per persona; do not assume Copilot equals every Sana capability.
5.  Align Available To groups with tool policies using **View Security for Agent Skill**.
6.  Review Passport stamps on both Workday-provided and third-party agents before Production Activate when your security policy requires stamps.
7.  Watch Platform Consumption Console daily during the first two weeks; deactivate skills that were only for discovery.

## What Workday does not say—so we do not either

Workday does not publish a single “pair these two agents” wizard. Pairing is a program design on top of ASOR, not a hidden product switch. If a customer asks whether a Custom Agent automatically inherits every Self-Service Agent skill, the documented answer is no: skills are configured per agent, and Custom Agents get the tools you put in `.agentskills`.

Sources for this session: Workday’s Custom Agents developer overview and build guide, Register and Configure Workday-Built Agents, Connect Custom Agents to External Agents Using A2A, the Extend AI custom-agents blog, the three-paths blog, Agent Passport product page, and the Flex Credits Rate Card dated 5 November 2026.

## Read next

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

-   [November 18 ### Workday FDE Skills Map: Posting Quals Meets Agent Platform](https://kiweely.com/blog/workday-fde-skills-map)
-   [November 17 ### Cursor for Workday Extend: Developer Agent vs Kiweely Vine](https://kiweely.com/blog/cursor-workday-extend-developer-agent-vs-kiweely)
-   [November 17 ### Workday Build vs Developer Agent vs Vine for consultants](https://kiweely.com/blog/workday-build-vs-developer-agent-vs-vine-for-consultants)

### More guides on Custom agents and Workday AI

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

-   [AI Gateway Document Intelligence (/ml/docint/v1/ids): Converting Workday Drive Base64 to Binary, Resume Layout Pitfalls, and Fixing Opt-In Errors](https://kiweely.com/guides/workday-document-intelligence-base64-binary-opt-in-errors)
-   [Why a Workday Custom Agent Has No Credentials Tab in Agent Management Hub, and How to Expose It Through A2A](https://kiweely.com/guides/workday-custom-agent-missing-credentials-tab-a2a)
-   [Passing Large CSV File Attachments From a Workday Custom Agent Flow to Orchestrate Without Hitting Context Limits](https://kiweely.com/guides/workday-custom-agent-csv-file-attachment-orchestrate)
-   [Preventing Duplicate Initiate\_Change\_Job Business Process Events When a Workday Custom Agent Calls a Write Tool](https://kiweely.com/guides/workday-custom-agent-duplicate-initiate-change-job)
-   [Why Custom Agent Actions Fail With S22 Permission Denied or Task Not Authorized in Agent Chat](https://kiweely.com/guides/workday-custom-agent-actions-permission-denied-tool-wids)
-   [Fixing invalid\_request OAuth Token Exchange Errors When Connecting Microsoft Copilot Studio to Workday A2A](https://kiweely.com/guides/workday-a2a-copilot-studio-oauth-invalid-request)
-   [Why Custom Agent Skills Deployed From the Developer Site Don’t Appear in Agent Management Hub, and ASOR Tenant Prerequisites](https://kiweely.com/guides/workday-agent-management-hub-skills-not-showing)
-   [Fixing Workday Developer Agent VS Code Sign-In With a Personal Developer Account and Subagent Interrupt Errors](https://kiweely.com/guides/workday-developer-agent-vscode-personal-account-login)

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