# URL decode

## Description

This operation converts a URL-encoded string back to its original format. URL encoding is used to encode special characters in URLs to ensure safe and proper transmission over the internet. When decoding, these encoded characters are translated back to their human-readable form.

***

## Data types

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

### Input data

![](/files/lPHCVhp93aYrWgLIlhNp) - URL-encoded strings to be decoded.

### Output data

![](/files/lPHCVhp93aYrWgLIlhNp) - Decoded versions of your URLs.

***

## Example

Suppose you want to **decode a series of URL-encoded strings** in your input data. To do it:

1. In your Pipeline, open the required [Action](/the-workspace/pipelines/actions.md) configuration and select the input **Field**.
2. In the **Operation** field, choose **URL decode**.
3. Give your **Output field** a name and click **Save**. Your URL-encoded strings will be converted. 

For example the following URL-encoded string:

```
https%3A%2F%2Fexample.com%2Fsearch%3Fq%3DHello+World%21
```

will be decoded like this:

```
https://example.com/search?q=Hello World!
```

{% 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/url-decode.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.