> 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/find-text-block.md).

# Find Text Block

### **Steps**

1. Go to your **Automation Builder Flow** and click on **Add Node**.
2. Navigate to **All Applications** → Search for **Text Format**.
3. Select **Find Text**.

#### Setup Authentication

4. Under **Authentication**, select an existing one or 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 Search

7. In the **Text Field**, select or map the text data where you want to perform the search.
8. In the **Value Field**, enter the text/keyword you want to find.
9. Click **Run**, then **Save**.

#### Check Result

10. Go to **Run History** → **Output** → **Response** → **Data**.
11. If the **Index is 0 or greater**, the value is present in the text.
12. If the **Index is less than 0 (e.g., -1)**, the value is not present in the text.

The **Find Text** block is useful for validating keywords, detecting coupon codes, and creating conditional logic inside automation workflows.

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


---

# 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/find-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.