How to configure workflows that run logic for each row in your Primary Table or for grouped subsets using Labels.
Overview
Rayven workflows can be configured to run once or iteratively—for each row in your Primary Table or for specific subsets defined by label values. This article explains how to set up iterative workflows, when to use them, and the key configuration settings in Trigger and Connector nodes that enable row-wise or group-wise execution.
This is especially useful when you want logic to be applied individually across a dataset—for example, generating calculations for every asset, sending alerts for each customer, or evaluating rules across different label groups like regions, types, or statuses.
Understanding Iterative Execution in Rayven Workflows
By default, a Trigger or Connector node executes a workflow once per event or schedule. However, Rayven provides the ability to iterate across your data by enabling the "Trigger using filter" option and selecting either:
-
A full-row iteration for each UID in the Primary Table
-
A grouped iteration based on selected Label Values
Once enabled, the node will iterate the workflow execution for each matching record or group, providing individual payloads for each execution.
When to Use Iterative Workflows
Iterative workflows are ideal for:
-
Running logic per record in your Primary Table (e.g. per asset, job, or user)
-
Processing grouped records by label (e.g. Region = NSW, VIC)
-
Sending individual outputs or notifications for each record or group
-
Performing conditional checks or updates row-by-row
Example use cases:
-
Send an email to each customer with overdue invoices
-
Generate a widget per active device in a dashboard
-
Aggregate sensor readings by equipment group
-
Create records in a secondary table for each job per project
How to Configure Iterative Execution
1. Use a Trigger or Connector Node
Drag in a node such as:
-
Trigger Node (e.g. Scheduled or On App Load)
-
Connector Node (e.g. API, SQL, FTP)
These will act as the entry point for the workflow.
2. Enable “Trigger using filter”
In the node configuration panel, check Trigger using filter.
This activates the ability to run the workflow once for each matched record (UID) or group (Label).
You must select at least one label filter from your Primary Table to proceed. The default label is PrimaryLabel:All.
🔍 Tip: You can combine multiple filters using AND/OR logic if needed.
3. Complete the Workflow Logic
With the node configured for iteration:
-
Each execution receives a payload scoped to one UID or Label group
-
Design your logic using standard nodes (e.g.
Update Table,Rule Builder,Data Summary,Send Data to Node) -
You can also dynamically push outputs or write results to tables per iteration
Best Practices
-
Start with a small dataset: Use a specific label filter while testing to reduce complexity
-
Use the Inspect Data tab: Each node includes this tab to debug the data per iteration
-
Label thoughtfully: Design your label model in the Primary Table early so filters align with real-world groupings
-
Chain update nodes: For writing results back, you can use
Update Tablein sequence, knowing each iteration has a scoped payload -
Name things clearly: Include UID/Label in workflow and node names when building complex systems
Summary
Iterative workflows enable you to process individual Primary Table records or grouped subsets based on labels. By enabling the Trigger using filter setting and selecting relevant filters, you can execute your workflow logic in a granular, controlled manner.
This capability is especially powerful when combined with table operations, output nodes, and real-time visualisation workflows.
FAQs
What’s the difference between using a label filter to activate triggerable nodes and not using one?
When you don’t use a label filter, the triggerable node activates the workflow once per scheduled event or external trigger—executing the logic in a single pass.
When you do enable a label filter, the workflow is executed once for each matching Primary Table row or label value, depending on the filter you apply. This enables per-record or per-group iteration, giving you scoped payloads for more granular logic execution
Do all nodes support iterative input?
Only Trigger and Connector nodes support the “Trigger using filter” setting, which determines whether a workflow runs iteratively per UID or label value.
All other nodes in the workflow do not differentiate between iterative or single execution—they simply process whatever payload they receive. It’s your responsibility to ensure downstream nodes are designed to handle payloads correctly, whether the workflow is triggered once or multiple times through iteration.
Can I use multiple labels in the filter?
Yes. You can use multiple label filters and combine them using AND or OR logic.
What happens if no rows match the label filter?
The workflow won’t run at all—there are no matching iterations to execute.
Does using “Trigger using filter” create multiple widgets on a page?
No. The “Trigger using filter” setting controls how many times the workflow runs, not how many widgets are created on the interface.
To display multiple widgets (e.g. one per UID or per Label Value), you must configure the Frontend node’s “Number of Widgets to Display” setting separately. That setting determines how the data is visualised, not how often the workflow is triggered.