# Message Builder

Learn more about this Action in [this article](/the-workspace/pipelines/actions/formatting/message-builder.md).

<details>

<summary>v1.1.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">01/21/2026</mark>

JSON mode performance improved.

</details>

<details>

<summary>v1.1.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">09/10/2025</mark>

New JSON mode added, which allows users to select literal value JSON types.

</details>

<details>

<summary>v1.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">06/04/2025</mark>

Added mode selector with 4 modes:

* **None** - free text editor for the user to input expressions. Same behaviour\
  as previous versions.
* **CSV** - given a value separator, and a list of fields/literals, generate a\
  CSV output.
* **Key-Value** - given a Key-value separator and an external separator, and a\
  list of key value objects, generate a KV list.
* **JSON** - given a list of key-value objects, generate a JSON object (no\
  nesting).

</details>

<details>

<summary>v0.2.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">04/07/2025</mark>

Character `#` is now accepted as a valid character in event field names.

</details>

<details>

<summary>v0.2.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">10/30/2024</mark>

Fixed the issue of surrounding characters when the delimiter is found in a field. The field value should be surrounding only if it contains the delimiter.

</details>

<details>

<summary>v0.1.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">09/05/2024</mark>

Timestamp represented in milliseconds.

</details>

<details>

<summary>v0.1.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">09/05/2024</mark>

Added support for `_{xxx}` tokens. They will be replaced by the content itself.

</details>

<details>

<summary>v0.0.2</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">07/04/2024</mark>

New action command when a field's value includes occurrences of the field delimiter used.

</details>

<details>

<summary>v0.0.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">05/06/2024</mark>

Initial version

</details>


---

# 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/actions/message-builder.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.