Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Condition Component evaluates expressions and directs data to either the true or false output port based on the result. It supports logical conditions using multiple operators and can process complex logical groupings.
expression
object
A structured condition with logical operators (AND, OR) and comparison rules.
=
Checks if two values are equal.
!=
Checks if two values are not equal.
>
Checks if a value is greater than another.
>=
Checks if a value is greater than or equal to another.
<
Checks if a value is less than another.
<=
Checks if a value is less than or equal to another.
%
Checks if a number is divisible by another (modulo).
empty
Checks if a value is empty.
notEmpty
Checks if a value is not empty.
contains
Checks if a value contains another value.
range
Checks if a value falls within a specified range.
regex
Validates if a value matches a given regular expression.
true
Fires if the condition evaluates to true.
false
Fires if the condition evaluates to false.
Define Conditions
Create conditions using logical grouping (AND, OR).
Choose an operator and provide a comparison value.
Evaluate Inputs
Inputs are compared using selected operators.
Logical groups (AND, OR) allow complex expressions.
Direct Output
If the condition evaluates to true, data is sent to the true port.
If the condition evaluates to false, data is sent to the false port.
Logical Groups: Conditions can be grouped using AND and OR for flexible logic handling.
Range Handling: Use rangeMin and rangeMax to check if a value is within a range.
Regex Support: Allows pattern matching for advanced validation.
Controls
The Counter Component maintains an internal counter that increments with each received message. It can also be reset to a specified value.
Set Initial Value and Increment
Configure the count parameter for the starting value.
Set increment to define how much the counter increases or decreases.
Increment Behavior
Each time a message arrives at the item port, the counter increases by the increment value.
Reset Counter
Sending a message to the reset port resets the counter to the specified value or its initial value if no value is provided.
Supports both increment and decrement operations.
State is maintained: The counter retains its value across executions until reset.
Useful for tracking counts in loops, event occurrences, or rate-limiting scenarios.
count
number
The initial counter value (default: 0).
increment
number
The amount by which the counter increments (default: 1, can be negative for decrement).
item
Triggers the counter increment.
reset
Resets the counter to a specified value or its initial value if not provided.
count
Emits the updated counter value after each increment.
The Digest Component collects incoming data entries and releases them as a batch based on a threshold, a schedule, or a manual trigger via a webhook. This component is useful for aggregating data over time and sending it at controlled intervals.
threshold
number
Number of entries required to trigger output. If set, output is triggered when this count is reached.
webhookUrl
string
A generated webhook URL that allows manual triggering of output.
minute
string
Specifies at which minutes of the hour the digest should run. Supports cron-like syntax.
hour
string
Specifies at which hours of the day the digest should run. Supports cron-like syntax.
dayMonth
string
Specifies on which days of the month the digest should run. Supports cron-like syntax.
dayWeek
string
Specifies on which days of the week the digest should run. Supports cron-like syntax.
timezone
string
Timezone for scheduling, defaults to GMT.
outputType
string
Format of the output data. Options: first (first entry), array (all entries as an array), object (one entry at a time), file (CSV file).
in
Receives data entries for aggregation.
out
Emits the aggregated data based on the configured condition (threshold, schedule, or webhook trigger).
Set a Threshold (Optional)
Define the threshold parameter to release data when a certain number of entries are reached.
Schedule Batch Processing (Optional)
Configure minute, hour, dayMonth, and dayWeek to process batches at specific times.
Manual Trigger via Webhook (Optional)
Use the webhookUrl to release entries manually at any time.
Select Output Type
Choose how the collected data should be sent (first, array, object, or file).
Supports multiple trigger methods: Data is released either via count (threshold), time (schedule), or manually (webhook).
Flexible scheduling: Uses cron-like syntax for precise control over execution times.
Different output formats: Users can choose between receiving data as an array, a single entry, or a downloadable CSV file.
The Join Component is used to merge multiple input connections. It forwards every received message to the output port without modification.
in
Receives messages from multiple sources.
out
Emits the received input messages as output.
Connect Multiple Inputs
Attach multiple input sources to the in port.
Forward Messages
Every received message is immediately sent to the out port.
Does Not Modify Messages: Messages are forwarded exactly as received.
Useful for Routing: Can be used to merge multiple data streams into one processing path.
The JoinEach Component is designed to work with the Each Component. It collects multiple incoming messages based on a specified count and outputs them as a single batch when all expected messages have arrived. If some messages do not arrive within a timeout period, it outputs the partial batch along with count information.
in
Receives individual messages to be aggregated. Each message must contain a correlationId.
count
Specifies the total number of messages expected. Must be provided before aggregation begins.
out
Fires when all expected messages arrive, emitting an array of collected messages.
timeout
Fires when the timeout is reached before all expected messages arrive, providing the partial batch and counts.
out Portitems
The array of collected messages.
timeout Portitems
The array of messages that arrived before the timeout.
count
The number of expected messages.
arrived
The number of messages that actually arrived.
Set Up with Each Component
Ensure messages sent to in contain a correlationId matching the one from the Each component.
Define Expected Count
Send a message to the count port specifying how many messages the component should wait for.
Processing Messages
The component collects messages based on the correlationId.
When all expected messages arrive, they are sent as an array to the out port.
If not all messages arrive before the timeout, the timeout port emits the partial batch.
Works with Correlation IDs: Ensures messages from the same batch are correctly joined.
Timeout Handling: Prevents indefinite waiting if some messages fail to arrive.
Batch Processing: Useful for grouping messages into structured outputs for further processing.
The SetVariable Component assigns variables dynamically based on input type and value. It allows storing values in various formats such as text, numbers, dates, booleans, and files.
in
Accepts an object containing variables and their values.
out
Emits the assigned variables as an object.
Text (text) – Stores a string value.
Textarea (textarea) – Stores a longer text value.
Number (number) – Stores a numeric value.
Date-Time (date-time) – Stores a date and time.
Boolean (toggle) – Stores a true/false value.
File (filepicker) – Stores a selected file reference.
Provide Variables
Send an object containing variable names, types, and values to the in port.
Processing Variables
The component assigns the variables dynamically based on their types.
Retrieve Output
The processed variables are sent as an object through the out port.
Flexible Variable Storage: Supports multiple data types for dynamic variable assignments.
Useful for Workflow Automation: Allows temporary storage of values for later processing.
Outputs in Key-Value Format: The output is structured as an object containing assigned values.
The Each Component iterates over a list and outputs a new message for each item. It allows processing list elements individually, enabling sequential execution of subsequent actions.
list
array / string
The list to iterate over. If a string is provided, it must be a valid JSON array.
in
Receives the list to iterate over.
item
Emits each item from the list with additional metadata.
done
Fires after all items have been processed, providing the total count and correlation ID.
item Portindex
The index of the current item in the list.
value
The value of the current item.
count
Total number of items in the list.
correlationId
Unique identifier for tracking batch processing.
done Portcount
The total number of processed items.
correlationId
Unique identifier for tracking batch execution.
Provide a List
Ensure the input list is an array or a valid JSON string representing an array.
Processing Items
Each item in the list is sent separately to the item port.
The done port is triggered after all items are processed.
Handling Index and Correlation ID
Each item is assigned an index and a correlationId to track processing.
Supports JSON Parsing: If list is a string, it will attempt to parse it as JSON.
State Persistence: Keeps track of progress and resumes processing if interrupted.
Efficient for Iteration: Useful for batch processing workflows requiring individual handling of list elements.
The OnStart Component is a trigger that fires once when the flow starts. It emits a timestamp indicating when the flow was initiated.
out
Fires when the flow starts, providing the start time.
out Portstarted
The timestamp (ISO 8601 format) indicating when the flow started.
Automatic Trigger
The component automatically fires when the flow begins execution.
Start Time Emission
Outputs a started timestamp that can be used for logging, tracking, or scheduling purposes.
One-Time Execution: Triggers only once per flow execution.
Useful for Logging: Can be used to capture flow start times for analytics or debugging purposes.
The Switch component allows conditional branching of messages based on predefined expressions. It evaluates up to five conditions (out1 to out5) and routes messages accordingly. If none of the conditions match, the message is sent to the else output.
Each expression supports AND/OR logic, allowing complex conditions.
Define Conditions
Configure up to 5 expressions (expression1 to expression5) for routing messages.
Set Operators
Use supported operators to define comparison logic.
Handle Default Cases
If none of the conditions match, the message is sent to else.
expression1 - expression5
expression
Conditional expressions for respective outputs (out1 to out5).
else
default
Messages that do not match any condition are sent here.
=
Equal to
!=
Not equal to
>
Greater than
>=
Greater than or equal to
<
Less than
<=
Less than or equal to
%
Modulo operation (divisibility check)
empty
Checks if the value is empty
notEmpty
Checks if the value is not empty
contains
Checks if a value contains a substring
range
Checks if a value falls within a specified range
regex
Matches a value against a regular expression
out1 - out5
Message is sent to the first matching output based on conditions.
else
If no conditions are met, the message is sent to this output.