> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2024.1/toolbox/string/replace.md).

# Replace

## Overview

![The Replace Node.](/files/2t8Z3Uq8dB12LzDxmpR1)

The **Replace** **Node** replaces a *substring* of a **String** with another given **String**. It receives three inputs:

* `String`: The **String** whose *substring* will be replaced.
* `From`: The *substring* of `String` that will be replaced.
* `To`: The **String** with which `From` will be replaced.

For example, if the inputs are: `String`=`ababab`, `From`=`a`, and `To`=`C`; the output will be `Result`=`CbCbCb`.

[**Scope**](/incari-studio/2024.1/toolbox/overview.md#scopes): **Project**, **Scene**, **Function**, **Prefab**.

## Attributes

![The Replace Node Attributes.](/files/BnQBTL3hWWGaWBYngpZg)

| Attribute | Type       | Description                                                                              |
| --------- | ---------- | ---------------------------------------------------------------------------------------- |
| `String`  | **String** | **String** whose *substring* will be replaced, if none is given in the **Input Socket**. |
| `From`    | **String** | *Substring* of `String` that will be replaced, if none is given in the **Input Socket**. |
| `To`      | **String** | **String** with which `From` will be replaced, if none is given in the **Input Socket**. |

## Inputs

| Input             | Type       | Description                                                           |
| ----------------- | ---------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**  | A standard **Input Pulse**, to trigger the execution of the **Node**. |
| `String`          | **String** | **String** whose *substring* will be replaced.                        |
| `From`            | **String** | *Substring* of `String` that will be replaced.                        |
| `To`              | **String** | **String** with which `From` will be replaced.                        |

## Outputs

| Output             | Type       | Description                                                                                                                            |
| ------------------ | ---------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse**  | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |
| `Result`           | **String** | The resulting **String** after the replacement.                                                                                        |

## See Also

* [**ReplaceRegex**](/incari-studio/2024.1/toolbox/string/replaceregex.md)


---

# 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.incari.com/incari-studio/2024.1/toolbox/string/replace.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.