Skip to content
KiweelyKiweelyKiweely

Orchestrate, an iPaaS, or Kiweely Roots

Orchestrate for Integrations is Workday’s own low-code product and its own SKU. An external platform sits outside the tenant. Kiweely Roots, coming next, is the third path: agents build and maintain the integration, and the run is tested code.

  • By Kiweely
  • 5 min read
On this page

The three ways to connect Workday to another system are easy to blur, because all three can move a file or call an API. They are not substitutes. Workday Orchestrate runs inside Workday’s platform. An integration platform you already operate runs outside it, with Workday as one system among others. Kiweely Roots (coming next) is also outside the tenant, and the agent builds and maintains the integration with you.

Pick per integration. A tenant can use all three.

What Workday’s own pages say about Orchestrate

The product page describes a low-code visual builder, real-time integrations, high-volume batch, monitoring, transformation, cross-application workflows, and connections to application APIs. Event-driven runs trigger a sequence in Workday or in a connected system. Batch runs handle full files and large API payloads. Workday says existing security controls and audit policies are enforced because Orchestrate is part of the Workday platform. The platform overview says you can build these integrations with no separate middleware, and it still lists Enterprise Interface Builder and Workday Studio beside Orchestrate.

The course material is more specific than the marketing page, and the two should not be flattened.

There are two products. Orchestrate for Integrations adds pieces Orchestrate for Extend does not have: a Workday report request, triggering a business process, triggering an integration, PDF generation, storing documents on the integration event, logging to a file, and adding an integration message. Orchestrate for Extend is the one with synchronous and asynchronous runs and with Amazon Web Services components the integrations product does not include. The same course says Studio remains the tool for complex or specialized requirements, and that a delivered connector is still right when you do not need a transformation.

The Orchestration Builder course says customers who buy the Orchestrate for Integrations SKU do not get Development tenants unless they also buy Workday Extend. Sandbox tenants are refreshed every week with production data. Promotion deadlines that apply to Extend apps do not apply to integration apps. An older Workday blog says Workday Orchestrate is included with every Extend subscription. Read that as the Extend product, not as “the Integrations SKU is free with Extend.” The course is the page that separates the SKUs.

Developer Agent is a third fact, and Workday’s pages do not agree with each other. The Developer Agent page says it is generally available starting with 2026R2, through Workday Extend Professional, with Flex Credits-based pricing, and that it builds apps, agents, and orchestrations from plain language. The platform FAQ still says building custom AI agents with Developer Agent is available to early access customers. Quote the page you were shown. Do not collapse those two sentences into one availability claim.

A failed integration step, on the integration business process, stops the parent process and is handled by a person, with Process Monitor and notifications. That page does not describe an agent that repairs the integration.

The other two columns

An external integration platform is the one your company already runs for systems that are not Workday. This article does not assign features to MuleSoft, Boomi, or Workato. Those products change, and a feature that is not on the vendor’s page this week does not belong in the matrix. What you can say without their pages is only the shape: the flow runs outside the Workday tenant, your team owns it, and Workday is one connector in a landscape that also has everything else.

Roots is the column with a published spec. It is coming next. There is no price on the page.

Question Orchestrate for Integrations An external platform you already run Kiweely Roots (coming next)
QuestionWhere it runs Orchestrate for IntegrationsOn Workday’s platform, in the tenant’s integration tooling An external platform you already runOutside the tenant, on that platform Kiweely Roots (coming next)Outside the tenant. Kiweely’s cloud, or your AWS, Azure, or Google Cloud
QuestionHow it is built Orchestrate for IntegrationsLow-code builder. Developer Agent’s availability depends on which Workday page you read, and it requires Extend Professional on the Developer Agent page An external platform you already runYour team, or whatever generator that vendor currently documents Kiweely Roots (coming next)The agent designs, builds, and tests from what you describe
QuestionWhat moves the data Orchestrate for IntegrationsThe orchestration you deployed An external platform you already runThe flow you deployed Kiweely Roots (coming next)Tested code. Agents are not in the path of the data
QuestionWorkday license Orchestrate for IntegrationsIts own SKU. Development tenants also need Extend An external platform you already runWhatever that vendor’s Workday connector requires. This article does not state an Extend rule for it Kiweely Roots (coming next)Standard Workday APIs. The Roots page does not require Workday Extend
QuestionWhen a run breaks Orchestrate for IntegrationsThe business process stops and a person handles the error An external platform you already runWhatever that platform does. Not claimed here Kiweely Roots (coming next)Finds the cause, fixes and tests it, then ships or asks, by your rule. Payroll, benefits, and tax wait for approval
QuestionWhat is kept Orchestrate for IntegrationsWorkday’s own event, documents stored on the event, and logs the course says you can write An external platform you already runThat platform’s logs Kiweely Roots (coming next)Nothing after the run except times, counts, and outcomes
QuestionAsking from Claude, ChatGPT, or Gemini Orchestrate for IntegrationsWorkday documents agent access to Workday data through other products. The Orchestrate integrations course does not say those assistants can operate the integration An external platform you already runOnly if that vendor says so Kiweely Roots (coming next)Yes. Those assistants reach Roots over MCP, as the person asking

How to triage one integration

Use the first row that matches. Stop.

  1. The integration has to be a step on a Workday business process, and a failure must stop that process. Use Orchestrate for Integrations or the integration business process you already have. Roots does not claim to be a step inside a Workday business process.
  2. You need a Workday-delivered connector and no transformation. The Orchestrate course says to keep the connector.
  3. The same team already runs a platform for a dozen non-Workday systems, and this flow is one more of those. Keep it there if the people who will be on call are that team.
  4. The integration is Workday plus one other system, you want it built from a description, tested on Sandbox before anything reaches Production, and you want the break fixed without a Studio redeploy. That is the Roots column. Payroll, benefits, and tax still wait for your yes. Directory and reporting feeds can go back on and tell the owner.
  5. The security review forbids a retained copy of the payload. Roots is the column that publishes that rule. Confirm the host at the same time: Kiweely’s cloud or yours.

Register interest on the Roots page with the integration you would put in row 4. Roots is coming next. Orchestrate is a Workday product you buy from Workday. This page does not resell it.

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.