# Parse URI

## Description

This operation is used to break down and analyze a Uniform Resource Identifier (URI) into its components, making it easier to understand and work with the data in a URI.

***

## Data types

These are the input/output expected data types for this operation:

### Input data

![](/files/PLlLS9WDthpZu0nbKCNG) - URLs you want to analyze.

### Output data

![](/files/FiO6hMIDNPuoHDSTAxHC) - Breakdown of the input URLs.

***

## Example

Suppose you want to **analyze** a series of **URLs** in your input data:

1. In your Pipeline, open the required [Action](https://onum.gitbook.io/onum-docs/the-workspace/pipelines/actions) configuration and select the input **Field**.
2. In the **Operation** field, choose **Parse URI**.
3. Give your **Output field** a name and click **Save**. The URLs in your input field will be analyzed. 

For example, for the following URL:

```
https://user:pass@example.com:8080/path/to/resource?key=value#fragment
```

you will get the following analysis:

{% code overflow="wrap" %}

```
Scheme: https Host: example.com:8080 Path: /path/to/resource Arguments: map[key:[value]] User: user Password: pass
```

{% endcode %}

{% hint style="info" %}
You can try out operations with specific values using the **Input** field above the operation. You can enter the value in the example above and check the result in the **Output** field.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onum.com/the-workspace/pipelines/actions/transformation/field-transformation/field-transformation-operations/networking/parse-uri.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.