> 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/slice-and-parse-function/parse-number-function.md).

# Parse Number Function

he **Parse Number** function is used to extract only numeric values from a string. It automatically removes alphabets, symbols, spaces, and special characters, leaving only numbers.

#### Use Case

If a phone number is received in this format:

`+91-98989-89898`

CRM or WhatsApp messaging may not accept dashes or symbols. Using **Parse Number**, the output becomes:

`919898989898`

#### How to Use

1. Go to your **Workflow** and get the required data (e.g., from a Webhook).
2. Open **CRM** → **Send Text Message**.
3. Select the appropriate **Channel**.
4. In the **WhatsApp Number** field, apply:

   ```
   parse(number_input)
   ```
5. Enter the message content.
6. Click **Run** and **Save**.

If the message is delivered successfully, it confirms the number was cleaned properly.

#### When to Use Parse Number

* Cleaning phone numbers
* Removing dashes or special characters
* Sending data to CRM or APIs
* Ensuring only numeric values are passed to systems

Whenever your data contains unwanted characters and you need only numbers, the **Parse Number** function is the ideal solution.<br>

{% embed url="<https://youtu.be/ketVZ9CvyiI?si=Cz2FQ7q_ujcy-nca>" %}


---

# 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/slice-and-parse-function/parse-number-function.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.