Understand how a pipeline is built.

Micaella Mazoni avatar
Written by Micaella Mazoni
Updated over a week ago

IMPORTANT: this documentation has been discontinued. Read the updated Pipeline documentation on our new documentation portal.

The Platform has the pipeline as main piece, which is a sequence of components that allow the connection os systems to establish data flow between them.

A pipeline is composed by:

  • 1 trigger

  • at least 1 other component

IMPORTANT: trigger and components must be connected between each other.

Trigger is the activation condition of the pipeline, which means, it's the element that defines how the pipeline execution will be initiated - for example, through an external call, in response to an event or via schedule.

A component is an element that receives a message, being able to interact with it or use its the information to execute one of the following activities:

  • call external services (for example, a call to a REST endpoint);

  • process messages (for example, transform the message content);

  • change the execution flow (for example, a bifurcation that allows the redirection of the pipeline flow based on a condition, as the Choice component does);

  • goes through collections (for example, For Each).

Now understand a little bit better how the iteration in collections works.

When you use a component that iterates in collection, each collection element is processed/treated in a separate flow named subpipeline. See the image below:

  1. the execution of the main process happens until getting to the component where the subpipeline is created (in the example above, For Each "Processes Registers" is the component);

  2. the execution goes to the subpipeline, where each collection item will be trated individually;

  3. when the execution of this item finishes, the control goes back to the subpipeline beginning, that starts the processing of the following item and so it goes, until the collection is entirely processed;

  4. once all the collection is processed, the control goes back to the For Each component that, with its finished execution, passes the process to the next component of the main process (in this case, the "Read all the Data" component").

To know how to build a subpipeline, just click here.

Did this answer your question?