Workday has not published an integration-design workshop. It has published an order for choosing the tool, four APIs, and a Deployment Agent pattern for reading a SOAP fault. Use that order in the room. If the agent names a tool before you have answered the order, ignore the tool name and walk the table.
An integration moves data between Workday and an external system, inbound or outbound, often in bulk, on a schedule or on demand. Workday stores customer data as objects. Web services are the usual way integrations reach those objects. All of that traffic is HTTPS.
Choose the tool in the published order
The integrations course (updated 2026-07-10) tells you to walk down this list and stop at the first row that fits.
Inbound
| Tool | Use it when |
|---|---|
| ToolEnd-to-end connector | Use it whenA template matches the vendor’s file and you do not need to transform it. |
| ToolGeneric connector | Use it whenA template has the elements you need, and the file is XML or CSV. |
| ToolOrchestrate | Use it whenNo package fits. You need events or batches, a transformation, or calls to Workday or a third party. |
| ToolConnector with Document Transformation | Use it whenYou must change an XML input to Workday’s format and you need your own error or warning text. |
| ToolWorkday Studio | Use it whenMany web-service requests per object, processing each object on its own, or complex errors and logging. |
Outbound
| Tool | Use it when |
|---|---|
| ToolEnd-to-end connector | Use it whenA template matches the vendor that receives the file. |
| ToolGeneric connector | Use it whenA template fits and you need change detection. |
| ToolOrchestrate | Use it whenNo package fits, you must call one or more APIs, you need events or batches, or you must transform. |
| ToolConnector with Document Transformation | Use it whenYou must change a core connector’s output, produce several files, produce something other than XML, or write your own error text. |
| ToolWorkday Studio | Use it whenSame reasons as inbound: many requests per object, one-by-one processing, complex errors and logging. |
Connectors sit on SOAP and make the call for you. You do not pick the operation. Studio is where you write SOAP or REST yourself. Studio is an Eclipse-based tool you install; it is not inside the Workday screen the way EIB is. The Studio concept topic describes assemblies: get data, transform it, optionally deliver it. The financial course describes EIB as the wizard for a simple inbound or outbound, with Get Data, Transform, and Delivery. Outbound EIB does not produce Excel. It can produce CSV, which you then open in Excel.
Orchestrate’s data sources, in the overview course, are RaaS, SOAP, and REST, including third-party endpoints. A later Orchestrate course says to picture Orchestrate as the broader tool for custom transformations and batch or real-time exchange, and to keep Studio for complex or specialized work. Where the two courses differ in emphasis, follow the overview’s order for the decision, and treat Studio as the row you reach only when the earlier rows fail. Do not ask an agent to “resolve” that emphasis. Write down which row you stopped on.
The four APIs, so the workshop names one
| API | What the course says |
|---|---|
| APIWorkday Web Services (SOAP) | What the course saysXML. The WSDL describes the operation. A fault you cannot read is a reason to open Deployment Agent, not a reason to change tools yet. |
| APIREST | What the course saysFor a small set of frequently used data, custom objects, and authentication. XML or JSON. |
| APIRaaS | What the course saysA custom report you enable as a web service. You do not hand-write the request. |
| APIWQL | What the course saysA query language the course compares to SQL, lighter than maintaining a custom report, and portable between tenants such as Implementation and Sandbox. The overview course says it is outside that class’s scope, so do not pretend a workshop exercise “did WQL” unless someone ran a query. |
Data Initialization Service is the exception the course calls out: retrieval that does not use those web-service requests, and is typically faster. If someone claims DIS, ask them to show the integration. The agent’s SOAP advice does not apply to a path that never sent SOAP.
Run the workshop on one integration
- Write the direction, the external system, the file or the message, and whether the data is a full set or only what changed. Change detection is a reason the course gives for a generic outbound connector.
- Walk the table until one row fits. Record the row in the decision log. That log is not the chat.
- Name the security the integration system user needs, as domains, not as “admin.” The SOAP example’s follow-up prompt is exactly that question.
- Only then open Deployment Agent in the Implementation, Sandbox, Preview, or Customer Central tenant where the fault happened.
Workday’s worked prompt:
I am an integration consultant working on a Financials implementation. I am calling the Submit_Expense_Report web service and receiving a ‘Validation error occurred’ message regarding a missing field. The error says: ‘The field Expense_Report_Data is required.’ I have confirmed this field is in my XML. What are the most common hidden missing fields or security issues that cause this specific SOAP fault for this service?
Then:
List the specific functional area and security domain permissions my integration system user needs to initiate this specific web service.
The example says the agent often points at a field or a permission and can still be wrong. You check the WSDL material it cites, fix the message or the domain, activate security if you changed it, and launch again. The example’s closing step in the admin guide even points at Create Calculated Field, which is a reminder that the agent’s write-up can mix tasks. Do not create a calculated field because a SOAP fault was the question. Launch the integration and read the event.
Technical troubleshooting is a documented Ask capability: web-service and SOAP errors, and rules or business processes that did not run. Configuration intelligence will also offer steps. Neither capability deploys an assembly or schedules an EIB. There is no badge that Ask is reading your tenant. Say “in my tenant” or name the connected tenant.
What you file the same day
| Decision | Where it lives |
|---|---|
| DecisionTool row you stopped on | Where it livesProject record. |
| DecisionOperation or connector template name | Where it livesThe integration system in the tenant. |
| DecisionDomains granted to the integration system user | Where it livesThe domain policy, after activation. |
| DecisionFault and the child element or permission that was actually wrong | Where it livesThe integration event after the successful retry, not the first chat. |
| DecisionPackage, if this integration is configuration you will migrate | Where it livesObject Transporter, supported objects only. An extract still cannot load straight to Production. |
Chat history lasts 14 days. An integration design that exists only there does not exist.
Failure modes
- Studio chosen because the file “looks hard,” before anyone opened the Integration Template Catalog. The course says to look at templates. End-to-end examples include vendor-specific connectors. Generic examples include Core Connector: Worker.
- EIB chosen for many requests per object and custom error handling. That is the Studio row.
- A REST design for a bulk journal load the financial course would put on an EIB or a connector. REST, in the overview, is the small, frequent set.
- Believing a parent-element fault. Expense_Report_Data required, while present, is Workday’s own illustration of a fault that can hide a child element or a security gap.
- Designing in Production chat. Deployment Agent is not a conversational assistant there. Build in an implementation tenant. The course also says WQL is easy to move between Implementation and Sandbox; the integration system itself still has to be migrated or recreated by the tools that support it.
- Letting the agent schedule the integration. Launch / Schedule Integration is a task you run. Verify the result.
Frequently asked questions
Can Ask draw the integration?
It can explain the fault and the documented steps, grounded in the tenant when Ask is on. The tool choice is the table above. The build is EIB, a connector, Orchestrate, or Studio, done by someone who can open that tool.
Do we need an integration system user in the workshop?
You need to name the domains that user must have, using the follow-up prompt, and then grant them. The workshop should not share the user’s credentials in the chat. The policy is the design.
Where does a business process fit?
Connectors can work with business processes. An integration step on a definition can have an exit condition. If the design is “when the hire completes, send the file,” say whether that is a connector tied to the process or a scheduled extract. Those are different rows.
What if Orchestrate and Studio both seem to fit?
Stop at the first row that fits. Orchestrate comes first in the overview’s order. Studio is for the cases that row cannot cover: many requests per object, processing objects one by one, or logging and errors you cannot get earlier in the list. Write the reason you rejected the earlier rows.
Sources checked
Public Workday course and admin-guide topics listed above, fetched 2026-11-16. No page fetched here describes an integration-design workshop product.