maestro
latest
false
- Introduction
- Process modeling
- Process implementation
- Debugging
- Simulate
- Publishing and upgrading agentic processes
- Extracting and validating documents
- Business Rules (Preview)
- Process Apps (Preview)
- Process operations
- Process monitoring
- Process optimization
- Licensing
- Reference information
Maestro user guide
Last updated Nov 5, 2025
This section shows how to build a process that downloads an invoice, extracts data with UiPath Document Understanding™, routes a Document Validation task to a user, and completes on approval.
To build this process, you need to achieve the following objectives:
- Create an RPA workflow to download an invoice, extract fields, and generate validation artifacts.
- Create an Action App to validate the extracted content.
- Model a Maestro process that runs the RPA workflow, hands off to a user for validation, and finishes on approval.
- You need access to Maestro, Orchestrator (shared folder and storage bucket), Studio Web, and Apps.
- You need a Document Understanding extractor/classifier configured for invoices.
- You need a sample invoice URL (publicly reachable or hosted in your environment).
- Create or open a Solution in Studio Web, and add a Maestro process. Read how to model a process.
- Ensure you can publish to your target Orchestrator folder and have a defined storage bucket.
- Ensure your Document Understanding model (extractor/classifier) is available to the RPA workflow.
To build and publish the RPA workflow in Studio Web, take the following steps:
- Create a new RPA project (e.g., Document Extraction).
- Add thwe following activities:
- Download File from URL. Add the invoice URL as input.
- Extract Document Data. Use your DU model and include classification if applicable.
- Create Document Validation Artifacts. Configure the shared Orchestrator folder and the storage bucket.
- Test the workflow locally in Studio Web.
- Publish the workflow to Orchestrator.
To build and publish the Action App in Studio Web, take the following steps:
- Create an Action App task named Document Validation.
- In the Action schema, add an input property (for example,
validationData) of type ContentValidationData. - Add the validation control to the App, and set its data source to the
validationDataproperty. - Publish the Action App.
To model the process in Maestro, take the following steps:
- Add a Start event.
- Use None (manual) for testing, or Message if you plan to trigger externally.
- Add a Service task – Run extraction.
- Implementation: Start and wait for RPA workflow.
- Select the workflow you published in Step 1 - Build and publish the RPA workflow (Studio Web).
- Map inputs (e.g., Invoice URL).
- Capture outputs. Maestro exposes them as variables.
- Add a User task – Validate Document Extraction.
- Implementation: Create action app task.
- Select the Document Validation Action App from Step 2.
- Map the user task input to the extraction output (bind to the
ContentValidationDatapayload).
- Add an Exclusive gateway to branch on the user’s decision.
- Approve: proceed to End.
- Reject: route to a correction branch (optional) or loop back to RPA.
To publish, run and validate the Maestro process, take the following steps:
- Publish and deploy the Maestro process. Read more about publishing.
- Start a Debug run from the Start event.
- When the Document Validation task is created, open it from the running instance.
- Review the extracted fields in the validation control. Select Approve to continue the flow.
- After completion, inspect Variables to see the stored
documentValidationdata and references to artifacts in your storage bucket.
