Browser actionNeeds verification

Scroll Page Block

Scroll Page moves the viewport by an amount or toward an element. It is useful for lazy-loaded content and pages where elements appear after scrolling.

At a glance

Best for
Lazy-loaded pages
Modes
By amount or to element
Variables
Selectors accept {{variableName}}
Error handle
Yes

What it does

Scroll Page changes the scroll position on the current page. It can scroll the full page or a configured container element.

Use it before extraction when content is loaded only after the viewport moves.

Use it when

  • Scroll down before extracting cards that load lazily.
  • Move a container list before a click or extraction.
  • Scroll to an element that appears lower on the page.

Do not use it when

  • The next content is available without scrolling.
  • You need repeated pagination logic; use Loop in paginate or scroll mode.
  • The target selector is unreliable or hidden.

Settings

Scroll Page can scroll by an amount or toward an element. Selector fields can use Scrapeer variables.

Scroll type

Required: No
Variables
No
Description
Choose by amount or to element.

Selector

Required: When scrolling to element
Variables
Yes
Description
Target element selector for to-element scrolling.

Container selector

Required: No
Variables
Yes
Description
Scrollable container selector when the page itself is not the scroll target.

Amount and direction

Required: For amount scrolling
Variables
No
Description
Distance and direction for by-amount scrolling.

Wait after scroll

Required: No
Variables
No
Description
Optional pause after scrolling so lazy-loaded content can render.

Outputs

Scroll Page records the scroll action but does not create a user variable.

scrolledboolean

Runtime result that the scroll action completed.

Example Flow

Use Scroll Page before extraction when the page loads more content as the viewport moves.

  1. Open the page.
  2. Scroll the page or container.
  3. Wait for or extract the content that appears.

Errors and fixes

Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.

Nothing changes after scrolling.

Check
Check whether the site scrolls the page or an inner container.
Fix
Set a container selector when the content area has its own scroll bar.

The next Block still runs too early.

Check
Check whether lazy content appears after the scroll.
Fix
Enable wait after scroll or add Wait For Element.

Local and cloud runs

Selector interpolation exists in both runtimes. Container-scroll behavior has known local/cloud differences and should be verified for the target Flow.