Published at: 2026-10-12
Overview
Learn the orchestration model of integration flows, Triggers, Actions, components, and data transformation.
Overview
An integration flow describes how business data moves between multiple systems. A typical integration flow consists of one Trigger and one or more Actions.
Core Concepts
The System Integration Platform uses the unified Trigger + Action workflow model:
Concept | Meaning |
|---|---|
Trigger | Defines when the flow starts |
Action | Defines what the flow does after it starts |
Component | A reusable building block that can be orchestrated inside an integration flow |
Data Transformation | Transforms dates, amounts, enums, and codes |
Integration Flow Orchestration Model
The System Integration Platform uses the unified Trigger + Action workflow model. The Trigger defines when the flow starts, and the Action defines what the flow does after it starts.
The advantages of this model include:
- Makes the flow structure easier for implementation consultants to understand
- Makes complex logic easier for technical consultants to break down
- Makes it easier to abstract API capabilities into reusable actions
- Makes future debugging, troubleshooting, and maintenance easier
- Makes it easier to accumulate typical integration scenarios into templates
Components
A component is a reusable building block that can be orchestrated inside an integration flow. Common components include:
- HTTP Component
- Conditional Component
- Field Mapping Component
- Data Transformation Component
- Enum Conversion Component
- Loop Processing Component
- Exception Handling Component
- Notification Component
- Logging Component
Orchestration for Complex Business Processes
Traditional data integration mostly handles point-to-point synchronization, while the System Integration Platform supports more complex business process orchestration. Typical capabilities include multi-step flows, multi-system coordination, multi-object synchronization, conditional logic, and branching. It also supports data transformation, field mapping, exception handling, retry mechanisms, and log tracing.
Action Atomicity
The platform breaks down common API capabilities and flow capabilities into composable actions, such as query, create, update, conditional, transform, notify, retry, and exception logging. Implementation consultants can orchestrate flows freely based on these actions, reducing dependency on R&D customization for simple logic and common synchronization scenarios.