Workday names both products. Neither Google’s nor Amazon’s pages fetched for this article publish a finished “connect our agent to your Workday tenant” guide that matches Workday’s agent endpoint field for field. Kiweely Bridge (coming next) is a third design, for Claude, ChatGPT, and Gemini, and it is not a substitute configuration for Agentspace or Bedrock.
The only shared prerequisite Workday prints
Connect an External Agent with Workday MCP says any platform that supports the protocol can use the same endpoint and the same OAuth credentials. The sentence names Google Agentspace, Amazon Bedrock AgentCore, and Microsoft Copilot Studio. It also says this functionality is for Extend Professionals only.
Workday’s prerequisites on that page, before the outside product matters:
| Prerequisite | What the page says |
|---|---|
| PrerequisiteAgent System of Record | What the page saysSet it up, register the external agent, configure skills, configure security for those skills |
| PrerequisiteAgreement | What the page saysUniversal Main Service Agreement customers already have the feature. Main Service Agreement customers enable it through Innovation Services |
| PrerequisiteProduction registration | What the page saysAbout Workday Agents says registering agents in Production requires opt-in to the UMSA. The same page says ASOR itself needs no additional SKU |
| PrerequisiteEndpoint | What the page sayshttps://{agentGatewayRegionEndpoint}/{tenantName}/mcp, with https://us.agent.workday.com as the example host |
| PrerequisiteToken | What the page saysAuthorize, exchange the code, and use the agent-system-user access token. Access tokens expire after 4 hours. Refresh tokens expire after 30 days. External-agent access-token expiry is not customizable today (agent security) |
| PrerequisiteProof | What the page saysA tools/list call that returns the tools you registered |
| PrerequisiteIdentity | What the page saysDelegate mode is the person plus the agent system user. Ambient mode is the agent system user only. Proxy is not supported |
Workday then says to use the platform’s own documentation for the click-path. That is as far as Workday goes. It does not publish an Agentspace screen list or a Bedrock console list.
Amazon Bedrock AgentCore, from Amazon’s docs
Amazon’s pages fetched on 16 November 2026 do not mention Workday.
What they do publish, on MCP server targets:
- A Bedrock AgentCore gateway can target an MCP server that already has tool capabilities.
- Supported protocol versions listed there include 2026-07-28, 2025-11-25, 2025-06-18, and 2025-03-26.
- Outbound authorization can be none (Amazon says this is not recommended), OAuth, IAM Signature Version 4, or an API key.
- OAuth options on that page are client-credentials (two-legged), authorization-code (three-legged), and token exchange (on-behalf-of). The provider is configured in AgentCore Identity in the same account and Region.
- IAM signing is only for targets that already verify Signature Version 4, such as AgentCore itself, Amazon API Gateway, or Lambda function URLs. A Workday host is not on that list.
- The target URL is encoded and then used as-is for later calls.
Deploy MCP servers in AgentCore Runtime is about hosting your server on AgentCore (ARM64, streamable HTTP, Cognito for inbound callers). It is not a Workday connector.
So the verified Bedrock prerequisite for Workday’s path is the generic one: you have an AgentCore gateway or runtime that can call an external MCP URL with OAuth, and you complete Workday’s agent registration yourself. Amazon does not, on these pages, name Workday scopes, a Workday ISU, or a Workday marketplace listing. If a Bedrock-Workday connector exists elsewhere, it was not on the pages this article used.
Google Agentspace, and the page that is gone
Workday’s admin guide is the source that names Agentspace. A Google Cloud URL that search indexes as “Connect Workday” under Agentspace Enterprise, https://cloud.google.com/agentspace/agentspace-enterprise/docs/connect-workday, returned 404 when fetched on 16 November 2026. This article does not repeat steps from that index. In particular, it does not assert that Agentspace’s current Workday datastore uses an integration system user, a non-expiring refresh token, or a copied list of functional areas.
Until Google republishes a page, the verified Agentspace prerequisite is only Workday’s: treat Agentspace as an external MCP client of the agent endpoint, with Extend Professionals, ASOR registration, and the OAuth client Workday shows once the agent is configured.
What neither page compares: a user-delegated connector
Kiweely Bridge (coming next) does not register an agent in the Agent System of Record and does not use an agent system user. Each employee signs in through Register API Client (authorization code and PKCE). Calls use that worker’s security groups. The published assistants are Claude, ChatGPT, and Gemini, not Agentspace and not Bedrock. Reads are the default. Writes that an admin enables stop for a browser card outside the chat. The company price is a flat band by licensed employees ($499, $1,499, or $3,999 per month, quote above 20,000), with unlimited calls, and it is not a Flex Credit meter.
| Agentspace via Workday’s agent endpoint | Bedrock AgentCore via the same endpoint | Kiweely Bridge (coming next) | |
|---|---|---|---|
| Who names the link | Agentspace via Workday’s agent endpointWorkday’s external-agent page | Bedrock AgentCore via the same endpointWorkday’s external-agent page. Amazon’s fetched pages do not name Workday | Kiweely Bridge (coming next)Bridge’s own pages |
| Vendor setup fetched this session | Agentspace via Workday’s agent endpointThe indexed Google Workday article returned 404 | Bedrock AgentCore via the same endpointGeneric MCP target: OAuth, API key, or IAM. No Workday fields | Kiweely Bridge (coming next)Published: one connector URL, employee sign-in on Workday |
| Workday identity | Agentspace via Workday’s agent endpointAgent system user | Bedrock AgentCore via the same endpointAgent system user, if you follow Workday’s page | Kiweely Bridge (coming next)The employee |
| Workday commercial gate | Agentspace via Workday’s agent endpointExtend Professionals; UMSA opt-in to register agents in Production | Bedrock AgentCore via the same endpointSame Workday gate | Kiweely Bridge (coming next)No Workday AI agreement, per the Bridge FAQ |
| ChatGPT | Agentspace via Workday’s agent endpointNot stated on the Workday sentence that lists Agentspace | Bedrock AgentCore via the same endpointNot stated | Kiweely Bridge (coming next)Named, with Claude and Gemini |
Frequently asked questions
Can a Bedrock agent call Workday with an integration system user?
Not on the evidence used here. Workday’s external-agent page tells you to use the agent-system-user OAuth client from agent configuration. Amazon’s gateway page allows client-credentials OAuth in general, which is a different grant from a named Workday integration user. This article does not invent a supported ISU recipe for Bedrock.
Is Agentspace the same product as connecting Gemini to Workday?
Workday’s external-agent page lists Google Agentspace. Kiweely Bridge’s pages list Google Gemini as an assistant employees already use. Those are different sentences. Do not treat a Gemini chat connector as proof of an Agentspace datastore, or the reverse.
What should we do if we need Agentspace or Bedrock specifically?
Follow Workday’s external-agent setup, then the live console docs for that vendor, and ignore any 404. For Claude, ChatGPT, and Gemini under each employee’s own Workday sign-in, register interest in Kiweely Bridge. It is coming next.