Sub Project flow
Sub Project flow runs another of your flows as if it were one more step of this one. Once you choose the flow, its inputs appear as node fields, and its results come out through Flow Outputs. That way you can reuse a process in several flows without copying it.
When to use it
- Reusing the same process in several flows, such as classifying an email or registering a customer.
- Splitting a big flow into parts that are easier to maintain.
- Letting one team maintain a process other flows use.
Configuration
| Field | What it does |
|---|---|
| Flow Name | The flow to run, among those in your account. Press the refresh button to see the list. Once chosen, one field per input of that flow appears, named after the component and the field, for example “Chat Input - Text”. |
Advanced options
| Field | What it does |
|---|---|
| Session ID | Message session identifier. If the main flow has one, that one is used. |
| Conversation ID | Conversation identifier. If the main flow has one, that one is used. |
Output
The Flow Outputs output holds the results of the flow that ran. In tool mode, an agent can run the flow when needed; see Tool Mode.
Example
A company has a “Customer signup” flow that creates the CRM record and sends the welcome email.
- In the sales flow, add Sub Project flow and choose “Customer signup” in Flow Name.
- Connect the customer’s name and email to the fields that appear.
- Use Flow Outputs to continue the sales process.
Related components
- Project flow as Tool: offers a flow as a tool for an agent.
- Projects: where your flows are.