Understand how a pipeline is built.
The Digibee Integration Platform has the pipeline as main piece, which is a sequence of components that allow the connection of systems to establish data flow between them.
A pipeline consists of:
- one trigger;
- at least one other component.
IMPORTANT: trigger and components must be interconnected.
A trigger is the pipeline's activation condition, that is, the element that defines how the pipeline's execution is initiated - for example, by an external call, in response to an event, or via a schedule. To learn more, read the Triggers documentation here.
A component is an element that receives a message and can interact with it or use the information it contains to execute any of the following activities:
- calling external services (for example, to a REST endpoint);
- processing messages (for example, transforming the contents of a message);
- changing the execution flow (for example, branching the pipeline flow based on conditions, as the Choice component does);
- looping through collections (for example, For Each).
This last case is a bit more sophisticated and to understand it we need to examine it more closely.
When you use a component that iterates in collections, each collection item is processed in a separate flow called a subpipeline. See the image below:
- 1.the execution of the main flow happens until it gets to the component where the subpipeline is created (in the example above, For Each Process Records is the component);
- 2.the execution takes place in the subpipeline, where each item of the collection is processed individually;
- 1.when the execution of this item finishes, the control returns to the beginning of the subpipeline, which starts processing the next item, and so it continues until the collection is entirely processed;
- 3.once the entire collection is processed, the control returns to the For Each component, which directs the flow to the next component in the main flow (in this case, the Read all Data component).