- Introduction and getting started
- Maestro landing page
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Licensing
- Reference information
Maestro user guide
In Maestro, agents are treated as participants in a business process. Within a BPMN workflow, agents are represented using Service tasks, which can invoke both UiPath-hosted and external agents. Each agent task can be configured with specific input and output parameters, which allow Maestro to pass context-aware data to the agent and receive structured results in return.
Refer to Tasks in BPMN modeling for an overview of Service Tasks in Maestro.
Agent behavior is defined in the Properties panel of a Service task. You can configure the task to call a UiPath agent or an external agent, depending on your business needs.
Start and wait for agent
Use this option to invoke an agent deployed in your UiPath tenant. This includes:
- Low-code agents created using tools like Agent Builder.
- Coded agents developed in Python or other languages and deployed to Orchestrator.
Start and wait for external agent
Use this option to connect to third-party or external systems. You must specify:
- Connector: The integration target (e.g., CrewAI, Salesforce, or another service)
- Connection: A configured instance of the connector, representing either a
specific agent or a context-specific credential set.
Note: You can use the same agent with different permissions or behaviors by defining multiple connections.
Inputs and outputs for agents are configured in the same way as other Maestro task types.
- Inputs: Variables or expressions passed to the agent at runtime.
- Outputs: Variables populated from the agent’s JSON response.
{
"key1": "value1",
"key2": "value2"
}{
"key1": "value1",
"key2": "value2"
}
The agent must return a JSON response using the same parameter names expected by Maestro. These values are mapped to process variables using the Output > Response section in the task's Properties panel.
| Parameter | Description |
|---|---|
role | Role or context for the task (e.g., validation vs. summarization) |
prompt | Instruction provided to the agent, often including process-specific data |
tools | List of tools the agent may use to complete the task |
user_id | Unique identifier shared between the process and the agent context |
Example prompt:"Complete loan validation for {loan_application_number}. Respond in JSON format using the parameter 'loan_application_status'."
| Parameter | Description |
|---|---|
conversation_id | Reference to the dialogue or interaction session |
loan_application_status | Status result returned by the agent |
tokens_used | Metadata about resource usage |
To use agent output in your workflow, you must assign each output parameter to a process variable in the Output > Response configuration of the task.
