---
title: "Workday Custom Agent Missing Credentials Tab & A2A Setup"
description: "Why the Credentials tab in Agent Management Hub only shows for External Agents, and how to expose a Workday Custom Agent via the Agent2Agent (A2A) protocol."
url: https://kiweely.com/guides/workday-custom-agent-missing-credentials-tab-a2a
---

# Why a Workday Custom Agent Has No Credentials Tab in Agent Management Hub, and How to Expose It Through A2A

Workday displays the Credentials tab in Agent Management Hub only for registered External Agents. To expose a Custom Agent built on Workday’s AI platform to an external assistant, register a third-party Agent Definition in the Agent System of Record that wraps the Custom Agent WID as an A2A tool.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   4 min read
-   Published November 6
-   By Kiweely

## Why the Credentials tab is missing on a Custom Agent

In the **Agent Management Hub** report, the **Credentials** tab on an agent profile is rendered exclusively for **External Agents** (`Provider=SELF-BUILT` or third-party platform agents registered through the Agent System of Record API). When you build and deploy a **Custom Agent** (`work-event-agent.agent` and `.agentskill` files) from App Builder on the Workday Developer Site, Workday registers it as a first-party hosted agent running inside Workday’s own agent runtime. Because Workday manages the internal Agent System User (ASU) and its lifecycle automatically upon activation, no OAuth client credentials or redirect URIs are exposed on the Custom Agent’s profile page.

For the same reason, a Custom Agent built in App Builder cannot be called directly by pointing an external Model Context Protocol client straight at the Custom Agent’s internal profile, nor will it return OAuth client details on its own **Agent Registry** entry. To invoke a Workday Custom Agent from an external AI platform (such as Google Gemini Enterprise or Microsoft Copilot Studio), you must expose it through the **Agent2Agent (A2A)** protocol by registering a separate third-party Agent Definition in the Agent System of Record (ASOR) that references your Custom Agent’s Workday ID (`wid`) as a delegated tool.

## How Custom Agents and External Agents differ in ASOR

Workday’s Agent System of Record separates agent registrations by where the reasoning loop executes:

-   **Custom Agents (Workday-hosted):** Authored in App Builder inside an Agent app or Extend app, deployed via **Save and Deploy**, and executed inside Workday’s chat panel or Sana. When you run **Configure Agent** and **Activate Agent**, Workday generates an internal Agent System User (visible on the **All AI Agent Accounts** report) and binds it to the agent, without issuing external OAuth client credentials.
-   **External Agents (third-party hosted):** Defined and registered via `POST /asor/v1/agentDefinition`. Because the runtime lives outside Workday, ASOR generates an OAuth 2.0 Client ID, Client Secret, Authorize Endpoint, and Token Endpoint during the first **Configure Agent** run and displays them on the **Credentials** tab under **OAuth Details for Delegate Skills** (or **OAuth Details for Ambient Skills**).

Workday recommends creating one third-party Agent Definition per external client system you integrate with, rather than creating a separate external wrapper per Custom Agent.

## Exposing a Custom Agent externally via the A2A protocol

To surface your deployed Custom Agent to an external platform and obtain the **Credentials** tab for OAuth connectivity, wrap the Custom Agent inside a third-party ASOR agent definition operating in `Mode=Delegate`.

### 1\. Copy the Custom Agent’s Workday ID

1.  In your tenant, open the **Agent Management Hub** report and select the **Agent Registry** tab.
2.  Confirm your Custom Agent’s skills are enabled and activated via **Configure Agent** and **Activate Agent**.
3.  Open the related actions menu on the Custom Agent and select **Integration IDs** > **View IDs**.
4.  Copy the 32-character **Workday ID** (`wid`), or query the ASOR Finder API (`GET https://us.agent.workday.com/asor/agentResourceSearch/v1?searchString=equipment&toolType=AGENT`) to locate it programmatically.

### 2\. Register the 3P Agent Definition in ASOR

Connect to your tenant from the Workday Developer Site (using an account granted the *Setup: Agents*, *Manage: Agents*, and *Agent Management Hub* domains in the *Agent System of Record* functional area) and copy your bearer access string. Send a `POST` request to `https://<region>.agent.workday.com/asor/v1/agentDefinition` with `wd-agent-tenant-alias` set to your tenant name:

json

```
{
  "name": "External Assistant A2A Gateway",
  "description": "Third-party agent definition exposing internal Custom Agents over A2A",
  "url": "https://us.agent.workday.com",
  "version": "v1",
  "provider": {
    "id": "Provider=SELF-BUILT"
  },
  "platform": {
    "id": "Platform=OTHER"
  },
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "stateTransitionHistory": false
  },
  "skills": [
    {
      "id": "custom-agent-as-a-tool",
      "name": "Equipment Request Custom Agent",
      "description": "Delegates equipment request queries and actions to the Workday Custom Agent.",
      "inputModes": [
        { "type": "text/plain" }
      ],
      "outputModes": [
        { "type": "text/plain" },
        { "type": "application/json" }
      ]
    }
  ],
  "workdayConfig": [
    {
      "skillId": "custom-agent-as-a-tool",
      "executionMode": {
        "id": "Mode=Delegate"
      },
      "workdayResources": [
        {
          "tool_name": "Equipment Request Agent Tool",
          "description": "Invokes the internal Equipment Request Custom Agent",
          "agent_resource": {
            "id": "386c0e439ecd100039e864720d570000"
          }
        }
      ]
    }
  ]
}
```

Replace `386c0e439ecd100039e864720d570000` with the Custom Agent WID you copied in step 1.

### 3\. Configure the wrapper agent to get OAuth credentials

1.  Return to **Agent Management Hub** > **Agent Registry** and select the newly registered `External Assistant A2A Gateway` entry.
2.  Click **Configure Agent**. Enable the **Status** toggle on the `custom-agent-as-a-tool` skill and populate **Available To** with the security groups permitted to invoke the agent.
3.  Select **Confirm**, click **OK**, and enter the external platform’s OAuth **Redirect URI** when prompted.
4.  Click **OK**. Workday displays the generated OAuth Client ID, Client Secret, Authorize Endpoint (`https://<region>.agent.workday.com/auth/authorize/<tenant-alias>`), and Token Endpoint (`https://<region>.agent.workday.com/auth/oauth2/<tenant-alias>/token`). Copy the Client ID and Client Secret immediately, as the secret is shown only once.
5.  Open the agent profile again and click **Activate Agent**.

### 4\. Fetch the A2A Agent Card JSON

To import the agent into your external platform, use an Integration System User (ISU) OAuth client registered via **Register API Client for Integrations** (with the *Agent System of Record* functional area scope and **Include Workday Owned Scopes** checked) to mint an ISU bearer string, then request the A2A discovery document:

bash

```
curl --request GET \
  --url "https://us.agent.workday.com/v1/a2a/acme_dpt1/386c0e439ecd100039e864720d570000/.well-known/agent-card.json" \
  --header "Accept-Encoding: identity" \
  --header "Content-Type: application/json"
```

Pass the ISU bearer credential in the standard `Authorization` header and use the wrapper agent’s WID in the URL path. Import the resulting `agent-card.json` payload and the OAuth client details into your external assistant.

## Verifying the setup in your tenant

Open **Agent Management Hub** and view the profile of the newly registered third-party wrapper agent. Confirm that the **Credentials** tab is now visible alongside **Skills** and **Analytics**, and that **OAuth Details for Delegate Skills** lists your Redirect URI, Authorize Endpoint, and Token Endpoint. Then run the **View Security for Agent Skill** report on both the wrapper agent and the underlying Custom Agent to verify that the security groups in **Available To** also hold permissions on every domain and business process policy securing the Custom Agent’s tools.

## Sources checked

-   [View External Agent Credentials](https://developer.workday.com/documentation/GUID-06065736-7eb0-4ea6-afbb-5000f458eb89-enHYPHENus)
-   [Connect Custom Agents to External Agents Using A2A](https://developer.workday.com/documentation/GUID-59871309-bbc4-4f06-9a68-80c331c7ed7b-enHYPHENus)
-   [Custom Agents on Workday's AI Platform](https://developer.workday.com/documentation/GUID-c3910467-0fd6-4f27-b78e-436cfe0a3147-enHYPHENus)
-   [Build and Deploy Custom Agents](https://developer.workday.com/documentation/GUID-c2e04f80-557a-4968-8957-9f1210156908-enHYPHENus)
-   [About Workday Agents](https://developer.workday.com/documentation/GUID-0e960e10-8a0f-4975-afc6-83ab303ed485-enHYPHENus)

## Related guides

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

-   [### Calling External Glean and Sana Agents From Workday Extend Without Hitting 408 Request Timeouts Direct outbound HTTP calls from a Workday Extend PMD page time out with Status Code 408 when an external Glean agent (/rest/api/v1/agents/runs/wait) or Sana webhook exceeds the presentation timeout. Route external agent runs through Workday Orchestrate and External Client CredStore.](https://kiweely.com/guides/workday-extend-external-agents-glean-sana-408-timeout)
-   [### Why Custom Agent Actions Fail With S22 Permission Denied or Task Not Authorized in Agent Chat Orchestration Builder runs Custom Agent Actions directly as your user, whereas Agent Chat enforces dual ASOR authorization and restricts the Agent System User token to the resources listed in your .agentskill file. Register every REST, SOAP, and WQL resource WID via the Finder API to fix it.](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 Connecting Microsoft Copilot Studio to a Workday Agent over the Agent2Agent (A2A) protocol fails with 400 BadRequest and invalid\_request when the token exchange omits Proof Key for Code Exchange (PKCE) or uses mismatched OAuth endpoints. Align PKCE and your ASOR Delegate skill settings to fix it.](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 When you deploy a Custom Agent with multiple .agentskill files from App Builder, Workday’s Agent System of Record packages all of their tools into a single combined skill registration that starts disabled. Learn how to enable and sync skills in Agent Management Hub and verify ASOR prerequisites.](https://kiweely.com/guides/workday-agent-management-hub-skills-not-showing)

### More guides on Custom agents and Workday AI

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

-   [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)
-   [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)
-   [Finding Workday tool IDs with the Agent Resource Search (finder) API](https://kiweely.com/guides/workday-finder-api-tool-discovery)
-   [Connecting an Extend app to the Workday Self-Service Agent and Microsoft Teams](https://kiweely.com/guides/workday-extend-self-service-agent-teams)
-   [How to build a chatbot in Workday Extend](https://kiweely.com/guides/workday-extend-chatbot)
-   [How to call AI Gateway Document Intelligence from a Workday Extend app](https://kiweely.com/guides/workday-extend-ai-gateway-document-intelligence)
-   [Who gets Workday Developer Agent, and what it uses in Flex Credits](https://kiweely.com/guides/workday-developer-agent-access-flex-credits)

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

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

-   [What to put in a Workday SOW when agents are in scope](https://kiweely.com/blog/workday-implementation-sow-ai-agents)
-   [Can AI agents speed up a Workday implementation? What they do in the tenant today](https://kiweely.com/blog/kiweely-vine-workday-implementation-project)
-   [A hybrid Workday build: people, Deployment Agent, and a desktop agent](https://kiweely.com/blog/hybrid-workday-delivery-ai-agents)

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