# URL encode transform action

## Use case

You are writing query parameters and the API you are sending them to requires them to be URL encoded.

## Overview

When given a string this transform will URL encode it.

<figure><img src="https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FtWkUUby4r6PxfJSUCeKM%2FScreenshot%202025-08-21%20at%201.57.34%E2%80%AFPM.png?alt=media&#x26;token=c2174532-f878-4ec8-86ca-8903abf3037f" alt=""><figcaption></figcaption></figure>

## Parameters

<table><thead><tr><th width="217">Parameter</th><th width="417.3333333333333">Description</th><th data-type="checkbox">Required</th></tr></thead><tbody><tr><td>String</td><td>String to URL encode.</td><td>true</td></tr></tbody></table>

## Usage

<details>

<summary>Example: Encode a string</summary>

Inputs: **String**: This-is-\@-test!

</details>

## Results output

```
This-is-%40-test%21
```


---

# 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.rewst.help/documentation/automations/actions-in-rewst/transform-actions/url-encode-transform-action.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.