maestro
latest
false
Maestro user guide
- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Dedicated Flow canvas nodes that apply UiPath document intelligence: extraction, summarization, and more as discrete steps in a process.
Document processing nodes bring UiPath document intelligence directly onto the Flow canvas as discrete, business-oriented steps. Each node represents one operation — extract structured fields, synthesize a long document — without requiring you to wire up a separate agent or understand the underlying model technology.
The nodes appear in the node palette under Document processing, grouped by the operation they perform.
Available nodes
| Node | What it does |
|---|---|
| Extract | Pulls typed fields from a document using a deployed IXP extraction model. Use when you need structured data — invoice totals, form values, named fields — returned in a typed shape for downstream nodes to act on. |
| Summarize | Synthesizes across a document (up to 1,000 pages) and returns a grounded answer with citations. Use when the next step needs a reasoned answer or summary, not a fixed schema of fields. |
How document processing nodes differ from agent tools
Summarize also exists as a built-in agent tool that attaches to an Autonomous Agent. The distinction is where the decision is made:
- Document processing node — the step is deterministic. The flow always calls Extract or Summarize at that point in the process, with the inputs you configure.
- Agent tool — the agent decides when to call the tool while reasoning. Use the Summarize agent tool when an Autonomous Agent needs to synthesize documents as part of broader open-ended reasoning.