Creoate Scraper - Extract products from category pages and search results

Scrape Creoate product data at scale from category URLs and keyword searches.

This Apify actor is built for teams that need fast, structured Creoate data for product research, lead generation, competitor monitoring, catalog enrichment, and wholesale marketplace analysis.

It collects product listings in a lightweight way, which makes it much faster and lighter than a browser-based scraper. No proxy is required.

What this actor can scrape

• Creoate category pages such as kitchen, stationery, home decor, beauty, gifts, and more
• Creoate search results for keywords such as notebook, candle, mug, or any niche product term
• Product details including product ID, WP ID, product name, slug, categories, prices, discounts, stock, thumbnails, variation labels, and flairs
• Optional wholesaler data including wholesaler ID, name, slug, logo, country, description, rating, minimum order values, and store discount information

Why use this Creoate actor

• High throughput scraping without browser automation
• Supports both category URLs and search queries in the same run
• No proxy setup needed
• Clean structured dataset output ready for export or downstream automation
• Built for Apify with input schema, dataset schema, output schema, and pay-per-event support

Typical use cases

• Monitor new products and pricing across Creoate categories
• Build category-level product datasets for wholesale research
• Search Creoate for specific keywords and export matching products
• Track brands, wholesalers, stock levels, and pricing changes over time
• Feed product data into internal dashboards, spreadsheets, or enrichment pipelines

Input

You can combine category URLs and keyword searches in a single run.

Example input

{
  "startUrls": [
    { "url": "https://www.creoate.com/product-category/kitchen-dining" },
    { "url": "https://www.creoate.com/product-category/home-fragrances" }
  ],
  "searchQueries": ["notebook", "candle"],
  "maxProductsPerUrlQuery": 100,
  "enrichBrandData": true,
  "resultsPerPage": 100,
  "maxConcurrency": 10,
  "includeRaw": false
}

Input fields

• startUrls - Creoate category URLs to scrape
• searchQueries - keywords to scrape from Creoate search
• maxProductsPerUrlQuery - max number of products per category URL and per query
• enrichBrandData - include nested wholesaler and brand information
• resultsPerPage - products fetched per page, up to 100
• maxConcurrency - number of category/query sources processed in parallel
• includeRaw - attach the raw Algolia hit to each item

Output

Each dataset item contains source metadata plus normalized product data.

Main fields

• sourceType, sourceValue, sourceUrl, searchQuery, categorySlug
• id, WP_id, productName, productSlug
• productCategories, productCategoryNames
• productPrice, productDiscount, productBulkDiscount
• productInventory, productOrderQuantity, productMinQuantity
• productVariationLabels, flairs
• productThumbnailUrl
• wholesaler when enrichBrandData is enabled

The actor also stores a run summary in the default key-value store under OUTPUT.

Performance notes

• It is optimized for large listing extraction, not browser rendering
• No proxy is used because it is not required for this workflow
• Higher resultsPerPage and moderate maxConcurrency values usually give the best throughput

Pricing model

This actor is prepared for Apify pay-per-event monetization.

Recommended pricing events:

• apify-actor-start
• result

The actor charges one result event per pushed product item.

Local development

Install dependencies:

$bun install

Run the quick CLI helper:

$bun run search -- notebook --hits 5

Run the actor locally:

$apify run

Local input file:

$storage/key_value_stores/default/INPUT.json

Notes

• This actor focuses on product listing extraction, not checkout, login, or retailer-only workflows
• Output order may differ slightly from what the public website renders in some edge cases
• If you need exact downstream formatting, transform the dataset after run completion or request a custom schema update