> 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/mouse/mouse-scroll.md).

# Mouse scroll

Mouse scroll is the action of instructing the browser to scroll the page up or down by a fixed number of scrolls. This action helps you actively move the screen to areas of content that are hidden below or above the webpage.

🎥 Watch the tutorial video: [Here](https://youtu.be/kQZWs1I76Zo).

#### Configuration parameters:

* Number of scrolls: The number of mouse scrolls to perform.
  * *Positive number (e.g., `5`)*: Scroll the screen down 5 times.
  * *Negative number (e.g., `-3`)*: Scroll the screen up 3 times.

#### Practical example: Scroll the screen to load more data or check the interface

When you are browsing a news page or an e-commerce product listing page, you need to scroll down a fixed short distance to activate the website's lazy load feature for loading new articles:

* Configuration: Drag the Mouse scroll action into the flow ➔ Enter the value `6` in the *Number of scrolls* field.
* Result: The browser will scroll down exactly 6 mouse scrolls decisively to push the screen down.


---

# 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/mouse/mouse-scroll.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.