> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/url-transcode.md).

# URL Transcode

## Description

**URL encoding** stands for encoding certain characters in a URL. The url\_transcode part does this by replacing them with one or more character triplets that consist of the percent character "`%`" followed by two hexadecimal digits. The two hexadecimal digits of the triplet(s) represent the numeric value of the replaced character. The part also helps you decode a url.

## Use

When you pass information through a URL, you need to make sure it only uses specific allowed characters like: alphabetic characters, numerals, and a few special characters that have meaning in the URL string. Any other characters should be encoded so that they don't cause problems. Any character that is not an alphabetic character, a number or a special character that is being used outside its normal context should be encoded. The part can be created with the folllowing steps:

1. Open the designer
2. Right click
3. Select "add node"
4. Select "Process" (depends on the framework: you may also need to select "url\_transcode" from the popup menu)
5. Double click on the added node (A menu will pop-up on right hand side, if the project is based on the framework, you may see the options of the url\_transcode part already without needing the following step 6.)
6. Insert a "url\_transcode " from the opened menu
7. Save

## Editor Fields

| Field           | Type / Options  | Optional/Mandatory | Description                                                                                                                    |
| --------------- | --------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| Input string    | DataObject/Text | M                  | Here you define the url or provide a data object that contains the url.                                                        |
| Output string   | Text            | M                  | Here you define the name of the place or variable name that will hold the replaced text. In other words it holds your results. |
| Conversion type | Text            | M                  | Here you choose if you want to **Encode** or **Decode** the url.                                                               |
| Resources (TAB) |                 | O                  | See node/part resource and references                                                                                          |

## Example

Please download and import the following [example project](/release-9/example-gallery/example-projects-for-parts/url-transcode-example-project.md) in your workspace.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/url-transcode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.