Flow Call Receiver Node
The Flow Call Receiver node acts as an entry point for sub-flows that are called from parent flows. It receives data from parent flows through defined input slots, allowing you to create reusable sub-flows that accept named parameters and process them independently. This node enables modular workflow design and flow composition.

Basic Usage
Use the Flow Call Receiver node as the starting point in a sub-flow to receive data from a parent flow that calls it.
Inputs
The Flow Call Receiver node does not accept direct inputs. Instead, it receives data from the parent flow when the sub-flow is called via a Flow Call node.
Outputs
The Flow Call Receiver node provides dynamic outputs based on configured slots:
- Slot Outputs: Each configured slot (e.g.,
slot-1,slot-2, or custom names likeuserInput,systemPrompt) has its own output handle that can be connected to downstream nodes. - Each slot output corresponds to a named parameter sent from the parent flow.
Configuration
Retrieving Text Content
The node displays a "RETRIEVING TEXT CONTENT" section where you configure input slots:
Slot Configuration
Each slot consists of:
-
Slot Name Input: A text field to define the parameter name
- Must be unique within the node
- Cannot contain spaces (spaces are automatically stripped)
- Default names like
slot-1,slot-2are provided - Empty fields revert to default names on blur
-
Delete Button (Trash Icon): Remove unwanted slots
- Disabled when only one slot remains (minimum requirement)
-
Output Handle (Green Connector): Connect to downstream nodes to route the received data
Add More Retrieval Slots
Click the "+ Add More Retrieval Slots" button to create additional input slots. Each new slot:
- Gets an auto-generated UUID key for reliable data routing
- Receives a default name (e.g.,
slot-1,slot-2) - Can be customized with meaningful parameter names
Example Workflows
Employee Report Processing Sub-Flow
Scenario: Create a reusable sub-flow that receives employee report text from a chatbot parent flow and processes it through JSON Builder for structured data extraction.

Steps to Create the Sub-Flow:
-
Add a Flow Call Receiver node as the entry point:
- This node receives data from the Chatbot with Flow Call Processor in the parent flow
- Configure
slot-1to receive the employee report text
-
Configure the input slot:
i. Use the default or rename the slot:
- Keep
slot-1or rename to something meaningful likereportText - This slot will receive the employee report data from the chatbot
- Keep
-
Connect the slot output to processing nodes:
i. Add a Text node with the report data:
- Connect the Flow Call Receiver's
slot-1output to provide the report text - Example report:
Company Employee Report 2026
Employee #1: John Smith (ID: EMP001, john@company.com, age 32, active) works as Senior
Developer in Engineering department.ii. Add a JSON Block node with the schema:
- Define the structure for employee data extraction
- Example schema:
{
"type": "object",
"properties": {
"employees": [
{
"name": "string",
"id": "string",
"email": "string",
"age": "number",
"status": "string"
}
]
}
}iii. Add a Text node with extraction instructions:
Extract information for all employees mentioned in the report. Create an array of employee
objects and provide summary statistics.iv. Add a JSON Builder node:
- Connect report text → Input
- Connect JSON schema → JSON Schema
- Connect instructions → Overwrite System Prompt
- Connect the Flow Call Receiver's
-
Complete the sub-flow with Flow Call Return:
- Add a Flow Call Return node at the end
- Connect JSON Builder's JSON Output → Returning Slot Json
- This returns structured employee data back to the chatbot
Parent Flow Usage:
In the parent flow (Chatbot with Flow Call Processor):
- User pastes employee report into chatbot
- Chatbot calls this sub-flow with the report text
- Flow Call Receiver's
slot-1receives the report - Data flows through JSON Builder for processing
- Structured JSON returns to chatbot via Flow Call Return
- Chatbot presents formatted results to user
Result: A modular, reusable employee report processing sub-flow that can be called from chatbots or other parent flows to extract structured employee data from unstructured text reports.