Extract Data Block
Extract Data finds every element that matches an item selector, extracts named fields inside each item, and saves the result as an array of rows.
At a glance
What it does
Extract Data is for pages where the same shape repeats: product cards, search results, table rows, job listings, directory entries, or similar lists.
The Item Selector chooses each repeated item. Each field selector then runs inside one item, so every matched item becomes one row in the extracted array.
Fields can extract visible text, outer HTML, or an attribute. When extracting href or src attributes, Scrapeer resolves relative links against the current page URL when possible.
Use it when
- Extract multiple fields from each repeated card or table row.
- Save a list of objects for spreadsheet, email, file, or later processing Blocks.
- Scrape search results, product listings, job boards, directories, or other repeated page sections.
Do not use it when
- You only need one value from the page; use Extract Text.
- The page does not have a repeated item structure.
- You need to open each item detail page before collecting fields; use Extract Data with a Loop or an enrichment-style workflow.
Settings
Start with the Item Selector, then add one field for every column you want in the output rows. Selector settings accept normal Scrapeer variables such as {{selectorName}}.
Item Selector
Required: Yes- Variables
- Yes
- Description
- CSS selector for the repeated item. Each matching item becomes one row.
Fields
Required: No- Variables
- Field selector accepts variables
- Description
- Named field definitions. Each field has a name, selector, extract type, and optional attribute name.
Limit
Required: No- Variables
- No
- Description
- Maximum number of matched items to extract. Empty or 0 means no limit.
No match
Required: No- Variables
- No
- Description
- Choose whether no matched items should fail the Block or continue with an empty list.
Timeout (ms)
Required: No- Variables
- No
- Description
- Optional wait time for the item selector. Strict mode waits up to 30000ms when unset. Continue mode checks once when unset.
Output variable
Required: Recommended- Variables
- Variable name
- Description
- Variable name that stores the extracted array. The default runtime fallback is a generated result variable when no name is set.
Outputs
Extract Data saves an array. Each row is an object whose keys are the field names you configured.
{{outputVariableName}}array<object>The extracted rows. For example, fields named title and price produce rows like { title, price }.
countnumberNumber of extracted rows in Cloud Run output and Inspector summaries when available.
extractedarray<object>Raw run output containing the same extracted row array shown in Inspector previews.
Example Flow
Extract Data usually runs after a page has opened and the repeated content is available.
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.
The Block returns no rows.
- Check
- Check that Item Selector matches repeated items on the current page.
- Fix
- Update the selector, open the correct page first, or add a wait before Extract Data.
A field is empty in some rows.
- Check
- Check whether the field selector exists inside every matched item.
- Fix
- Use a selector that is relative to the item, or accept null for optional fields.
The Block fails when no items are found.
- Check
- Check the No match setting.
- Fix
- Turn on Continue if an empty result should be valid for this Flow.
Local and cloud runs
Local and cloud runs both interpolate Item Selector and field selectors before extraction.
When No match is set to Error, both runtimes wait for the item selector and fail if it does not appear. When No match is set to Continue, Scrapeer returns an empty array instead.
Local and cloud runs both support text, HTML, and attribute field extraction. href and src attributes are resolved to absolute URLs when the browser can resolve them.