Tools includes several useful modules that can enhance your scenario.
Allows you to create a custom trigger and define input bundles.
Create custom bundles by adding array items.
The array consists of the name – value pairs.
You can use it, for example, for contacts or any other list that is scheduled to be send to specified email address (Email > Send an email, Gmail > Send an Email modules.) or as a simple reminder to be triggered whenever you want.
Returns value incremented by 1 after each scenario run.
The following scenario sends an email to the first recipient after every odd scenario run, and to the second recipient after even scenario run.
There are two conditions used after the router module:
1. odd – set the condition using the modulus math function that equals
2. even – set the condition using the modulus math function that equals
Allows you to delay the scenario flow for up to 300 seconds (5 minutes).
Enter the number of seconds the scenario will be paused for.
If you wish to pause the flow for longer periods of time, we suggest to split your scenario into two scenarios:
1. The first scenario would contain the part before the pause
2. The second scenario would contain the part after it.
The first scenario would end up with storing all the necessary information to a Data store together with the current timestamp. The second scenario would periodically check the Data store for records with timestamp older than the intended delay, retrieve the records, finalize the processing of the data and remove the records from the Data store.
Retrieves a value that was previously created by the Set Variable module.
Creates a variable that can be mapped by other modules in the route or by the Get Variable module in the every route in the scenario.
Enter the variable name. This name will be displayed when mapping the variable in other modules.
Enter the value for the variable.
Merges values from the selected fields of received bundles into a single bundle using a specified column and row separator (which allows you to create a table).
Select the module you want to aggregate fields from.
|Aggregated fields||Select fields from the module selected above whose values you want to aggregate into the one bundle.|
Select or enter the type of separator that will separate field values columns in the resulting bundle.
Select or enter the type of separator that will separate field values rows in the resulting bundle.
Define an expression containing one or more mapped items. The aggregated data will be then separated under Groups with the same expression's value. Each Group outputs as a separate bundle containing a Key with the evaluated expression and the aggregated text. By doing this, you can use the Key as a filter in subsequent modules.
Merges values from the selected fields of received bundles into a single bundle.
You can use the text aggregator to insert more values (e.g. customer names or notes) to the single bundle and send the email containing all values in the email body or the email subject.
This module allows you to retrieve numerical values, apply one of the selected functions (SUM, AVG, COUNT, MAX,...) and return the result in one bundle.
The module sums up values under the number parameter.
Converts any value to a string data type (text). It makes the mapping easier when mapping e.g. binary data.
Converts entered input text (or binary data) to the selected encoding.
Enter the content you want to convert.
|Input data codepage||Enter the input data encoding type. This is important for the binary form of data.|
|Output data codepage||
Select the target encoding of your data.
Checks the input value for the match with the provided list of values. Returns output based on the result.
Enter the expression you want to evaluate.
|Cases||If the input contains a value entered to the Pattern field, then the value entered to the Output field is returned.
If the condition is not met then no output is returned OR the value from the Else field (below) is returned.
Enter the value that is returned when the criteria set in the Cases field are not met.
PLANNED- see the Workaround section below.
Employ HTTP > Make a request module in the main scenario to call the other scenario. Employ Webhooks > Custom webhook module in the other scenario to receive the call Employ Webhooks > Webhook response module in the other scenario to return the response.
In some cases you may want to forcibly stop the scenario execution followed by rollback or commit phase or to stop the processing of a route and optionally store it in the queue of incomplete executions.
PLANNED- see the Throw module.