---
title: "Google Agentspace and Amazon Bedrock Agents Calling…"
description: "What Workday, Google, and Amazon publish about Agentspace and Bedrock AgentCore calling Workday, and what those pages leave out."
url: https://kiweely.com/blog/agentspace-bedrock-workday-prerequisites-compared
---

# Google Agentspace and Amazon Bedrock Agents Calling Workday: Prerequisites That Are Actually Published

Workday’s admin guide names Google Agentspace and Amazon Bedrock AgentCore as clients of the same agent endpoint and OAuth credentials. Amazon’s AgentCore docs describe generic MCP targets, not a Workday connector. A previously indexed Google Agentspace Workday page returned 404 on 16 November 2026.

-   By Kiweely
-   November 16
-   5 min read

Google Agentspace and Amazon Bedrock Agents Calling Workday: Prerequisites That Are Actually Published

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](https://kiweely.com/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](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/external-agents/connect-an-external-agent-with-workday-mcp.html) 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 |
| --- | --- |
| Agent System of Record | Set it up, register the external agent, configure skills, configure security for those skills |
| Agreement | Universal Main Service Agreement customers already have the feature. Main Service Agreement customers enable it through Innovation Services |
| Production registration |  [About Workday Agents](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/setup-considerations--agent-system-of-record.html) says registering agents in Production requires opt-in to the UMSA. The same page says ASOR itself needs no additional SKU |
| Endpoint | `https://{agentGatewayRegionEndpoint}/{tenantName}/mcp`, with `https://us.agent.workday.com` as the example host |
| Token | Authorize, 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](https://doc.workday.com/admin-guide/en-us/workday-ai/agent-security/concept--agent-security.html)) |
| Proof | A `tools/list` call that returns the tools you registered |
| Identity | Delegate 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](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-MCPservers.html):

-   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](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html) 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](https://kiweely.com/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 | Workday’s external-agent page | Workday’s external-agent page. Amazon’s fetched pages do not name Workday | Bridge’s own pages |
| Vendor setup fetched this session | The indexed Google Workday article returned 404 | Generic MCP target: OAuth, API key, or IAM. No Workday fields | Published: one connector URL, employee sign-in on Workday |
| Workday identity | Agent system user | Agent system user, if you follow Workday’s page | The employee |
| Workday commercial gate | Extend Professionals; UMSA opt-in to register agents in Production | Same Workday gate | No Workday AI agreement, per the Bridge FAQ |
| ChatGPT | Not stated on the Workday sentence that lists Agentspace | Not stated | 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](https://kiweely.com/bridge). It is coming next.

## Read next

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

-   [November 16 ### Microsoft Copilot Studio and Workday: Agent Gateway vs. User-Delegated Bridge](https://kiweely.com/blog/copilot-studio-workday-agent-gateway-vs-user-delegated-bridge)
-   [November 16 ### Workday BP Optimize Agent vs a consultant redesigning business processes](https://kiweely.com/blog/workday-bp-optimize-agent-vs-consultant)
-   [November 15 ### When Claude Code Should Call Developer Agent vs Stay Offline on Extend Source](https://kiweely.com/blog/when-claude-code-calls-developer-agent-vs-stays-offline)

### More guides on Custom agents and Workday AI

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

-   [One Developer Agent Ask Can Cost Hundreds of Invocations](https://kiweely.com/guides/developer-agent-invocations-can-be-hundreds)
-   [Who Owns the Flex Credit Overage When a Workday Custom Agent Loops?](https://kiweely.com/guides/who-owns-flex-credit-overage-when-custom-agent-loops)
-   [Install Workday Developer Agent in Claude Code, Cursor, or VS Code](https://kiweely.com/guides/install-workday-developer-agent-claude-code-cursor)
-   [Flex Credit Alerts That Reach People Who Can Stop a Workday Agent](https://kiweely.com/guides/flex-credit-alerts-who-can-stop-workday-agents)
-   [Workday Flex Credits in Non-Production: What Is Free and What Still Costs](https://kiweely.com/guides/workday-flex-credits-non-production-what-still-costs)
-   [What Is Workday Agent Passport and How Do Admins Audit or Stop an AI Agent?](https://kiweely.com/guides/workday-agent-passport-governance-explained)
-   [What Workday’s Deployment Agent Can and Cannot Do in Your Tenant](https://kiweely.com/guides/workday-deployment-agent-tenant-inspection)
-   [What Workday Admins Need to Configure Before Turning On Sana Self-Service Agent](https://kiweely.com/guides/workday-sana-self-service-agent-admin-setup)

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