--- category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend] keyword: [Integrate, Workday Integration, Orchestrate for Integrations, Orchestration, Orchestration Builder] nav: wcp_docs parent_url: /wcp_docs/ title: >- Concept: Triggering Integrations layout: subsection --- Orchestration Builder's Trigger Integration component enables you to configure and execute integrations in your Workday tenant. An integration that you trigger in this way is said to be a child of the orchestration that calls it. Specifically, the component enables you to: - Invoke an integration of these types: - Workday Studio. - Orchestrate. - Packaged. - Create expressions that provide launch parameter values and an input document to the child integration. - Gain post-processing access to integration status information, integration messages, and any integration event attachments from the child integration. After triggering the child integration, the orchestration pauses its own execution. The child integration runs asynchronously and when it completes sends a callback to Orchestrate, indicating its status and providing output data or results. The orchestration then resumes execution. It can now provide the child integration's status information, PIMs, and documents as outputs of the Trigger Integration step. The parent orchestration can pass a single document to the child integration. Validation occurs to ensure the user launching the orchestration can access the document. Orchestrate ensures that the document is accessible by the child integration. The child integration has no access to other documents created or processed by the parent orchestration. It only has access to the single document that the orchestration explicity passes to it, and to any documents that it creates itself. Benefits The Trigger Integration component facilitates: - Multi-step processes: Chaining integrations so the output of one becomes the input for the next. - Conditional logic and data-driven workflows: Executing integrations based on results from previous steps. - Error handling and fallback: Because it provides access to the child integration's status, the component enables you to handle errors in the event of integration failure. - Data transformation and enrichment: Combining, transforming, and enriching data across multiple integrations. - Reusing existing integrations: Leveraging existing custom or Workday-delivered integrations to reduce development effort and improve quality. Points to Note Some limitations and behaviors to bear in mind: - Supported child integration types: The component can currently trigger packaged, Workday Studio, and orchestration integration system types. There is no support for EIBs. - Supported orchestration types: The component is currently for use with the Workday Integration System orchestration template type only. - Placement: You can place the component in the top-level workflow, in error handlers, in branches, in loops, in batch loops, or in suborchestrations. You can't use it in join loops. - Tenant and integration system binding: When configuring the component, you can connect to a tenant and link an integration system to enable parameter discovery and configuration. However, it's not required that the integration system be available on the tenant as you have the option of manually configuring the step. - Parameter refresh behavior: You can use the Refresh Launch Parameters function to reset default values back to those provided by the child integration system. Doing so has no effect on any custom parameters you added or on imported parameters whose values subsequently changed. - Input document requirements: When you pass a document to a child integration, you must complete the required fields on the Document tab, that is, Document to Store, Document Title, and Storage Expires In. Failing to complete them results in validation errors - Retry behavior: Like other components, Trigger Integration provides retry mechanisms. It's important to note that these mechanisms only support retry on failure to trigger the integration, not on failure of the integration itself. If you want to automatically relaunch a failed child integration, configure an appropriate error handler. - Tags: You can add descriptive tags to help categorize a document you're passing to the child integration, but those tags are only valid if they already exist in the tenant. ### Related Information [Reference: Trigger Integration](/wcp_docs/GUID-cb68f51e-56ce-4159-b450-5b5ede1caf59.html)