Overview
A flow is an organized set of components which interact with each other via a simple and intuitive drag and drop interface to perform a specific task.
Flow Components
Flows differ in complexity depending on the purpose of the flow. Components within a flow are connected together by lines which represent data flow paths between the components.
When a flow is run, components defined within the flow are executed in order to produce one or more outputs as defined by the particular flow.
If you click on the triple-dot icon at the top right of the trigger component you can change the name "Trigger" and you can write a description as you can see on the top right of the screen. This method works for every components.
In the illustration down below you can see all the different inputs that can be created. You can add components with the "+ add" button on the config. When you click on preview you can fulfill all your different inputs.
When you click "Preview," you can enter data into all the different input fields and test the functionality to ensure everything works as expected. This feature allows you to simulate actual usage scenarios, verifying that the inputs are correctly processed and that the desired outcomes are achieved. inputs and test to see if it's works.
Each component's output has a unique identifier assigned when the component instance is created. For triggers, the identifier is formatted as "trigger." followed by the "Variable Name." For instance, if you have a text component, its identifier would be "trigger.text," and you can reference this identifier by typing "@".
Component Data Flow
Data is transferred through a flow with connections between components. For example, the flow shown below, is a simple flow, in which a "Trigger" component is used to feed a textual query (via a text input component) into an OpenAI component. The OpenAI component has an output connected to an "Output" component, in order to receive the result of the query.
Components only accept specific types of data flow connections from other components. For instance, an OpenAI component's input will exclusively accept connections from a Text Input component, since the OpenAI component is designed to process textual input queries.
A flow can also be configured as an API end-point, thereby providing optimal adaptability for integration within your software application.
Components can be selected from a large library of pre-defined components and components can be created to encapsulate customized data processing tasks.
Component Parameters
Most components have configuration parameters. Depending on the particular component, key configuration parameters regarding the execution of the component can be selected directly in the component UI block.
For example, for the OpenAI component, we can select the particular OpenAI model to use by clicking the "Model" dropdown menu as shown below.
Advanced configurations
To access more advanced configurations for a component, select "Show Advanced Configurations" at the bottom of the component. This will display additional options and settings for the component, as illustrated below.
For more information regarding the available components and detailed information regarding each components configuration parameters, please refer to the Component Reference section.
Last updated
