Helper Flow
On-demand flow triggered by other flows. Acts like a function — receives input from the caller, processes it, returns output.
Unlike Telegram, webhook, or schedule events, a Helper Flow has no external trigger. It runs only when another flow invokes it via a Flow Control function.
Creating a Helper Flow
- Create a new flow
- Select Helper Flow as the event
- Click + Add output on the event block to define the input parameters the caller will provide
- Add actions and functions to process the data
- Save and enable
How It's Called
Helper flows are invoked by Flow Control functions:
| Function | Description |
|---|---|
| Call Flow | Run the helper flow once, wait for the result |
| Call Flow Async | Run without waiting |
| For Each | Run once per item in a list |
| For Each — Ignore Errors | Same as For Each, but continues if one iteration fails |
| Repeat | Run N times with an index counter |
| Filter Custom | Run as a filter test per list item |
Data Flow
- The caller defines input values that map to the helper flow's event outputs.
- In For Each, the Item block represents the current list item.
- Drag Item into the helper flow's input fields.
- Each iteration creates a separate execution history entry.
Item Block
In For Each, the blue → Item block appears in the "With the following values" section. Drag it to any input field — it represents the current list item for each iteration.
Per-Iteration History
Each For Each iteration creates a separate execution entry in the helper flow's history. You can inspect:
- What data was passed (event outputs with real values)
- What each block produced
- Whether it succeeded or failed
Concurrency
Set concurrency to control parallel execution:
0— sequential (one at a time)1+— parallel (multiple items at once)
Example: Process Each User
- Main flow: get a list of users → For Each → select a helper flow.
- Helper flow event outputs:
userId,action. - In For Each: drag Item into
userId, type"notify"inaction. - Helper flow: send a Telegram message to each
userId.