The Warehouse NZ Scraper

Scrape product data from The Warehouse New Zealand thewarehouse.co.nz in a clean, structured format.

This actor supports two scraping modes:

• Search mode — scrape products from one or more keyword searches.
• URL mode — scrape from pasted Warehouse search, category, or product URLs.

It can collect product cards, enrich records from product detail pages, extract review data where available, and optionally export product summaries to connected apps through MCP connectors.

What this actor is for

Use this actor when you need structured product data from The Warehouse NZ without manually copying product pages or search results.

It is useful for:

• product research
• price monitoring
• catalog discovery
• ecommerce analysis
• marketplace tracking
• review collection
• internal product workflows

The actor can discover products from search and category pages, or enrich specific products when you already have the exact product URLs.

Output

Each product record can include:

• product URL
• product ID
• title
• brand
• price
• price range text
• currency
• availability
• main image
• full image gallery
• breadcrumbs
• category path
• marketplace flags
• seller name, where available
• rating summary fields
• product details, when detail enrichment is enabled
• customer reviews, when review extraction is enabled

The output is written to the default Apify dataset and can be exported as JSON, CSV, Excel, or through the Apify API.

Reviews

Review extraction is optional.

When customer reviews are available, the actor normalizes them into a consistent structure, including fields such as:

• id
• productId
• rating
• title
• body
• authorAlias
• publishedAt
• verifiedPurchaser
• badges
• secondaryRatings
• vote counts

Not every product exposes review data. If no reviews are available, the product record is still saved normally.

Input highlights

Key input fields include:

• mode — choose search or url
• queries — search terms for search mode
• urls — Warehouse search, category, or product URLs for URL mode
• fetchDetails — enrich product cards using product detail pages
• fetchReviews — fetch normalized customer reviews
• maxReviewsPerProduct — limit the number of reviews collected per product
• sortBy — sort search results by relevance, price, rating, newest, best sellers, or name
• maxItems — maximum number of products to save
• maxPages — maximum number of result pages to visit
• proxy — proxy configuration
• mcpConnectors — optional MCP connector IDs for app export
• notionParentPageUrl — parent Notion page URL for Notion export
• maxNotifyListings — maximum number of products sent to connectors

Sorting options

Search mode supports the following sort options:

• relevance
• price ascending
• price descending
• top rated
• newest
• best sellers
• name ascending
• name descending

URL mode

URL mode accepts:

• search result URLs
• category URLs
• direct product URLs

This is useful when you want to scrape a specific Warehouse page or enrich known products instead of starting from keyword search.

Detail enrichment

When fetchDetails is enabled, the actor visits product detail pages to improve the quality and completeness of each record.

Detail enrichment can add or improve:

• product description
• attributes
• image gallery
• breadcrumbs
• category path
• availability
• marketplace and seller fields

Detail enrichment is recommended when you need higher-quality product records rather than lightweight search-result data.

Export to your apps with MCP connectors

You can optionally send a copy of scraped product summaries into the apps you already use through Model Context Protocol connectors.

Supported connector targets include:

• Notion
• Airtable
• Linear
• Apify

To use connector export:

1. Authorize a connector in Apify under Settings → Integrations.
2. Add one or more connector IDs to mcpConnectors.
3. If exporting to Notion, set notionParentPageUrl.
4. Use maxNotifyListings to limit how many products are sent to connectors in a single run.

Connector export is a side channel only:

• it does not change the dataset output
• it does not block a successful scrape
• connector failures are logged and skipped

What gets sent to connectors

Each connector receives a condensed, human-readable product summary, including fields such as:

• title
• product URL
• price
• availability
• brand
• seller
• key product fields

The full structured JSON record always remains available in the Apify dataset.

Typical use cases

• Scrape Warehouse NZ search results by keyword.
• Monitor prices and availability for selected products.
• Collect product and review data for ecommerce research.
• Enrich known product URLs with detail-page data.
• Send product summaries into Notion for research tracking.
• Push product records into Airtable for manual review.
• Trigger internal workflows using Apify or MCP-connected tools.
• Keep the full dataset in Apify while mirroring a smaller working set into operational apps.

Output notes

• Search mode walks result pages until maxItems or maxPages is reached.
• URL mode supports search, category, and product URLs.
• Detail enrichment improves product descriptions, attributes, images, breadcrumbs, category paths, and availability.
• Review extraction is optional because not every product exposes review data.
• If mcpConnectors is empty, the actor writes only to the default Apify dataset.

Local checks completed

The following checks were completed successfully:

• npm run typecheck
• npm run build
• live search mode
• URL mode
• sort coverage
• detail enrichment
• review extraction