> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/scroll/scroll-to-top.md). # Scroll to top Scroll to top is an action that commands the browser to immediately scroll the entire screen back to the original starting position of the webpage. This action operates completely automatically and does not have any accompanying configuration parameters. 🎥 Watch the tutorial video: [Here](https://youtu.be/cCTEtuMtz-s). #### Practical example: Return to the main menu bar after browsing content When you set up a data scraping or interaction scenario, the processing flow often scrolls the screen down very deep to load more articles (Lazy load) or read comments. After scrolling down, you want to return to the top of the page to click on the search bar, notification panel, or navigation menu fixed at the top: * How to apply: Instead of using the Mouse scroll action with negative parameters multiple times (which is time-consuming and difficult to accurately adjust the scroll step), you only need to insert a single Scroll to top action. * Result: The browser will execute the command to scroll the screen to the top of the website immediately, allowing the script to be ready for the next operations quickly and accurately. --- # 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.gpmautomate.com/automate-en/action-guide/scroll/scroll-to-top.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.