Workday announced Build with a future Agent Builder availability window
Workday announced Workday Build on September 16, 2025, including a Flowise Agent Builder planned for Workday Extend Professional customers in the first half of 2026.
Historical reporting: Workday announced Workday Build on September 16, 2025 and said the Flowise Agent Builder would be available to eligible Workday Extend Professional customers in the first half of 2026. Workday’s same-day developer blog explains that the builder used Flowise technology and described MCP support for Workday APIs. The release is a roadmap and platform announcement, not proof that the builder was available, that a customer agent was deployed or that Workday data could be used without configuration and authorization.
Key takeaways
- Workday Build was announced in September while its Flowise Agent Builder had a first-half-2026 availability window.
- The same-day developer blog described Flowise technology and MCP support for Workday APIs.
- An announced builder is not evidence of a live agent or a completed enterprise deployment.
Workday announced Build on September 16, 2025[source 1]
Workday’s September 16 release introduced Workday Build as a developer platform for customers and partners to create, share and scale AI-powered enterprise solutions. The release names Workday Flowise Agent Builder, data products, developer tooling and an Agent Gateway as parts of the platform direction. This is workplace and enterprise-product news because it connects developer access to HR and finance applications. It does not establish that a custom agent was live on the day of announcement or that an enterprise had approved it to use people or financial data. The release’s availability language defines that boundary.
The release scheduled Agent Builder for the first half of 2026[source 1][source 2]
Workday says the new Flowise Agent Builder would be available to customers with Workday Extend Professional in the first half of 2026. This is a forward availability statement, not a September 2025 launch receipt. The distinction matters for any article about enterprise agents: a product can be announced, demonstrated or documented before a customer can use it under stated access terms. Workday’s same-day developer blog explains that Flowise technology would support visual agent building and management inside Workday, while MCP support was planned for Workday APIs. That technical explanation does not change the feature schedule. A later availability claim would require its own dated evidence.
Workday described developer tools, data and agent connections as separate platform layers[source 1][source 2]
The Build release describes a developer platform that includes applications and data access, a developer copilot, Agent Gateway and a marketplace or partner ecosystem. These are different layers. A data product can make records available under an approved connection; an Agent Gateway can describe a way to connect an agent; a builder can compose a workflow. None by itself tells a reader what an individual agent may do. The announcement is specific about Workday’s intention to open these surfaces. It does not provide a tenant’s access rules, field-level scope, integration credentials or audit evidence for a deployed solution.
Using people and financial context remains a deployment decision after a platform announcement[source 1][source 2]
Workday positioned Build around its existing people and financial application context. That can be valuable for business-specific agents, but it also makes scope and authorization central to adoption. A developer may have access to an API while an agent should have narrower tools, a different identity or a human approval before it changes a record. The release says Workday Build will help customers create and manage agents; it does not establish that an agent’s output is correct, that data is current or that a particular action is safe. The useful historical fact is the September announcement and its stated future availability window, not an implied production outcome. Any later rollout needs an event record that names the access tier, date and enabled features.
Sources
- Workday: Workday Build announcement (September 16, 2025)
- Workday developer blog: Introducing Workday Build (September 16, 2025)
Continue reading
Related reading
News analysisZendesk’s 2025 Resolution Platform joined service agents, knowledge, actions and QA3 min read
News analysisWriter launched AI HQ with a beta Agent Builder and observability tools3 min read
News analysisWorkday signed for Sana’s search, agents and learning products, then completed the acquisition in November3 min read