# Your first Flow

> Build and debug your first Flow process in under five minutes by calling an API, extracting data, and inspecting the output.

## 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.

![Flow canvas in Studio Web showing the default Manual Trigger node and the bottom toolbar with the + button.](https://dev-assets.cms.uipath.com/assets/images/maestro/flow-canvas-3aaccc65.webp)

## 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:

1. Set **Method** to `GET`
2. Set **URL** to `https://jsonplaceholder.typicode.com/posts/1`

Leave all other fields at their defaults.

![Canvas showing a Manual Trigger connected to an HTTP Request node, with the HTTP Request properties panel open showing Method set to GET and the URL field.](https://dev-assets.cms.uipath.com/assets/images/maestro/flow-http-request-3dcc8e72.webp)

## 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:

```javascript
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.

![Canvas showing three connected nodes: Manual Trigger, HTTP Request, and Script. The Script properties panel is open with the JavaScript code visible in the editor.](https://dev-assets.cms.uipath.com/assets/images/maestro/flow-script-ad789fff.webp)

:::note
`$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:

```json
{
  "title": "sunt aut facere repellat provident occaecati excepturi optio reprehenderit",
  "id": 1
}
```

If you see this output, your process is working.

![Canvas in debug mode with all three nodes showing green success indicators. The Script node is selected and the output panel shows the JSON result with title and id fields.](https://dev-assets.cms.uipath.com/assets/images/maestro/flow-debug-f334338e.webp)

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](variables-and-data-flow.md)** — understand how data moves between nodes
- **[HTTP Request node reference](node-http-request.md)** — add authentication, headers, and POST requests
- **[The Canvas](canvas-overview.md)** — learn Build mode, Debug mode, and keyboard shortcuts