Skip to content
KiweelyKiweelyKiweely

When Workday Integrations Should Leave the Tenant

Stay in Workday’s tools when a connector, a simple EIB, or an Orchestrate flow matches the job. Leave when the other system’s file rules, volume, or release ownership sit outside those tools.

  • Checked against Workday on
  • Applies to Workday Extend
  • 10 min read
  • Published
  • By Kiweely
On this page
When a new Workday integration should leave the tenant

Leave the tenant when the integration’s real specification lives in another system, and Workday’s tools would only be transporting a file those tools do not own. Stay in the tenant when Enterprise Interface Builder, a Cloud Connect template, Workday Studio, or Workday Orchestrate already matches the job Workday’s own pages describe. Kiweely Roots is an outside platform aimed at the first case. It is coming next. This guide is the decision, using Workday’s documentation. It does not depend on Roots existing.

“Leave the tenant” means the integration does not run as an EIB, a connector template, a Studio assembly Workday hosts, or an Orchestrate app launched by an integration system. It does not mean the design tool is installed on a laptop. Studio already is that, and Workday is explicit: the IDE is not part of Workday, and Workday hosts and runs the integration you upload.

What staying in the tenant looks like

Workday’s integrations course ranks the in-tenant choices from guided to fully custom.

Stay here Workday’s condition Leave when
Stay hereEIB Workday’s conditionSimple inbound or outbound, without programming. Often fed by a custom report exposed as a web service. Leave whenThe flow needs branching, several external systems, or a format the wizard will not produce.
Stay hereCloud Connect, including end-to-end connectors Workday’s conditionWorkday builds and supports the template. You configure fields, destination, file name, maps, and transformations. For benefits, end-to-end connectors exist so you can meet a provider’s functions without extra transformation. Workday says it maintains and tests those templates each release and updates them when the endpoint’s requirements change. Leave whenThe endpoint is not in the catalog, or you cannot wait for Workday’s template update when the provider’s companion guide changes.
Stay hereDocument Transformation Workday’s conditionYou need to reshape another connector’s output or input, still on a template. Leave whenThe reshape is really a new integration.
Stay hereStudio Workday’s conditionThe integration is custom, exchanges bulk data, needs a specific format, or needs unit tests on the XML. Workday recommends Preview Sandbox before Production. Leave whenYou do not have people who will own and support the assembly, which Workday says is your job.
Stay hereOrchestrate Workday’s conditionReal-time, transactional, decision-driven flows, minimal code, on the Developer Site, launched by an integration system. The education manual says this tool is not the one for large batch jobs. Leave whenThe payload is a large batch file, or you need an operating model the builder does not include.

Orchestrate’s product marketing also lists high-volume batch as a capability. The education manual says the opposite about large batch. Until those two Workday pages agree, do not move a full-population nightly file onto Orchestrate on the strength of the marketing line, and do not refuse Orchestrate for a modest file on the strength of the manual alone. Ask the account team which runtime you are subscribed to run.

The tests that say “stay”

Stay when every answer below is yes.

The endpoint is one Workday already templates, and the template’s file is the file the endpoint accepts. The benefits course is the clearest case. End-to-end connectors align each system’s business functions without additional coding or document transformation. If a carrier is in that catalog, building a second integration outside the tenant duplicates a template Workday has said it will maintain. Leaving is justified only by a requirement the template does not implement, not by taste.

The integration is simple enough for EIB. Programming is the line Workday draws. If you are about to write code, you have already left EIB. You have not yet left the tenant. Studio and Orchestrate are still in Workday’s toolset.

Your team will own a Studio assembly, and Preview Sandbox is a habit. Workday’s words are “build, own, and support.” The setup page tells you to deploy and test in Preview Sandbox before Production. The tenant datasheet describes Sandbox as a weekly copy of Production and Sandbox Preview as a twice-yearly refresh that receives new functionality first. A team that uses those tenants has the test gate. An outside platform is not required to obtain Sandbox. It is required only if you also want a different owner for the repair.

The flow is a workflow, and Orchestrate’s access path is open. Access Orchestrate for Integrations ties availability to the subscription agreement. Universal Main Service Agreement customers are told the feature is already there. Main Service Agreement customers opt in through Innovation Services, on the Workday Orchestrate for Integration checkbox, and then name a Developer Site administrator. The app lifecycle is Implementation, then Sandbox, then Production. That is a complete path. Use it when the flow matches the tool.

The data should remain an integration event inside Workday. Security administrators already know how to permission integration events. Studio’s logging course tells developers not to put the raw message on that event in production. If your audit story is “look at the integration event,” staying keeps one story. An outside platform creates a second run record. That is worth it only when the second record stores something the event does not, or stores less.

The tests that say “leave”

Leave when any of these is the actual problem, not a preference for a new tool.

The other system’s companion guide is the specification, and it changes between Workday releases. Workday will update an impacted end-to-end template. Workday will not, on the pages read for this guide, rewrite your Studio map on the Tuesday a provider adds a required element. If you are not on a template, the map is yours. An outside platform is a way to put that repair somewhere other than a single developer’s IDE. It is not magic. Kiweely Roots, coming next, says the agent finds the change, fixes it, and tests it on Sandbox, and that payroll, benefits, and tax wait for approval. That is a published operating model. It is not available to switch on today. Until it is, leaving the tenant means your team runs that operating model on whatever host you choose.

The file is large, and Orchestrate’s education limit applies. The manual says Orchestrate is not suitable for large batch data jobs and points those jobs at Studio. Studio is still inside Workday’s hosting. You leave the tenant for batch only if you also need a runtime Workday is not hosting — for example a process that must use your network to reach a partner that will not accept Workday’s delivery step. Confirm that constraint. “We prefer our own workers” is not the constraint. “The partner’s allow-list and our private connectivity require the client to run in our cloud” is.

You need one place for payroll, benefits, identity, and the SFTP file a partner still requires. EIB can do each hop. It will not give you one rule for which hops may repair themselves. Roots’ page is written as that one place, and names payroll providers, benefits carriers and 834 files, identity providers, NetSuite, Snowflake, and SFTP. If your estate is one of those hops and a template exists, stay. If your estate is all of them and the failure modes differ, a single outside operating model is the point of leaving. Mixing them across four EIBs and one Studio assembly is how the payroll file and the directory file end up with the same person’s inbox and no distinction.

Workday’s integration status is the wrong definition of success. A completed delivery means the file reached the endpoint Workday was configured to call. The benefits testing chapter separates connectivity testing from file-format testing. A file can be delivered and still have blank required fields or codes the provider rejects. If your operators treat the integration event as the business result, you have a monitoring gap. You can close that gap inside Studio with error handlers and a cloud log. You leave the tenant when you want the other system’s acceptance, not Workday’s event, to be the thing that is tested and acted on. The companion guide on delivered versus rejected is the Workday detail.

The integration has to call Workday’s APIs as a client, not run inside Workday’s integration runtime. The integrations course says you can access the APIs directly or use Workday’s tools. Direct access is the outside path Workday already contemplates. Roots’ page says each integration has its own API client, scoped to what it reads. That is the same hygiene you would demand of any external client. Leaving is not a bypass of security. A client with a broad scope is worse than an integration system with a narrow domain, wherever it runs.

A sequence that keeps you from moving the wrong integration

  1. Search the connector catalog, not your architecture diagram. If an end-to-end template matches, proof that template against the provider’s file before you design anything else. Workday’s benefits testing cycles — connectivity, file format, data and events — are the proof.
  2. If there is no template, decide whether the work is a simple file. If it is, prototype the EIB. Stop if the wizard holds.
  3. If it needs logic and the volume is transactional, check Orchestrate access for your agreement type and prototype on the Developer Site. Promote to a non-production tenant before you believe it.
  4. If it needs a custom bulk transform, estimate Studio with the ownership sentence in view: your team supports it, and Preview Sandbox comes before Production.
  5. Only then ask whether the ongoing repair, the acceptance test at the other system, or the place the process must run is outside what those tools do. That is the leave decision.
  6. If you leave, write down what the external run record will store. Workday’s event already stores status, messages, and output files. An external record that copies the file has created a second copy of worker data. Roots’ rule, when you are evaluating it, is the opposite: times, counts, and outcomes, and the rows deleted at the end of the run.

What leaving does not fix

Leaving does not remove Workday’s release. Sandbox Preview still receives functionality first, and a client you wrote against an API still has to be retested there. The tenant datasheet’s reason for Sandbox Preview — see what is coming before Production — applies to an external client as much as to a Studio assembly.

Leaving does not remove the weekly Sandbox refresh. External credentials configured against Sandbox still have to survive that refresh. Workday’s eSignature guidance is a specific example of production credentials that cannot be reused in Sandbox and of a setup that must be redone after refresh. Plan the same for any external client.

Leaving does not skip the integration system if you are still launching Orchestrate. An external platform that calls APIs is a different design from an orchestration the tenant launches. Do not do both for the same feed unless you have a reason to reconcile two writers.

Leaving does not, by itself, give you an agent. Roots is the product that specifies agents for design, test, and repair, with code on the path, and it is coming next. An external Python job is a leave decision with none of that operating model. Be sure which one you are choosing.

A short list you can take to a design review

Integration you are about to build Default Leave only if
Integration you are about to buildProvider already in Cloud Connect DefaultStay on the template Leave only ifThe template’s output fails the provider’s current companion guide and you cannot wait for Workday’s update
Integration you are about to buildOne report, one file, little logic DefaultEIB Leave only ifThe destination’s rules no longer fit the wizard
Integration you are about to buildCustom bulk file, team in place DefaultStudio, Preview Sandbox first Leave only ifThe runtime must run in your cloud, or you will not staff the assembly
Integration you are about to buildAPI workflow, modest volume DefaultOrchestrate, if your agreement includes it Leave only ifThe education manual’s batch limit matches your file and Studio is the in-tenant alternative
Integration you are about to buildMany surrounding systems, repairs tracked by vendor acceptance DefaultConsider an outside platform Leave only ifYou only have one feed and a template already fits

Register interest in Kiweely Roots if the last row is the one you are actually on and you want the repair model on that page. Do not register as a substitute for a template you have not checked. The integrations that should leave are a minority. They are expensive because they are the ones Workday’s event calls finished and the other system calls wrong.

Sources checked

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

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