Plain-language definitions of the terms used in the Maestro Automate guide, with links to the pages that explain each one.

The terms used in this guide, in alphabetical order.

A separate kind of UiPath project that chains API calls and returns a result quickly, without AI agents or human steps. A Maestro Automate workflow can call a deployed API workflow as a node. Maestro Automate or API workflow compares the two.

An AI agent that works on a task on its own: it reads its instructions and the input, uses the tools you give it, and returns a result. On the canvas, it's the Autonomous Agent node.

An AI assistant that writes code from your instructions, such as Claude Code, Codex, Cursor, or GitHub Copilot. With the UiPath CLI and skills installed, it can build Maestro Automate workflows from a description. Set up your coding agent describes how.

The link between UiPath and another app, such as Slack, Gmail, or Salesforce, signed in with your account for that app. Nodes that work with other apps use a connection. Connector lists every connector, and Create a connection describes how to create one.

An AI agent that holds a conversation with a user in a chat or a phone call. On the canvas, it's the Conversational Agent or Voice Agent node.

The way you test a workflow before you deploy it. The workflow runs step by step on the canvas, and each node shows its input, output, and errors. Debugging basics describes it.

To make a workflow available to run outside the canvas, for example on a schedule or when an app event happens. A deployed workflow runs without you. Deploy a workflow describes how.

A request from an AI agent to a human, when the agent shouldn't decide alone. The agent pauses, the human answers, and the agent continues. Human in the loop: escalation or human step compares escalations with Human nodes.

A test that checks whether a workflow or an agent gives the expected results for a set of sample inputs. Evaluators score each result. Evaluations describes how to set them up.

The record of a run: which nodes ran, in what order, with what input and output, and how long each took. Debugging basics describes it for test runs, and Monitor runs for deployed runs.

A piece of JavaScript in a node field that computes a value when the workflow runs, such as $vars.newOrder.output.productId. Expression syntax describes how to write one.

The visual editor where you build a workflow by adding nodes and connecting them. It's the same in Studio Web, VS Code, and Studio Desktop. Flow canvas describes its parts.

A step in the workflow where a human reviews or approves something, and the workflow continues based on their choice. The Human category of the Add node panel offers two: Quick Form and Action App.

An error recorded during a run, with its message and the node where it happened. Debug mode shows incidents on the Incidents tab. Debugging basics describes how to find them.

The UiPath product for building workflows in which AI agents and APIs work together. Each run finishes within 24 hours. What is Maestro Automate? introduces it.

The UiPath product for orchestrating a business process across agents, humans, and systems. You can convert a Maestro Automate workflow to Maestro Orchestrate when the design calls for it. Convert to Maestro Orchestrate describes when and how, and Maestro Orchestrate or Maestro Automate? compares the two products.

Sample output that replaces a node's real result while you test, so you can test without calling an app, an agent, or a human. Output mocking describes how.

One step in a workflow, such as a trigger, an HTTP request, an AI agent, or a decision. Node reference lists every node.

The unique name of a node, which expressions use to refer to its output, for example checkStock in $vars.checkStock.output. It can differ from the label on the canvas. Variables and data flow describes how to use it.

One time a workflow runs, from the trigger to the end. Runs are what Maestro Automate counts for billing. Monitor runs describes how to follow them.

A set of instructions that teaches a coding agent how to build a kind of UiPath project. The skill for Maestro Automate workflows is uipath-maestro-flow. Set up your coding agent installs it.

The package that holds a workflow and everything it needs, such as other workflows and agents. You deploy a solution, not a single file. Deploy a workflow describes how.

A workflow inside another workflow. It groups a set of nodes into one step, runs them with its own variables, and returns its output to the parent workflow. Subflows describes them.

The node that starts a workflow, for example manually, on a schedule, or when an email arrives. Every workflow needs at least one. Triggers lists them.

The UiPath command-line tool, uip. Coding agents and the VS Code extension use it to build, run, and deploy workflows. UiPath CLI describes it.

A sequence of connected nodes that does a job, from a trigger to an end. In Maestro Automate, you build it on the Flow canvas.