---
title: "How do you build an AI agent in Workday? Developer Agent…"
description: "Workday's documented way to build a custom agent: Developer Agent in App Builder, validate, deploy, activate in the Agent Registry, test in Agent Chat."
url: https://kiweely.com/guides/workday-build-flowise-agent-builder
---

# How do you build an AI agent in Workday? Developer Agent, App Builder and Flowise

Workday now documents one path for building a custom agent: describe it to Developer Agent in App Builder, validate, deploy to your tenant, activate it in the Agent Registry for a security group, then test it in Agent Chat. Workday’s Workday Build page no longer mentions Flowise.

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

Describe the agent to Developer Agent in App Builder, review and apply what it generates, select **Validate**, then **Save and Deploy** to your tenant. In the tenant’s Agent Registry, turn the agent on, make it available to a security group and activate it, then test it from Agent Chat. Workday walks through exactly this in its activity “Build an AI Agent in Workday”, which runs on a free personal developer tenant.

## What has changed since Workday Build launched

When Workday Build launched in September 2025, Workday presented Flowise Agent Builder, a low-code tool built on the open-source Flowise project it had acquired, as the way to build agents. That is no longer the documented path. Workday’s developer site now has a step-by-step activity, “Build an AI Agent in Workday”, in which Developer Agent writes the agent for you inside App Builder. Workday’s current Workday Build page describes building agents “in plain language using your preferred agentic development tool” and does not mention Flowise.

On availability, Workday’s own pages disagree. Its 13 October 2026 announcement says Agent-Ready Tools, Custom Agents and Developer Agent “are generally available in Workday Extend AI”. Its Workday Build page still says building custom agents with Developer Agent is available to early access customers. Workday also renamed the Extend Professional tier to Extend AI in its developer documentation in October 2026. Check with your Workday account team which of these applies to your company’s tenants.

## What you need

-   **An account on the Workday developer site** and a development tenant. Workday’s activity uses a free personal account: create it at developer.workday.com, open **Console > Tenants** and select **Create Tenant**. The activity says this takes 1 to 2 minutes, then you set the tenant password from an email.
-   **The sign-in for the tenant.** You sign in as `lmcneil`, the persona Logan McNeil, a fictional Vice President of Human Resources. The tenant holds mock workers, data and business processes for testing.
-   **For a company’s tenants, Workday Extend AI.** In the activity, the agent’s **Model** field is set to **Auto - Base**; Workday says that with an Extend AI subscription you can choose other large language models.

## The steps, as Workday documents them

1.  **Create the agent.** On the Workday Developer Platform home page, select **Build Custom Agents**, then **Build with Developer Agent**. Name it, then select **Create and Build with Developer Agent**. This opens App Builder.
2.  **Connect App Builder to your tenant.** Select **Connect to Tenant**, choose your tenant alias and sign in. A green dot by the Manage Tenant Connections icon means you are connected.
3.  **Describe the agent.** In **What do you want to build?**, give Developer Agent the goal and functional requirements in plain language. Workday’s example asks for a talent profile snapshot built from a worker’s skills, education, job history and performance. Developer Agent generates an Agent component (description, system prompt, guidelines) and one or more Skills files.
4.  **Review and apply.** Read the generated components in the Components panel, select **Apply Changes**, choose the components and confirm.
5.  **Name it consistently.** The name in the Agent Definition must match the agent’s name in the Components panel.
6.  **Validate.** Select **Validate** at the top of App Builder and fix anything it reports. Workday notes that because the output comes from AI, an error is possible even when none is expected, and suggests asking Developer Agent to fix it.
7.  **Deploy.** Select **Save and Deploy**, choose your tenant alias and **Deploy to Tenant**.
8.  **Activate it in the Agent Registry.** From **View Agent Registry**, open the agent, select **Configure Agent**, turn on **Status**, choose who it is **Available To** (a security group; the activity uses HR Administrator) and select **Activate**.
9.  **Test it.** In the tenant, open Agent Chat from the top-right corner, pick your agent and ask it the question it was built for.

The Agent Registry is part of Workday’s Agent System of Record, which Workday describes as the place to register, configure, monitor and manage Workday-built, partner-built and third-party agents.

## A sensible first agent

Pick something narrow and read-only that you can judge right or wrong at a glance: an agent that answers one question a person now answers by opening a report or a task. Workday’s talent profile example is that kind of agent. An agent that changes data needs the review a person taking the same action would get: which security group it acts for, which business process or validation catches its mistakes, and what happens when it is wrong.

The **Available To** setting is where that starts. The activity makes the agent available to one security group. Give a first agent the smallest group that needs it, and widen it only once you have read what it actually returned.

## Test it before anyone else uses it

Validate and Deploy prove that the agent is well formed and installed, not that its answers are right. Test it the way you test any Workday build: in a development or Sandbox tenant, as the people who will use it, with the questions they will really ask, including the ones it should refuse. Read what it returned, not just whether it ran. If you already have a testing routine for Extend apps, add agents to it rather than starting a separate one.

## Where this connects

If people are already asking an outside AI assistant about Workday data, [connecting Claude or ChatGPT to Workday](https://kiweely.com/blog/connect-claude-chatgpt-to-workday) covers the routes and credentials involved. For the stages an Extend build passes through before Production, see [testing a Workday Extend app before promoting it](https://kiweely.com/guides/workday-extend-testing).

## Sources checked

-   [Workday Developer Site: Build an AI Agent in Workday](https://developer.workday.com/documentation/GUID-e0052175-0a0f-407b-999b-d278ba15bab7-enHYPHENus/BuildanAIAgentinWorkday)
-   [Workday: Workday Build developer platform](https://www.workday.com/en-us/ai-platform/developer-platform.html)
-   [Workday: Agent System of Record](https://www.workday.com/en-us/artificial-intelligence/agent-system-of-record.html)

## Related guides

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

### More guides on Custom agents and Workday AI

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

-   [Why use Kiweely Vine when Workday has its own agents?](https://kiweely.com/guides/workday-own-agents-vs-kiweely-vine)
-   [How to Use an AI Agent for Workday Testing (Step-by-Step Guide)](https://kiweely.com/guides/how-to-use-ai-agent-for-workday-testing)
-   [Workday Implementation Phases: Workday’s Own Stages, and What Stays Manual vs What an AI Agent Does](https://kiweely.com/guides/workday-implementation-phases)
-   [Deployment Agent Users domain and View Security for Agent Skill](https://kiweely.com/guides/workday-deployment-agent-users-domain-security)
-   [Deployment Agent prompt patterns: in my tenant and CRAFT](https://kiweely.com/guides/workday-deployment-agent-prompt-patterns)
-   [Deployment Agent Configuration Catalog Support for Implementers](https://kiweely.com/guides/deployment-agent-configuration-catalog)
-   [Workday Custom Agent First POC Checklist for Implementers](https://kiweely.com/guides/workday-custom-agent-first-poc-checklist)
-   [Workday Developer Agent and Agent-Ready Tools for Implementers](https://kiweely.com/guides/workday-developer-agent-and-agent-ready-tools)

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

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

-   [Cursor for Workday Extend: Developer Agent vs Kiweely Vine](https://kiweely.com/blog/cursor-workday-extend-developer-agent-vs-kiweely)
-   [Workday Build vs Developer Agent vs Vine for consultants](https://kiweely.com/blog/workday-build-vs-developer-agent-vs-vine-for-consultants)
-   [How do I connect Microsoft 365 Copilot or Copilot Studio to Workday?](https://kiweely.com/blog/microsoft-copilot-workday-connector-options)

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