Skip to content
KiweelyKiweelyKiweely

When to Use Workday Build’s Flowise Canvas vs. Deterministic Extend Orchestrations

Use Workday Build’s Flowise Agent Builder when the outcome needs LLM judgment over Agent-Ready tools under ASOR. Use deterministic Extend orchestrations when the path is fixed: sync page calls capped at 25 seconds, or async work up to 48 hours with explicit steps and callbacks.

  • By Kiweely
  • 4 min read
On this page

Choose Flowise Agent Builder when a worker needs a governed conversational agent that reasons over Agent-Ready tools under Agent System of Record. Choose a deterministic Extend orchestration when every branch is known in advance and must finish inside Workday’s published runtime ceilings. Mixing the two without that split produces agents that invent steps and orchestrations that stall on LLM latency.

Workday Build now spans both styles. Flowise Agent Builder (announced with Workday Build for Extend Professional customers) is the visual canvas for agent graphs. Orchestration Builder remains the path for fixed sync and async step chains inside Extend apps and integration apps.

Decision Table: Agent Canvas vs. Deterministic Orchestration

Question Prefer Flowise / custom agent Prefer Extend orchestration
QuestionDoes the path need LLM judgment or tool selection at runtime? Prefer Flowise / custom agentYes Prefer Extend orchestrationNo: fixed branches and mappings
QuestionIs the primary UI a chat panel, Sana, or A2A/MCP invoke? Prefer Flowise / custom agentYes Prefer Extend orchestrationNo: a PMD page, Home Card, or BP step
QuestionMust the step finish while a page HTTP call stays open? Prefer Flowise / custom agentRarely Prefer Extend orchestrationSync orchestration, 25-second page-trigger ceiling
QuestionCan the work run in the background for hours? Prefer Flowise / custom agentOnly via tools that themselves are async Prefer Extend orchestrationAsync orchestration up to 48 hours
QuestionDo you need custom business objects and PMD pages in the same app? Prefer Flowise / custom agentUse an Extend app (not an Agent app) plus optional agents Prefer Extend orchestrationExtend app with orchestrations attached

Agent apps in App Builder support agents, skills, attributes, and orchestrations, but they cannot include PMD or model components and do not consume Extend app entitlements. Full worker-facing apps still need the Extend app type.

What Deterministic Orchestrations Guarantee

Workday’s orchestration runtime limits are explicit:

  • Synchronous orchestration triggered by a presentation page: 25 seconds (overrides other configured timeouts).
  • Synchronous orchestration duration (Extend apps): up to 5 minutes when not constrained by the page trigger rule.
  • Asynchronous Extend orchestration: up to 48 hours.
  • Integration System orchestration: up to 48 hours.
  • Business process callback window from an orchestration: up to 90 days.
  • Structure caps: 150 orchestrations/suborchestrations per app, 300 steps per orchestration.
text
Page Submit -> sync orchestration
  OK: validate payload, write one business object, return JSON < 25s
  FAIL PATTERN: call three external vendors synchronously and wait

Page Submit -> enqueue async orchestration
  OK: acknowledge immediately, poll or webhook later, BP callback within 90 days

Use Orchestrate Expression Language, grouped steps, and suborchestrations when the map is known. Do not park “decide what to do” inside a sync page call.

What Flowise and Custom Agents Are For

Custom agents follow Build → Register in ASOR → Invoke. Artifacts use .agent and .agentskill files. At runtime, an Agent System User bound to the agent executes allowed tools under the security group you assign in ASOR. Users can reach the agent from Workday’s self-service chat panel, Sana, business process framework, A2A, or MCP. Workday documents these as delegate-mode agents.

Flowise Agent Builder sits on that agent path: a low-code canvas for designing, deploying, and managing agents that consume Workday context through Agent-Ready MCP tools rather than free-form HTTP. External MCP clients can also connect through Workday’s Agent Gateway once ASOR and OAuth setup are complete for Extend Professional tenants.

json
{
  "pattern": "agent",
  "ui": "chat-or-sana",
  "tools": ["agent-ready-mcp", "custom-agent-actions"],
  "governance": "ASOR + ASU audit"
}

That is not a substitute for a PMD intake form with field-level validation and a My Tasks approval. If managers must enter structured compensation exception fields under constrained security, build the Extend page and business object first; attach an agent only where conversation or multi-tool synthesis helps.

Failure Patterns Teams Hit When They Swap the Two

Teams that force Flowise to “just submit the award” usually rediscover why Extend pages exist: field-level validation, effective dating, and constrained security already live in Workday’s presentation and business process stack. An agent that improvises a write through a broad tool grant is harder to audit than a PMD endpoint running as the signed-in worker under SSO.

Teams that force a sync orchestration to “call an LLM and decide” hit the 25-second page ceiling, then blame network latency. Put probabilistic work in the agent layer; keep the page orchestration boring.

text
fails: sync page orchestration that waits on an LLM tool
  - page endpoint timeout / 25s orchestration kill
  - partial writes with no BP audit trail

works: PMD save -> BP approval -> async orchestration
  - optional custom agent answers policy questions only
  - money fields stay on the Extend object and BP

Orchestrate for Integrations remains a third lane when there is no worker UI at all: scheduled or event-driven integration apps talking through the Cloud Platform API gateway. Do not stuff those headless syncs into Flowise merely because the canvas feels newer.

Hybrid Pattern That Stays Honest

A practical split for a mobility or recognition program:

  1. Extend app: PMD pages, .businessobject storage, security domains, and a business process for human approval.
  2. Deterministic orchestration: on approval completion, async steps create downstream tickets or write integration payloads within the 48-hour ceiling.
  3. Flowise / custom agent: optional concierge that answers policy questions using Agent-Ready tools, without owning the money fields.

Availability note for planning: Workday positioned Flowise Agent Builder for Extend Professional customers on a first-half 2026 rollout. Deterministic Orchestration Builder and Extend app limits are already documented on developer.workday.com; design the fixed path first so agent features can land without blocking go-live.

Kiweely Vine builds, validates, deploys, and browser-tests the Extend and orchestration halves against your Development tenant. It does not replace ASOR registration or Flowise canvas authoring inside Workday Build. For films of Extend apps built on camera, see /vine/films. Compare generic chat agents versus Vine on /vine/compare, and read the companion guide on Workday Build Flowise agent builder when you need setup steps rather than the architectural split.

Model component warning

Extend business objects, business processes, and security domains that leave Development deploy through Workday’s Weekly Service Update path and cannot be deleted once promoted. Keep experimental schemas in Development until the object model is settled, whether an agent or a human authored the first draft.

Frequently asked questions

Does Flowise Agent Builder replace Workday Extend presentation pages?

No. Flowise Agent Builder targets custom AI agents. Extend apps still own PMD pages, model business objects, and security domains. Agent apps are a separate app type that cannot include PMD or model components and do not count against Extend app entitlements.

What is the hard timeout for a synchronous orchestration launched from a presentation page?

Twenty-five seconds. That page-triggered limit takes precedence over other timeouts on the orchestration. If the work may run longer, Workday recommends an asynchronous orchestration, which can run up to forty-eight hours.

Can a custom agent call arbitrary Workday REST APIs directly?

Workday's custom agent runtime routes tool calls through dedicated clients such as the MCP client on the Agent Gateway and the Custom Agent Actions client for Orchestrate. It does not allow arbitrary API calls outside those governed clients.

When is Orchestrate for Integrations the better canvas than an Extend app orchestration?

When the workload is a headless integration system event or scheduled sync without worker-facing PMD pages. Extend orchestrations belong beside pages and business objects; Orchestrate for Integrations belongs beside integration apps and Cloud Platform gateway patterns.

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.

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.

We’ll email you once to confirm. Unsubscribe in one click from any issue.