> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/components-and-data/flows/node-reference/function/change.md).

# Change

Use a Change node in your Flow to *Set*, *Change*, *Delete*, or *Move* one or more values in the `msg.` object path to other values that you specify.

### Basic Node Usage Example

{% @mermaid/diagram content="flowchart LR
A("msg.payload<br>#quot;myProperty#quot;: #quot;Banana#quot; ") --> B("<div style="text-align:left"><h3>Change</h3>Set: msg.payload.myProperty<br>To string: #quot;Apple#quot;</div>")\
B --> C("msg.payload<br>#quot;myProperty#quot;: #quot;Apple#quot; ")
style A fill:#FFFFFF,stroke:#000000
style B stroke:#00C853,color:#FFFFFF,fill:#00C853
style C fill:#FFFFFF,stroke:#000000" %}

### Configuring a Change Node

To configure a Change node in the [Flow Editor](/documentation-and-resources/components-and-data/flows/node-red-flow-editor.md), drag it from the Palette to the Workspace canvas, then double-click the node to open and configure its behavior.

<figure><img src="/files/10roGPlQjJ7rj9aJzBer" alt="Example of settings for a Change node"><figcaption><p>Example of settings for a Change node</p></figcaption></figure>

1. Provide an optional **Name** for the node.
   * By default a Change node will be shown with a generated label based on how it has been configured, for instance "set msg.payload.myProperty".
2. In the **Rules** section, there will be a single Rule by default.
3. Choose and configure the **Operation** you want to perform.
   * **Set** - set the value of the specified msg. path to another value specified by `msg.`, `flow.`, `global.`, `string`, `number`, `boolean`, `JSON`, `buffer`, `timestamp`, `expression`, or `env variable` data.
   * **Change** - search within the value of the specified msg. path for a value that you specify using `msg.`, `flow.`, `global.`, `string`, `reguar expression`, `number`, `boolean`, or `env variable` data, and replace it with a value that you specify with `msg.`, `flow.`, `global.`, `string`, `number`, `boolean`, `JSON`, `buffer`, or `env variable` data.
   * **Delete** - delete the specified msg. path from the message.
   * **Move** - move a msg. path and its value to a different msg. path.
4. **Add more Rules** by clicking **"+add"** at the bottom left of the Change node panel.
5. **Re-Order Rules** with the drag-and-drop handle on the left of each Rule row.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.contextual.io/documentation-and-resources/components-and-data/flows/node-reference/function/change.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.