> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/automation-apps-blocks/text-block/replace-text-block.md).

# Replace Text Block

### **Steps**

1. Go to your **Automation Builder Flow** and click on **Add Node**.
2. Select **Add Automation App** (or **Show All Apps**).
3. Search for **Text Formatter** and select **Replace Text**.

#### Setup Authentication

4. If authentication is not available, click **Add New Authentication**.
5. Enter a **Label** and add your **API Key**.
6. Click **Add New Authentication**, then select it from the dropdown.

#### Configure Replace Text

7. Select or map the **Text** in which you want to perform the replacement.
8. In the **Replace Field**, enter the word/value that needs to be replaced.
9. In the **With Field**, enter the new word/value.
10. Click **Run** to preview the replaced text.
11. Click **Save** to apply the changes.

You can now use the updated output in the next steps of your automation flow.

{% embed url="<https://youtu.be/kidUFy3VrtE?si=hj2f2PBG1dgUZQc1>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/automation-apps-blocks/text-block/replace-text-block.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.