---
category: [Administration & Integrations, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions, Platform and Product Extensions/Workday Extend, Platform and Product Extensions/Integration]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Concept: Integration Events and Integration Process Events
layout: subsection
---

<b>Integration Event</b>

In Workday, an Integration Event is the top-level container for an integration execution within the Integration Framework. Integration Events are often referenced in the user interface. Each one contains:

-   A reference to the job sent to the integration runtime.
-   The status of the integration run.
-   Messages associated with the integration run.
-   Attached documents, also referred to as Output Files.
-   Launch parameters.
-   Initiated and Completed timestamps for the integration run.


An Integration Event may comprise a Main Orchestration Event and 0 or more Child Integration Events.

<b>Integration Process Event</b>

An Integration Process Event provides a sequential view of the Business Process steps configured by the integration's developer. Think of it as the workflow side of the integration. You may see an Integration Process Event referred to as an Integration Event Business Process.

Typically, an integration's Business Process includes service steps, such as Retrieval and Delivery, and integration steps, such as the invocation of other Integration Systems.

The completion of a child integration, which triggers the callback to the parent orchestration, occurs only when the associated Integration Business Process completes execution of the configured steps.

In essence, an Integration Event is the wrapper for an integration run in Workday, while an Integration Process Event is the actual Business Process execution that defines and performs the steps involved in that run. Every Integration Event has an Integration Process Event.