- Introduction
- Getting started
- Process modeling with BPMN
- Process modeling with Case Management
- Designing a persistent case entity schema
- 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)
- Managing live case instances: pause, migrate, and retry
- Maestro case management component dictionary
- Process modeling with Flow
- Getting started
- What is Flow?
- Your first Flow
- Flow in VS Code
- Core concepts
- Node reference
- Build guides
- Best practices
- Reference
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
What you'll build
A process that calls a public API, extracts data from the response, and logs it to the output panel.
Time to complete: 5 minutes
What you'll need
- Access to UiPath Automation Cloud with Flow enabled (Studio Web)
Step 1 — Create a new flow
Open Studio Web and select Create Project to create a blank process.
You'll see the Flow canvas with a Manual Trigger already on it. The Manual Trigger starts your process on demand — you'll use it to debug your flow later.
Step 2 — Add an HTTP Request node
Select the + on the outgoing handle of the Manual Trigger. Search for HTTP Request and select it.
Configure the HTTP Request node in the properties panel:
- Set Method to
GET - Set URL to
https://jsonplaceholder.typicode.com/posts/1
Leave all other fields at their defaults.
Step 3 — Add a Script node
Select the + on the outgoing handle of the HTTP Request node. Search for Script and select it.
In the script editor, enter the following JavaScript:
const post = $vars.httpRequest1.output.body;
return {
title: post.title,
id: post.id
};
const post = $vars.httpRequest1.output.body;
return {
title: post.title,
id: post.id
};
This reads the response body from the HTTP Request node and returns the post title and ID.
$vars.httpRequest1 references the HTTP Request node by its default name, and .output.body is the HTTP response body. If you renamed the node, use the name shown on the canvas.
Step 4 — Debug your process
Select Debug in the top toolbar.
Flow runs your process from the Manual Trigger through each node in sequence. When it finishes, the output panel shows the result of each node.
Select the Script node on the canvas to see its output:
{
"title": "sunt aut facere repellat provident occaecati excepturi optio reprehenderit",
"id": 1
}
{
"title": "sunt aut facere repellat provident occaecati excepturi optio reprehenderit",
"id": 1
}
If you see this output, your process is working.
If the process fails, select the failed node to see the error details in the output panel.
Result
Your process runs end-to-end: the Manual Trigger starts execution, the HTTP Request fetches a post from the public API, and the Script node extracts and returns the title and ID. You can see the result in the output panel and confirm each node succeeded with a green indicator on the canvas.
What to build next
- Variables and data flow — understand how data moves between nodes
- HTTP Request node reference — add authentication, headers, and POST requests
- The Canvas — learn Build mode, Debug mode, and keyboard shortcuts