# Myer Australia Products, Prices, Brands & Offers Scraper (`dromb/myer-wave1`) Actor

Extract Myer Australia products, prices, availability, variants, barcodes, categories, brands, filters, and sale offers for price monitoring, market research, catalog enrichment, and ecommerce automation.

- **URL**: https://apify.com/dromb/myer-wave1.md
- **Developed by:** [Dmitriy Gyrbu](https://apify.com/dromb) (community)
- **Categories:** Automation, E-commerce, Developer tools
- **Stats:** 5 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.40 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Myer AU Product Scraper

Extract Myer Australia product, price, category, brand, offer-page, and product-detail data for ecommerce monitoring and catalog intelligence.

Use this unofficial Myer scraper to monitor assortment changes, track sale pages, enrich product databases, compare brands, discover category shelves, and feed market research or price intelligence workflows.

This is an unofficial actor and is not affiliated with Myer.

### Recommended Saved Tasks

Eight ready-to-run Apify Saved Tasks cover product search monitoring, category shelves, product detail enrichment, brand tracking, offer pages, category maps, brand directories, and filter discovery. Their proven inputs and use cases are documented in [SAVED\_TASKS.md](./SAVED_TASKS.md).

### Supported operations

- `probe` - Check access to the Myer category API.
- `categories` - Build a Myer category map with category IDs, slugs, names, and breadcrumbs.
- `search_filters` - Discover live category and facet values for search or category workflows.
- `search` - Search Myer products by keyword.
- `category` - Browse products from a Myer category shelf.
- `brands` - Extract public brands from Myer navigation.
- `brand` - Monitor a Myer brand page.
- `offers_featured` - Extract the current public promotional strip with offer messages and ready-to-use sale URLs.
- `offers` - Resolve a Myer offer/sale page URL into product results.
- `item` - Extract normalized product detail data by product slug.

### Operation guide

The Apify Console form shows the union of all supported fields, so the visible inputs do not change when you switch `operation`. Use the guide below to know which fields are required.

- `probe`
  Required: none
  Optional: `includeRaw`

- `categories`
  Required: none
  Optional: `depth`, `includeRaw`

- `search_filters`
  Required: none
  Optional: `query`, `slug`, `categoryId`, `category_id`, `facets`, `depth`, `includeRaw`

- `search`
  Required: `query`
  Optional: `page`, `pageSize`, `facets`, `details`, `includeFilters`, `includeRaw`

- `category`
  Required: `slug` or `categoryId`/`category_id`
  Optional: `page`, `pageSize`, `facets`, `details`, `includeFilters`, `includeRaw`

- `brands`
  Required: none
  Optional: `includeRaw`

- `brand`
  Required: `brand` or `url`
  Optional: `page`, `facets`, `details`, `includeFilters`, `includeRaw`

- `offers_featured`
  Required: none
  Optional: `includeRaw`

- `offers`
  Required: `url`
  Optional: `details`, `includeFilters`, `includeRaw`

- `item`
  Required: `slug`
  Optional: `includeRaw`

### Example inputs

```json
{
  "operation": "search",
  "query": "dress",
  "page": 1,
  "pageSize": 10,
  "includeFilters": true,
  "includeRaw": false
}
```

```json
{
  "operation": "categories",
  "depth": 2,
  "includeRaw": false
}
```

```json
{
  "operation": "category",
  "slug": "women-clothing-sale",
  "categoryId": "974553",
  "page": 1,
  "pageSize": 10,
  "includeFilters": true,
  "includeRaw": false
}
```

```json
{
  "operation": "item",
  "slug": "basque-long-sleeve-midi-georgette-dress-with-belt-in-navy",
  "includeRaw": false
}
```

```json
{
  "operation": "brand",
  "brand": "Blaq",
  "page": 1,
  "includeFilters": true,
  "includeRaw": false
}
```

```json
{
  "operation": "brands",
  "includeRaw": false
}
```

```json
{
  "operation": "offers",
  "url": "/c/offers/home--sale",
  "includeFilters": true,
  "includeRaw": false
}
```

```json
{
  "operation": "search_filters",
  "query": "dress",
  "depth": 1,
  "includeRaw": false
}
```

### Output

- Dataset: normalized products, categories, brands, or offers depending on operation
- Key-value store `OUTPUT`: run summary with `source`, `operation`, `success`, `total`, `errors`, `proxy`, and `monetization`

### Output fields

Depending on the operation, dataset items may include:

**Products:**

- `id` - Product ID
- `slug` - Product slug for URL
- `name` - Product name
- `brand` - Brand name
- `source_url` - Full product URL
- `price` - Current price
- `discount_price` - Discount/sale price
- `currency` - AUD
- `saved_amount` - Amount saved
- `saved_percent` - Percentage saved
- `availability` - in\_stock or out\_of\_stock
- `in_stock` - Boolean availability flag
- `buyable` - Boolean buyable flag
- `color` - Product color
- `images` - List of image URLs
- `price_info` - Price breakdown
- `variants` - Product variants (when details=true)
- `barcodes` - EAN barcodes (item operation)
- `attributes` - Product attributes (item operation)
- `breadcrumbs` - Category breadcrumbs (item operation)
- `payment_flags` - Payment method flags (item operation)

**Categories:**

- `id` - Category ID
- `slug` - Category slug
- `name` - Category name
- `children` - Child categories (if depth > 0)
- `breadcrumbs` - Category path

**Brands:**

- `name` - Brand name
- `slug` - Brand slug
- `url` - Brand URL
- `path` - Brand path
- `landing_type` - brand\_page or category\_page
- `section` - Navigation section

**Offers:**

- `message` - Offer message
- `url` - Offer URL
- `path` - Offer path
- `facets` - Parsed facet values

### Notes

- For `category`, first run `categories` and copy a real `slug` or `categoryId` from that output.
- For `item`, use the `slug` from search or category results.
- For `brand`, use the `brand` slug from `brands` output, or pass a full `url` for featured-brand/category pages.
- For `offers`, use a concrete Myer offer path such as `/c/offers/home--sale`.
- The `facets` parameter uses comma-separated exact facet values returned by live Myer responses. Use `search_filters` to discover available facet values.
- `maxItems` can cap the final Dataset for any operation. It is especially useful for brand, offer, category-map, and directory exports.
- Default access strategy is `direct`, the cheapest route verified against the live Myer source. `auto` is available for accounts whose Actor token can create Apify proxy configurations.
- `details=true` on listing endpoints only expands fields already present in the listing payload. It does not trigger hidden per-item detail fetches.

### Use with n8n / Make

An importable n8n example is included in [`examples/n8n_myer_prices_to_google_sheets.json`](examples/n8n_myer_prices_to_google_sheets.json).

The workflow is:

`Myer Actor → wait for run → Dataset products → Google Sheets / Telegram / CRM`

Start a run and wait for completion:

```bash
curl -X POST "https://api.apify.com/v2/acts/dromb~myer-wave1/runs?token=YOUR_APIFY_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"operation":"search","query":"dress","pageSize":10,"maxItems":10}'
```

Read `defaultDatasetId` from the run response and download clean rows:

```bash
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true&format=json&token=YOUR_APIFY_TOKEN"
```

For production workflows, continue only when the run is `SUCCEEDED`, `OUTPUT.success=true`, and `OUTPUT.errors=[]`.

### Proxy behavior

- Recommended mode: `direct`
- Proxy required: No
- Startup strategy: `direct`
- `direct` forces the cheapest route. `auto` tries direct first and can use an Apify datacenter fallback when proxy permission is available. `apify` forces datacenter proxy, and `residential` forces an Australian residential route. `special` is available only for explicit diagnostics and is not recommended for normal Myer runs.
- Browser automation is not required for the current public source.

### Limitations

- Featured offer strips can change or temporarily disappear with Myer's campaigns. Use `offers` with a concrete current sale URL for product extraction.
- Some featured-brand/category brand pages may require URL-based routing via the `url` parameter instead of `brand`.
- Product availability and pricing may vary by location; this actor uses the default public API response.

# Actor input Schema

## `operation` (type: `string`):

Actor operation to execute. The Console form shows all possible fields at once, so check the README for the exact required inputs for each operation.

## `query` (type: `string`):

Required for `search` and `search_filters`. Search phrase.

## `slug` (type: `string`):

Optional for `category`, `search_filters`, and `item`. Category or product slug.

## `categoryId` (type: `string`):

Optional for `category` and `search_filters`. Use `categoryId` or `slug`.

## `category_id` (type: `string`):

Alternative field name for category ID.

## `brand` (type: `string`):

Optional for `brand`. Brand slug or brand name as used in /b/<brand>.

## `url` (type: `string`):

Required for `offers`. Optional for `brand`. Full Myer URL or path such as `/c/offers/home--sale` or `/b/Breville`.

## `page` (type: `integer`):

Optional for `search`, `category`, and `brand`. Page number (1-based).

## `pageSize` (type: `integer`):

Optional for `search` and `category`. Number of results per page (1-120).

## `maxItems` (type: `integer`):

Optional final cap for any operation. Useful for brand, offer, category-map, and directory exports that can expose many rows.

## `facets` (type: `string`):

Optional for `search`, `category`, `brand`, and `search_filters`. Comma-separated exact facet values from live filters.

## `details` (type: `boolean`):

Optional for `search`, `category`, and `brand`. Return richer listing fields already present in the payload. No hidden item fan-out.

## `includeFilters` (type: `boolean`):

Optional for `search`, `category`, `brand`, and `offers`. Include live facet metadata in the response.

## `depth` (type: `integer`):

Optional for `categories` and `search_filters`. Depth: 0 top level only, 1 one level deeper, etc.

## `includeRaw` (type: `boolean`):

Optional for any operation. Include the unnormalized source payload in the OUTPUT summary.

## `proxyConfiguration` (type: `string`):

Direct is the cheapest verified route and is recommended for normal runs. Auto can try Apify proxy fallbacks when the Actor token has proxy permission; residential AU is more expensive.

## Actor input object example

```json
{
  "operation": "search",
  "query": "dress",
  "page": 1,
  "pageSize": 10,
  "details": false,
  "includeFilters": false,
  "depth": 1,
  "includeRaw": false,
  "proxyConfiguration": "direct"
}
```

# Actor output Schema

## `results` (type: `string`):

Normalized dataset items returned by the actor.

## `summary` (type: `string`):

Run summary JSON stored under the OUTPUT key.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dromb/myer-wave1").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("dromb/myer-wave1").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call dromb/myer-wave1 --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=dromb/myer-wave1",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/6q92XbrTLVotIfbKC/builds/68fiv2pWEKSI8ervC/openapi.json