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

# Text Parser

The **Text Parser** block is used to extract pattern-based data from a sentence.\
It helps capture values like OTPs, coupon codes, invoice numbers, or API responses.

Steps

1. Add a new node in your flow
2. Go to **Formatter → Text Formatter**
3. Select **Text Parser**
4. Choose or create **Authentication**
5. Enter the **Input Text**
   * Example: `Your coupon code is 456789 use it`
6. In **Text Match After**, enter `is`
7. In **Text Match Before**, enter `use`
8. Click **Run & Save**
9. Check **Run History → Output Response**

The parser will extract the value between the defined patterns (e.g., `456789`).

This is useful for extracting OTPs, codes, invoice numbers, or specific data from text.

{% embed url="<https://www.youtube.com/watch?v=R4fpaF9h1E4>" %}

<br>


---

# 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/text-parser.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.
