The Condition node lets you define decision points in an Agentic Process, from which one or more paths can continue.
You can add a Condition node from any existing node in the Agentic Process. To do so, hover over one of the node's anchor points and click on the + icon. This opens the context menu, where you will see options such as Task, Event, Finish, and Condition.
You can also add a Condition by dragging it directly from the Toolbox.
Agentic Processes support two types of Condition nodes: Agentic and Parallel.
The Agentic condition allows you to delegate the decision on which path to follow to an Agent. This Agent evaluates the current state of the Agentic Process instance and selects one or more possible paths based on the available information.
When you select a Condition node of Agentic type, the Properties panel becomes available with the following options:
- Condition name: Enter a descriptive name to identify the condition in the Agentic Processes.
- Type: Defines the type of condition. In this case, it is set to Agentic, which means an Agent will decide which path to follow based on the state of the Agentic Processes.
- Condition instructions: Enter custom instructions to guide the Agent’s decision. This field is optional, but useful if you want to limit the choice to a single path, prioritize certain steps, or include specific conditions.
The Agent's decision is based on three elements that are automatically includes in the prompt:
- The subject of the Agentic Process and the variables assigned up to that point. Note that if the Agentic Process starts with an artifact event, no variables are retained.
- The process history, including the list of executed tasks, their statuses, and start and end times. Task content, results, and generated files are not included.
- Information about the tasks available after the Condition node: task names, descriptions, and the Agents that will execute them.
If you don’t enter any Condition instructions, a default prompt is generated that automatically includes this information.
The prompt has the following structure:
This is a workflow process, here is what has happened so far:
The instance subject is: {{PROCESS_INSTANCE_SUBJECT}}
The information about the process that we have so far is as follows:
### START HISTORY
{{PROCESS_HISTORY}}
### END HISTORY
{{GATEWAY_EXPRESSION}}
You must choose one of the following next-steps to call:
{{NEXT_STEPS}}
Any text you enter in Condition instructions will be inserted in the {{GATEWAY_EXPRESSION}} space.
The Parallel condition allows the Agentic Process to continue along multiple paths simultaneously. It is useful when different tasks can be executed in parallel.
When you select a Condition node of Parallel type, the Properties panel is enabled with the following options:
- Condition name: Enter a descriptive name to identify the condition in the Agentic Process.
- Type: Defines the condition type. In this case, it is set to Parallel, which means the Agentic Process will continue through multiple paths at the same time from this point forward.
Unlike the Agentic type, the Parallel node does not evaluate any conditions or require instructions. All outgoing paths are triggered simultaneously, with no need for a decision.
After a Parallel node, you can define a new node where you want the process to converge once all branches are completed. This convergence point must be located one step away from the Parallel node.
Since version 2025-05.