Architecture of Action Batches
An Execute Action Batch follows a layered and logical flow that enables complex, nested behavior while keeping execution understandable and modular.
Trigger >> Evaluation >> Send Fields >> Action
Each Action Batch begins with a trigger, which can come from any supported event source such as a touch interaction, sensor event, data change, or time-based logic.
Learn more: Triggers
Once triggered, the batch runs through the following structure:
Evaluation Phase
Conditions are checked to determine whether the batch should proceed.
Send Fields
Data is passed and collected through configured Send Fields, which can be used in downstream evaluations or actions.
Action Execution
If the evaluation passes (evaluates to true), the defined actions are executed.
Inside each Action Batch, this same structure can repeat — each action may contain its own evaluations and even nested batches.
Nested Batches
Nested action batches allow deeper logic to be constructed through hierarchical flow.
Think of it like a tree: the root node is the initial Execute Action Batch, and each branch can represent an action or another batch, leading to multiple layers of logic and conditional flows.
This architecture supports:
- Multi-step logic (e.g. "if X happens, then do A, and if A returns Y, then do B")
- Conditional branching with Send Fields and Evaluations at each layer
Benefits of the Architecture
This structure makes it possible to:
- Break down complex logic into organized, readable units
- Pass, filter, or transform data at every level
- Extend or reuse logic by nesting or duplicating batches
- Debug more efficiently by isolating logical blocks