> 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-bottom.md). # Scroll to bottom Scroll to bottom is an action that commands the browser to immediately scroll the entire screen straight down to the bottom position of the current webpage. This action works automatically and does not have any accompanying configuration parameters. 🎥 Watch the tutorial video: [Here](https://youtu.be/cCTEtuMtz-s). #### Real-world example: Trigger loading of hidden data or find the footer This action is extremely useful and is frequently used in data scraping tasks or automated marketing: * Load more data (Trigger Lazy Load): Many modern websites (like Facebook, Pinterest, e-commerce sites) implement infinite scroll technology. When you first enter the page, the system only displays a few posts. By invoking the Scroll to bottom command, the browser will scroll to the bottom of the page, forcing the website to load additional new data. * Interact with the footer: When you need to click on policy buttons, terms, or social media links that are often fixed at the very bottom of the website, this action helps bring those elements clearly into view on the screen in preparation for subsequent click commands. --- # 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-bottom.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.