> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/sap/operations/get-page-title.md).
# Get Page Title
This is a pre-built Action located under the **@Sap Element.** The functionality of this action in Avo Assure is to retrieve the title of the currently displayed SAP application screen or window name and save the result in a dynamic variable.
### Syntax
**Input Value:** `N/A`
| Argument | Description |
| -------- | -------------- |
| N/A | Not Applicable |
**Output Value**
| Argument | Description |
| ------------------------------------------- | ------------------------------------------------------------------------------ |
|
\
(Required)
| Provide the variable to holds the page title. |
|
\ (Optional)
| This dynamic variable holds the status of the action as **True** or **False**. |
**Example:**
#### **Retrieving the Title of the 'SAP' Window Using the Get Page Title Action**
The **Get Page Title** action does not require any input value. The action retrieved page title is stored in the **{PageTitle}** variable as **(e.g. SAP)**
---
# 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://docs.avoautomation.com/avo-assure/actions/sap/operations/get-page-title.md?ask=&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.
