This action can execute any predefined Function in Internal, including HTTP Functions, SQL Functions, MongoDB Aggregate Pipelines, and functions auto-generated by Internal.
Select a data source and function.
Then, click “Configure” on the bottom right if the function has parameters. You can leave the parameter unresolved if you want to define it later in Spaces, Queues, or Automations.
If you want to resolve the parameter now, choose from Value, Data binding, Template, or Null.
- Value: A hard coded value.
- Data binding: Bind to available data in this Pipeline such as data returned from a previous step or global values such as the logged-in user’s email address.
- Null value: If you want the value to be null
When you click Configure inputs, you’ll see that parameter show up. In this case, you’ll want to set the value type to be “Data binding” and bind to data being returned from the first step name “Users”.
Add a Conditional action to execute a Function when a condition is true (or false).
You can use data from previous steps in the Pipeline or global variables like the logged-in user’s email address. Below is an example where we bind to the previous step’s data.
If you choose to multiple conditions, be aware that ANDs take precedence over ORs.
Once you’ve defined the condition, configure what to do when the condition is true, and when it is false.
Loops are useful for automating repetitive tasks with complex logic. Loops require data from the previous Pipeline Step to iterate through.
Once you've chosen what data to loop through, configure what function will execute against each item in the data you've selected. Loops are helpful for use cases like automating inventory checks, customer notifications, and reporting metrics.
Updated 8 months ago