# To base32

## Description

This operation is used to encode data into a Base32 string. Supports custom alphabets or standards (RFC4648 or Hex Extended).

Base32 is an encoding scheme that represents binary data using 32 ASCII characters. It’s commonly used in systems where case-insensitivity is beneficial or where limited character sets are required, such as Google Authenticator secrets (TOTP/HOTP), QR codes, DNS, or URLs.

***

## Data types

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

### Input data

![](https://965373739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkxZeV4nlXcIAjMGZxzLI%2Fuploads%2FEAiKqmMTtuQqEcB1ARyA%2Fimage.png?alt=media\&token=4af58dc3-64ff-4780-aaff-8e73704304ac) - The string you want to encode.

### Output data

![](https://965373739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkxZeV4nlXcIAjMGZxzLI%2Fuploads%2FwTb2oTb0LEAHXBbhwEP9%2Fimage.png?alt=media\&token=9b224990-9f87-48b5-8995-5e7e62e71a79) - Resulting Base32 string.

***

## Parameters

These are the parameters you need to configure to use this operation (mandatory parameters are marked with a <mark style="color:red;">**\***</mark>):

<details>

<summary>Alphabet</summary>

Optionally, you can enter a custom alphabet of 32 unique characters to use for encoding (for example: `a-zABCDE`).

</details>

<details>

<summary>Standard</summary>

This defines which character set is used for encoding. This is crucial because **Base32 has multiple variants**, and decoding must match the correct alphabet to yield meaningful results. Enter one of the following:

* `standard` - Enter this to choose **RFC4648 (Standard).** This is the default Base32 encoding system. This is the character set:&#x20;

```
A B C D E F G H I J K L M N O P
Q R S T U V W X Y Z 2 3 4 5 6 7
```

* `hex` - Enter this to choose **Hex Extended.** Designed to preserve numeric sorting order when Base32 is used. It starts with digits `0–9`, then continues with letters `A–V` — not the same order as standard. This is the character set:&#x20;

```
0 1 2 3 4 5 6 7 8 9 A B C D E F
G H I J K L M N O P Q R S T U V
```

</details>

## Example

Suppose you want to **encode** a series of events into **Base32**:

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 **To Base32**.
3. In the **Standard** option, enter `standard`.
4. Give your **Output field** a name and click **Save**. The values in your input field will be encoded. For example:

<pre><code><strong>hello -> NBSWY3DP
</strong></code></pre>

{% 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/data-format/to-base32.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.