E-Commerce Cluster
Answer natural language e-commerce questions by routing to the right Apify Actor and delivering a synthesized answer via the apify CLI.
CLI rules: Always pass --user-agent apify-awesome-skills/apify-ecommerce, --json (or the relevant --format flag on datasets get-items), and 2>/dev/null. The --user-agent flag is critical for telemetry — never omit it.
Prerequisites
(No need to check it upfront)
- Apify CLI v1.5.0+ (
npm install -g apify-cli)
jq (recommended for quick extraction and filtering; brew install jq on macOS, apt install jq on Linux)
- Authentication via one of:
Verify auth: apify info --user-agent apify-awesome-skills/apify-ecommerce — should show username and userId.
Workflow
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Detect intent and select Actor
- [ ] Step 2: Fetch Actor schema
- [ ] Step 3: Ask user preferences (format, result count)
- [ ] Step 4: Run the Actor and fetch results
- [ ] Step 5: Analyze results and deliver synthesized answer
Step 1: Detect Intent and Select Actor
Classify the user's message into an intent, then pick the right Actor.
Intent signals:
| Signals in user message |
Intent |
| price, cost, cheapest, compare prices, pricing |
pricing |
| review, rating, sentiment, stars, feedback |
reviews |
| bestseller, top selling, most popular, trending |
bestsellers |
| seller, vendor, reseller, who sells |
sellers |
| all products from, scrape store, full catalog |
store-scrape |
| what platform, built on, tech stack, Shopify or WooCommerce |
tech-stack |
| SEO, listing quality, product page audit |
seo-audit |
| competitor funnel, competitor pricing, conversion elements |
competitor |
| search intent, keyword intent, SERP intent |
search-intent |
| match products, same product on different platforms |
product-matching |
| restaurant, food delivery, DoorDash, UberEats, TheFork |
food-delivery |
| enrich store, store metadata, store list |
store-enrichment |
| event, concert, ticket, Eventbrite |
events |
| property, real estate, house listing, Realtor |
real-estate |
| Facebook ads, Meta ads, ad library, competitor ads |
ads-intelligence |
| classified, Craigslist, used item for sale |
classifieds |
| car, used car, vehicle, automotive, Webmotors |
automotive |
| pins, inspiration, Pinterest boards, visual search, Pinterest trends |
content-discovery |
| TikTok Shop, TikTok store, TikTok creator |
tiktok-shop |
| website for sale, domain for sale, Flippa |
website-marketplace |
If multiple intents are detected, ask: "Do you want [intent A] or [intent B]?"
Actor routing table — always try Primary first, switch to Fallback only if it fails or returns 0 results. The Primary actor (apify/e-commerce-scraping-tool) handles most intents once you feed the right input mode:
- Have target URLs (a listing, profile, or category page) →
detailsUrls / listingUrls.
- Have a keyword/marketplace →
keyword + marketplaces (product-details mode).
- Broad discovery (competitor, search-intent, classifieds, automotive, real-estate, website-marketplace, events) → use
searchEngineKeyword (search-engine mode) or keyword/detailsUrls depending on whether you have a query or URLs.
Exception — skip the Primary and go straight to the Fallback for intents the Primary genuinely can't do (different data source or specialized analysis): tech-stack, seo-audit, store-enrichment, product-matching, ads-intelligence, content-discovery (Pinterest), and tiktok-shop. Routing these to the Primary wastes a run and credits.
| Intent |
Platform |
Primary Actor |
Fallback Actor |
pricing |
Amazon / Walmart / generic |
apify/e-commerce-scraping-tool |
— |
pricing |
eBay |
apify/e-commerce-scraping-tool |
ivanvs/ebay-scraper-pay-per-result |
pricing |
Etsy |
apify/e-commerce-scraping-tool |
epctex/etsy-scraper |
pricing |
Google Shopping |
apify/e-commerce-scraping-tool |
epctex/google-shopping-scraper |
pricing |
Facebook Marketplace |
apify/e-commerce-scraping-tool |
apify/facebook-marketplace-scraper |
pricing |
SHEIN |
apify/e-commerce-scraping-tool |
seamless_coffer/shein-product-scraper |
pricing |
Lazada |
apify/e-commerce-scraping-tool |
fatihtahta/lazada-scraper |
pricing |
Canadian Tire |
apify/e-commerce-scraping-tool |
azzouzana/canadiantire-ca-scraper |
pricing |
Tesco |
apify/e-commerce-scraping-tool |
radeance/tesco-scraper |
pricing |
Shopify |
apify/e-commerce-scraping-tool |
trovevault/shopify-products-scraper |
pricing |
WooCommerce |
apify/e-commerce-scraping-tool |
trovevault/woocommerce-products-scraper |
reviews |
Amazon / Walmart / generic |
apify/e-commerce-scraping-tool |
junglee/amazon-reviews-scraper |
reviews |
Trustpilot |
apify/e-commerce-scraping-tool |
casper11515/trustpilot-reviews-scraper |
reviews |
TheFork |
apify/e-commerce-scraping-tool |
jdtpnjtp/thefork-restaurant-scraper-advanced |
bestsellers |
Amazon |
apify/e-commerce-scraping-tool |
junglee/amazon-bestsellers |
sellers |
Amazon |
apify/e-commerce-scraping-tool |
junglee/amazon-seller-scraper |
sellers |
eBay |
apify/e-commerce-scraping-tool |
ivanvs/ebay-scraper-pay-per-result |
store-scrape |
Shopify |
apify/e-commerce-scraping-tool |
trovevault/shopify-products-scraper |
store-scrape |
WooCommerce |
apify/e-commerce-scraping-tool |
trovevault/woocommerce-products-scraper |
store-scrape |
Amazon |
apify/e-commerce-scraping-tool |
junglee/Amazon-crawler |
store-scrape |
Flippa |
apify/e-commerce-scraping-tool |
scraped/flippa-scraper |
tech-stack |
any |
apify/e-commerce-scraping-tool |
trovevault/e-commerce-tech-stack-detector |
seo-audit |
any |
apify/e-commerce-scraping-tool |
trovevault/product-listing-seo-auditor |
competitor |
any |
apify/e-commerce-scraping-tool |
trovevault/competitor-intelligence-scraper---funnel-pricing-conversion |
search-intent |
any |
apify/e-commerce-scraping-tool |
trovevault/ai-serp-intent-extractor---search-intent-classifier |
product-matching |
any |
apify/e-commerce-scraping-tool |
— |
store-enrichment |
any |
apify/e-commerce-scraping-tool |
trovevault/e-commerce-store-data-enricher |
food-delivery |
DoorDash |
apify/e-commerce-scraping-tool |
tri_angle/doordash-store-details-scraper |
food-delivery |
UberEats |
apify/e-commerce-scraping-tool |
e-commerce/ubereats-reviews-scraper |
food-delivery |
TheFork |
apify/e-commerce-scraping-tool |
jdtpnjtp/thefork-restaurant-scraper-advanced |
ads-intelligence |
Facebook / Meta |
apify/e-commerce-scraping-tool |
apify/facebook-ads-scraper |
classifieds |
Craigslist |
apify/e-commerce-scraping-tool |
ivanvs/craigslist-scraper-pay-per-result |
automotive |
Webmotors |
apify/e-commerce-scraping-tool |
stealth_mode/webmotors-auto-search-scraper |
events |
Eventbrite |
apify/e-commerce-scraping-tool |
aitorsm/eventbrite |
real-estate |
Realtor.com |
apify/e-commerce-scraping-tool |
powerai/realtor-properties-search-scraper |
content-discovery |
Pinterest |
apify/e-commerce-scraping-tool |
fatihtahta/pinterest-scraper-search |
tiktok-shop |
TikTok Shop |
apify/e-commerce-scraping-tool |
lemur/tiktok-shop-creators |
website-marketplace |
Flippa |
apify/e-commerce-scraping-tool |
scraped/flippa-scraper |
Escalation — if both Primary and Fallback fail or return 0 results, discover a current alternative live instead of guessing an ID:
# Find relevant, well-rated, pay-per-event Actors for the platform/intent.
# Keep the default relevance sort — `--sort-by popularity` surfaces generic
# big-name scrapers over the platform you actually asked for.
apify actors search "PLATFORM or INTENT keywords" \
--pricing-model PAY_PER_EVENT --limit 10 --json \
--user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null \
| jq '[.items[]
| select(.stats.totalUsers > 100 and .actorReviewRating > 4.5)
| {id: (.username + "/" + .name), users: .stats.totalUsers,
rating: (.actorReviewRating | (. * 100 | round / 100)),
pricing: .currentPricingInfo.pricingModel}]'
Pick the top match. Before running it, confirm it requests only limited permissions (check the Actor's Store page / README — prefer Actors that don't require full account access). If the PAY_PER_EVENT filter returns nothing, drop the --pricing-model flag and re-run, keeping the ≥100-users and ≥4.5-rating bar.
Step 2: Fetch Actor Schema
Fetch the Actor summary, input schema, and README:
# Summary (title, description, pricing, stats)
apify actors info "ACTOR_ID" --user-agent apify-awesome-skills/apify-ecommerce --json 2>/dev/null
# Input schema — use --input WITHOUT --json to get the clean schema directly.
# (Adding --json returns the full ~250 KB actor object instead, with the schema
# buried as an escaped string under .taggedBuilds.latest.build.inputSchema.)
apify actors info "ACTOR_ID" --user-agent apify-awesome-skills/apify-ecommerce --input 2>/dev/null
# README (capabilities, examples, gotchas)
apify actors info "ACTOR_ID" --user-agent apify-awesome-skills/apify-ecommerce --readme 2>/dev/null
Replace ACTOR_ID with the selected Actor (e.g., apify/e-commerce-scraping-tool).
Primary actor input cheat-sheet. apify/e-commerce-scraping-tool is mode-driven — pick fields by intent (always set the matching max…Results cap):
| Intent |
Minimal input |
pricing (keyword) |
{"keyword": "wireless earbuds", "marketplaces": ["www.amazon.com"], "maxProductResults": 50} |
pricing (specific URLs) |
{"detailsUrls": [{"url": "https://…"}], "maxProductResults": 50} |
store-scrape (category) |
{"listingUrls": [{"url": "https://…/category"}], "maxProductResults": 500} |
reviews |
{"keywordReviews": "echo dot", "marketplacesReviews": ["www.amazon.com"], "sortReview": "Most recent", "maxReviewResults": 200} |
sellers |
{"sellerUrls": [{"url": "https://…"}], "maxSellerResults": 50} |
pricing (Google Shopping) |
{"searchEngineKeyword": "ps5", "countryCode": "us", "maxSearchEngineResults": 50} |
food-delivery |
{"keywordDelivery": "pizza", "marketplacesDelivery": ["www.doordash.com"], "addressDelivery": "New York, NY", "maxDeliveryResults": 50} |
For any other actor (or fields not listed), fetch the schema with the --input command above.
Step 3: Ask User Preferences
Before running, ask:
- Output format:
- Quick answer (default) — synthesized answer in chat, no file saved
- CSV — full export saved to disk
- JSON — full export saved to disk
- Result count — suggest defaults by intent:
| Intent |
Default |
pricing |
50 products |
reviews |
200 reviews |
bestsellers |
100 items |
sellers |
50 sellers |
store-scrape |
all (unlimited) |
food-delivery |
50 restaurants |
| all others |
20–50 |
Cost safety: Always set a sensible result limit in the Actor input. For the Primary actor the cap field is mode-specific — maxProductResults, maxReviewResults, maxSellerResults, maxSearchEngineResults, or maxDeliveryResults (there is no single maxResults). For Fallback actors, use whatever the schema exposes (maxResults, resultsLimit, maxItems, maxCrawledPages, etc.). Default to the per-intent values above unless the user explicitly asks for more. Warn the user before running large scrapes (1000+ results) as they consume more Apify credits.
Step 4: Run the Actor and Fetch Results
Two steps: run the Actor (blocks until done), then fetch dataset items in the requested format.
Run the Actor — returns run metadata as JSON; extract defaultDatasetId for the next step:
apify actors call "ACTOR_ID" -i 'JSON_INPUT' \
--user-agent apify-awesome-skills/apify-ecommerce --json 2>/dev/null
From the output use .id (run ID), .status (should be SUCCEEDED), and .defaultDatasetId.
Fetch results — pick the variant based on the user's preference:
# Quick answer: total count + fields + top 5 in chat (no file)
apify datasets info DATASET_ID --json \
--user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null \
| jq '{itemCount, fields, consoleUrl}'
apify datasets get-items DATASET_ID --limit 5 \
--user-agent apify-awesome-skills/apify-ecommerce --format json 2>/dev/null
# CSV file
apify datasets get-items DATASET_ID \
--user-agent apify-awesome-skills/apify-ecommerce --format csv 2>/dev/null > YYYY-MM-DD_OUTPUT_FILE.csv
# JSON file
apify datasets get-items DATASET_ID \
--user-agent apify-awesome-skills/apify-ecommerce --format json 2>/dev/null > YYYY-MM-DD_OUTPUT_FILE.json
Other --format options: jsonl, xlsx, xml, rss, html. Use --offset N to paginate large datasets.
Tip: for anything more than a quick peek, save the dataset to a local file first (with > file.json / > file.csv) and run further analysis from disk. apify datasets get-items always streams over the network, so piping it straight into jq re-downloads the whole thing every iteration.
Combining with jq for quick extraction:
Treat jq as a complement to apify datasets get-items, not a replacement: server-side --limit / --offset / --format keeps cost and bandwidth down. Use jq on a sample item or on a file you already saved.
# Discover real field names from one sample item (Actor outputs vary —
# use this before composing further jq queries)
apify datasets get-items DATASET_ID --limit 1 --format json \
--user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null \
| jq '.[0]'
# Quick aggregation from a JSON file you already saved with the commands above
jq '[.[] | select(.rating != null and .rating >= 4.5)] | length' YYYY-MM-DD_OUTPUT_FILE.json
Step 5: Analyze Results and Deliver Answer
After the run completes, deliver a direct synthesized answer — not a data dump:
- Pricing: price range, average, top 5 cheapest with URLs
- Reviews: average rating, top 3 positive and negative themes, recent snippets
- Bestsellers: top 10 by rank with name, price, rating, URL
- Sellers: total sellers, price range per seller, unauthorized seller flags
- Store-scrape: total products, category breakdown, price range, stock summary
- Tech-stack: platform detected, confidence level, notable plugins
- Food delivery: restaurant count, average rating, price tier breakdown
- Ads intelligence: total ads, active/inactive split, top creative formats
Error Handling
- Auth error → run
apify login, or set APIFY_TOKEN env var
Actor not found → check Actor ID spelling in the routing table
- Run status
FAILED → open the console URL (.consoleUrl from run metadata) for logs
- Timeout / very long run → pass
--timeout <seconds> to apify actors call
No results → broaden the keyword, switch to the Fallback Actor, then use the Escalation discovery command (under Step 1) if both fail
proxy is required → add "proxy": {"useApifyProxy": true} to the Actor input
Platform not detected → default to apify/e-commerce-scraping-tool with generic intent
Gotchas
--input --json is a trap. It returns the full ~250 KB actor object, not the schema. Use apify actors info ID --input --user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null (no --json) for the clean schema; only dig into .taggedBuilds.latest.build.inputSchema if you specifically need it as JSON.
- The Primary actor has no
maxResults field. Its caps are mode-specific (maxProductResults, maxReviewResults, maxSellerResults, maxSearchEngineResults, maxDeliveryResults). Setting maxResults does nothing and the run scrapes unbounded.
- The Primary handles most intents via the right input mode (URLs →
detailsUrls/listingUrls; query → keyword or searchEngineKeyword), including competitor, search-intent, classifieds, automotive, real-estate, website-marketplace, and events. It genuinely can't do tech-stack, seo-audit, store-enrichment, product-matching, ads-intelligence, content-discovery (Pinterest), or tiktok-shop — route those straight to the Fallback.
apify actors call -i expects valid JSON on one line. For inputs with URL arrays or quotes, write a file and pass -i @input.json instead of inlining — shell quoting silently corrupts complex inputs.
datasets get-items always streams over the network. Save to a file once (> file.json), then run jq against the file — don't re-pipe the command into jq repeatedly or you re-download every time.
apify actors search --sort-by popularity ignores relevance. It returns the biggest-name scrapers regardless of your query (an "etsy" search surfaces Instagram/Google Maps Actors). For escalation discovery keep the default relevance sort and filter on stats.totalUsers/actorReviewRating instead.
marketplaces values are full domain slugs, e.g. ["www.amazon.com", "www.ebay.com"] — not "amazon" or display names. Delivery mode is even narrower: marketplacesDelivery only accepts ["www.doordash.com", "www.instacart.com"] (no UberEats — use the e-commerce/ubereats-reviews-scraper fallback for that). Always confirm accepted values from the --input schema's enum before guessing.
1---
2name: apify-ecommerce
3description: Scrape e-commerce data for pricing, reviews, bestsellers, and seller discovery across 30+ platforms including Amazon, Walmart, eBay, Shopify, WooCommerce, and more. Use when user asks about product prices, competitor analysis, store scraping, tech stack detection, food delivery, real estate, or marketplace intelligence.
4author: Luis Pinto
5author_url: https://github.com/luispintoapify
6metadata:
7 source: https://skillmd.com/skills/apify/apify-ecommerce
8 keywords: "ecommerce, pricing, reviews, sentiment, products, sellers, amazon, walmart, ebay, MAP, competitor, research, supply-chain"
9---
10
11# E-Commerce Cluster
12
13Answer natural language e-commerce questions by routing to the right Apify Actor and delivering a synthesized answer via the `apify` CLI.
14
15**CLI rules:** Always pass `--user-agent apify-awesome-skills/apify-ecommerce`, `--json` (or the relevant `--format` flag on `datasets get-items`), and `2>/dev/null`. The `--user-agent` flag is critical for telemetry — never omit it.
16
17## Prerequisites
18(No need to check it upfront)
19
20- Apify CLI v1.5.0+ (`npm install -g apify-cli`)
21- `jq` (recommended for quick extraction and filtering; `brew install jq` on macOS, `apt install jq` on Linux)
22- Authentication via one of:
23 - `apify login` (OAuth, opens browser)
24 - `APIFY_TOKEN` env variable (e.g. `export APIFY_TOKEN=...` or `.env` file)
25 - Token from [Apify Console → Settings → Integrations](https://console.apify.com/settings/integrations)
26
27Verify auth: `apify info --user-agent apify-awesome-skills/apify-ecommerce` — should show username and userId.
28
29## Workflow
30
31Copy this checklist and track progress:
32
33```
34Task Progress:
35- [ ] Step 1: Detect intent and select Actor
36- [ ] Step 2: Fetch Actor schema
37- [ ] Step 3: Ask user preferences (format, result count)
38- [ ] Step 4: Run the Actor and fetch results
39- [ ] Step 5: Analyze results and deliver synthesized answer
40```
41
42### Step 1: Detect Intent and Select Actor
43
44Classify the user's message into an intent, then pick the right Actor.
45
46**Intent signals:**
47
48| Signals in user message | Intent |
49|------------------------|--------|
50| price, cost, cheapest, compare prices, pricing | `pricing` |
51| review, rating, sentiment, stars, feedback | `reviews` |
52| bestseller, top selling, most popular, trending | `bestsellers` |
53| seller, vendor, reseller, who sells | `sellers` |
54| all products from, scrape store, full catalog | `store-scrape` |
55| what platform, built on, tech stack, Shopify or WooCommerce | `tech-stack` |
56| SEO, listing quality, product page audit | `seo-audit` |
57| competitor funnel, competitor pricing, conversion elements | `competitor` |
58| search intent, keyword intent, SERP intent | `search-intent` |
59| match products, same product on different platforms | `product-matching` |
60| restaurant, food delivery, DoorDash, UberEats, TheFork | `food-delivery` |
61| enrich store, store metadata, store list | `store-enrichment` |
62| event, concert, ticket, Eventbrite | `events` |
63| property, real estate, house listing, Realtor | `real-estate` |
64| Facebook ads, Meta ads, ad library, competitor ads | `ads-intelligence` |
65| classified, Craigslist, used item for sale | `classifieds` |
66| car, used car, vehicle, automotive, Webmotors | `automotive` |
67| pins, inspiration, Pinterest boards, visual search, Pinterest trends | `content-discovery` |
68| TikTok Shop, TikTok store, TikTok creator | `tiktok-shop` |
69| website for sale, domain for sale, Flippa | `website-marketplace` |
70
71If multiple intents are detected, ask: *"Do you want [intent A] or [intent B]?"*
72
73**Actor routing table — always try Primary first, switch to Fallback only if it fails or returns 0 results.** The Primary actor (`apify/e-commerce-scraping-tool`) handles most intents once you feed the right input mode:
74
75- **Have target URLs** (a listing, profile, or category page) → `detailsUrls` / `listingUrls`.
76- **Have a keyword/marketplace** → `keyword` + `marketplaces` (product-details mode).
77- **Broad discovery (competitor, search-intent, classifieds, automotive, real-estate, website-marketplace, events)** → use `searchEngineKeyword` (search-engine mode) or `keyword`/`detailsUrls` depending on whether you have a query or URLs.
78
79**Exception — skip the Primary and go straight to the Fallback** for intents the Primary genuinely can't do (different data source or specialized analysis): `tech-stack`, `seo-audit`, `store-enrichment`, `product-matching`, `ads-intelligence`, `content-discovery` (Pinterest), and `tiktok-shop`. Routing these to the Primary wastes a run and credits.
80
81| Intent | Platform | Primary Actor | Fallback Actor |
82|--------|----------|---------------|----------------|
83| `pricing` | Amazon / Walmart / generic | `apify/e-commerce-scraping-tool` | — |
84| `pricing` | eBay | `apify/e-commerce-scraping-tool` | `ivanvs/ebay-scraper-pay-per-result` |
85| `pricing` | Etsy | `apify/e-commerce-scraping-tool` | `epctex/etsy-scraper` |
86| `pricing` | Google Shopping | `apify/e-commerce-scraping-tool` | `epctex/google-shopping-scraper` |
87| `pricing` | Facebook Marketplace | `apify/e-commerce-scraping-tool` | `apify/facebook-marketplace-scraper` |
88| `pricing` | SHEIN | `apify/e-commerce-scraping-tool` | `seamless_coffer/shein-product-scraper` |
89| `pricing` | Lazada | `apify/e-commerce-scraping-tool` | `fatihtahta/lazada-scraper` |
90| `pricing` | Canadian Tire | `apify/e-commerce-scraping-tool` | `azzouzana/canadiantire-ca-scraper` |
91| `pricing` | Tesco | `apify/e-commerce-scraping-tool` | `radeance/tesco-scraper` |
92| `pricing` | Shopify | `apify/e-commerce-scraping-tool` | `trovevault/shopify-products-scraper` |
93| `pricing` | WooCommerce | `apify/e-commerce-scraping-tool` | `trovevault/woocommerce-products-scraper` |
94| `reviews` | Amazon / Walmart / generic | `apify/e-commerce-scraping-tool` | `junglee/amazon-reviews-scraper` |
95| `reviews` | Trustpilot | `apify/e-commerce-scraping-tool` | `casper11515/trustpilot-reviews-scraper` |
96| `reviews` | TheFork | `apify/e-commerce-scraping-tool` | `jdtpnjtp/thefork-restaurant-scraper-advanced` |
97| `bestsellers` | Amazon | `apify/e-commerce-scraping-tool` | `junglee/amazon-bestsellers` |
98| `sellers` | Amazon | `apify/e-commerce-scraping-tool` | `junglee/amazon-seller-scraper` |
99| `sellers` | eBay | `apify/e-commerce-scraping-tool` | `ivanvs/ebay-scraper-pay-per-result` |
100| `store-scrape` | Shopify | `apify/e-commerce-scraping-tool` | `trovevault/shopify-products-scraper` |
101| `store-scrape` | WooCommerce | `apify/e-commerce-scraping-tool` | `trovevault/woocommerce-products-scraper` |
102| `store-scrape` | Amazon | `apify/e-commerce-scraping-tool` | `junglee/Amazon-crawler` |
103| `store-scrape` | Flippa | `apify/e-commerce-scraping-tool` | `scraped/flippa-scraper` |
104| `tech-stack` | any | `apify/e-commerce-scraping-tool` | `trovevault/e-commerce-tech-stack-detector` |
105| `seo-audit` | any | `apify/e-commerce-scraping-tool` | `trovevault/product-listing-seo-auditor` |
106| `competitor` | any | `apify/e-commerce-scraping-tool` | `trovevault/competitor-intelligence-scraper---funnel-pricing-conversion` |
107| `search-intent` | any | `apify/e-commerce-scraping-tool` | `trovevault/ai-serp-intent-extractor---search-intent-classifier` |
108| `product-matching` | any | `apify/e-commerce-scraping-tool` | — |
109| `store-enrichment` | any | `apify/e-commerce-scraping-tool` | `trovevault/e-commerce-store-data-enricher` |
110| `food-delivery` | DoorDash | `apify/e-commerce-scraping-tool` | `tri_angle/doordash-store-details-scraper` |
111| `food-delivery` | UberEats | `apify/e-commerce-scraping-tool` | `e-commerce/ubereats-reviews-scraper` |
112| `food-delivery` | TheFork | `apify/e-commerce-scraping-tool` | `jdtpnjtp/thefork-restaurant-scraper-advanced` |
113| `ads-intelligence` | Facebook / Meta | `apify/e-commerce-scraping-tool` | `apify/facebook-ads-scraper` |
114| `classifieds` | Craigslist | `apify/e-commerce-scraping-tool` | `ivanvs/craigslist-scraper-pay-per-result` |
115| `automotive` | Webmotors | `apify/e-commerce-scraping-tool` | `stealth_mode/webmotors-auto-search-scraper` |
116| `events` | Eventbrite | `apify/e-commerce-scraping-tool` | `aitorsm/eventbrite` |
117| `real-estate` | Realtor.com | `apify/e-commerce-scraping-tool` | `powerai/realtor-properties-search-scraper` |
118| `content-discovery` | Pinterest | `apify/e-commerce-scraping-tool` | `fatihtahta/pinterest-scraper-search` |
119| `tiktok-shop` | TikTok Shop | `apify/e-commerce-scraping-tool` | `lemur/tiktok-shop-creators` |
120| `website-marketplace` | Flippa | `apify/e-commerce-scraping-tool` | `scraped/flippa-scraper` |
121
122**Escalation — if both Primary and Fallback fail or return 0 results**, discover a current alternative live instead of guessing an ID:
123
124```bash
125# Find relevant, well-rated, pay-per-event Actors for the platform/intent.
126# Keep the default relevance sort — `--sort-by popularity` surfaces generic
127# big-name scrapers over the platform you actually asked for.
128apify actors search "PLATFORM or INTENT keywords" \
129 --pricing-model PAY_PER_EVENT --limit 10 --json \
130 --user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null \
131 | jq '[.items[]
132 | select(.stats.totalUsers > 100 and .actorReviewRating > 4.5)
133 | {id: (.username + "/" + .name), users: .stats.totalUsers,
134 rating: (.actorReviewRating | (. * 100 | round / 100)),
135 pricing: .currentPricingInfo.pricingModel}]'
136```
137
138Pick the top match. Before running it, confirm it requests only **limited permissions** (check the Actor's Store page / README — prefer Actors that don't require full account access). If the `PAY_PER_EVENT` filter returns nothing, drop the `--pricing-model` flag and re-run, keeping the ≥100-users and ≥4.5-rating bar.
139
140### Step 2: Fetch Actor Schema
141
142Fetch the Actor summary, input schema, and README:
143
144```bash
145# Summary (title, description, pricing, stats)
146apify actors info "ACTOR_ID" --user-agent apify-awesome-skills/apify-ecommerce --json 2>/dev/null
147
148# Input schema — use --input WITHOUT --json to get the clean schema directly.
149# (Adding --json returns the full ~250 KB actor object instead, with the schema
150# buried as an escaped string under .taggedBuilds.latest.build.inputSchema.)
151apify actors info "ACTOR_ID" --user-agent apify-awesome-skills/apify-ecommerce --input 2>/dev/null
152
153# README (capabilities, examples, gotchas)
154apify actors info "ACTOR_ID" --user-agent apify-awesome-skills/apify-ecommerce --readme 2>/dev/null
155```
156
157Replace `ACTOR_ID` with the selected Actor (e.g., `apify/e-commerce-scraping-tool`).
158
159**Primary actor input cheat-sheet.** `apify/e-commerce-scraping-tool` is mode-driven — pick fields by intent (always set the matching `max…Results` cap):
160
161| Intent | Minimal input |
162|--------|---------------|
163| `pricing` (keyword) | `{"keyword": "wireless earbuds", "marketplaces": ["www.amazon.com"], "maxProductResults": 50}` |
164| `pricing` (specific URLs) | `{"detailsUrls": [{"url": "https://…"}], "maxProductResults": 50}` |
165| `store-scrape` (category) | `{"listingUrls": [{"url": "https://…/category"}], "maxProductResults": 500}` |
166| `reviews` | `{"keywordReviews": "echo dot", "marketplacesReviews": ["www.amazon.com"], "sortReview": "Most recent", "maxReviewResults": 200}` |
167| `sellers` | `{"sellerUrls": [{"url": "https://…"}], "maxSellerResults": 50}` |
168| `pricing` (Google Shopping) | `{"searchEngineKeyword": "ps5", "countryCode": "us", "maxSearchEngineResults": 50}` |
169| `food-delivery` | `{"keywordDelivery": "pizza", "marketplacesDelivery": ["www.doordash.com"], "addressDelivery": "New York, NY", "maxDeliveryResults": 50}` |
170
171For any other actor (or fields not listed), fetch the schema with the `--input` command above.
172
173### Step 3: Ask User Preferences
174
175Before running, ask:
1761. **Output format**:
177 - **Quick answer** (default) — synthesized answer in chat, no file saved
178 - **CSV** — full export saved to disk
179 - **JSON** — full export saved to disk
1802. **Result count** — suggest defaults by intent:
181
182| Intent | Default |
183|--------|---------|
184| `pricing` | 50 products |
185| `reviews` | 200 reviews |
186| `bestsellers` | 100 items |
187| `sellers` | 50 sellers |
188| `store-scrape` | all (unlimited) |
189| `food-delivery` | 50 restaurants |
190| all others | 20–50 |
191
192**Cost safety**: Always set a sensible result limit in the Actor input. For the Primary actor the cap field is **mode-specific** — `maxProductResults`, `maxReviewResults`, `maxSellerResults`, `maxSearchEngineResults`, or `maxDeliveryResults` (there is no single `maxResults`). For Fallback actors, use whatever the schema exposes (`maxResults`, `resultsLimit`, `maxItems`, `maxCrawledPages`, etc.). Default to the per-intent values above unless the user explicitly asks for more. Warn the user before running large scrapes (1000+ results) as they consume more Apify credits.
193
194### Step 4: Run the Actor and Fetch Results
195
196Two steps: run the Actor (blocks until done), then fetch dataset items in the requested format.
197
198**Run the Actor** — returns run metadata as JSON; extract `defaultDatasetId` for the next step:
199
200```bash
201apify actors call "ACTOR_ID" -i 'JSON_INPUT' \
202 --user-agent apify-awesome-skills/apify-ecommerce --json 2>/dev/null
203```
204
205From the output use `.id` (run ID), `.status` (should be `SUCCEEDED`), and `.defaultDatasetId`.
206
207**Fetch results** — pick the variant based on the user's preference:
208
209```bash
210# Quick answer: total count + fields + top 5 in chat (no file)
211apify datasets info DATASET_ID --json \
212 --user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null \
213 | jq '{itemCount, fields, consoleUrl}'
214apify datasets get-items DATASET_ID --limit 5 \
215 --user-agent apify-awesome-skills/apify-ecommerce --format json 2>/dev/null
216
217# CSV file
218apify datasets get-items DATASET_ID \
219 --user-agent apify-awesome-skills/apify-ecommerce --format csv 2>/dev/null > YYYY-MM-DD_OUTPUT_FILE.csv
220
221# JSON file
222apify datasets get-items DATASET_ID \
223 --user-agent apify-awesome-skills/apify-ecommerce --format json 2>/dev/null > YYYY-MM-DD_OUTPUT_FILE.json
224```
225
226Other `--format` options: `jsonl`, `xlsx`, `xml`, `rss`, `html`. Use `--offset N` to paginate large datasets.
227
228**Tip:** for anything more than a quick peek, save the dataset to a local file first (with `> file.json` / `> file.csv`) and run further analysis from disk. `apify datasets get-items` always streams over the network, so piping it straight into `jq` re-downloads the whole thing every iteration.
229
230**Combining with `jq` for quick extraction:**
231
232Treat `jq` as a complement to `apify datasets get-items`, not a replacement: server-side `--limit` / `--offset` / `--format` keeps cost and bandwidth down. Use `jq` on a sample item or on a file you already saved.
233
234```bash
235# Discover real field names from one sample item (Actor outputs vary —
236# use this before composing further jq queries)
237apify datasets get-items DATASET_ID --limit 1 --format json \
238 --user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null \
239 | jq '.[0]'
240
241# Quick aggregation from a JSON file you already saved with the commands above
242jq '[.[] | select(.rating != null and .rating >= 4.5)] | length' YYYY-MM-DD_OUTPUT_FILE.json
243```
244
245### Step 5: Analyze Results and Deliver Answer
246
247After the run completes, deliver a direct synthesized answer — not a data dump:
248
249- **Pricing:** price range, average, top 5 cheapest with URLs
250- **Reviews:** average rating, top 3 positive and negative themes, recent snippets
251- **Bestsellers:** top 10 by rank with name, price, rating, URL
252- **Sellers:** total sellers, price range per seller, unauthorized seller flags
253- **Store-scrape:** total products, category breakdown, price range, stock summary
254- **Tech-stack:** platform detected, confidence level, notable plugins
255- **Food delivery:** restaurant count, average rating, price tier breakdown
256- **Ads intelligence:** total ads, active/inactive split, top creative formats
257
258## Error Handling
259
260- Auth error → run `apify login`, or set `APIFY_TOKEN` env var
261- `Actor not found` → check Actor ID spelling in the routing table
262- Run status `FAILED` → open the console URL (`.consoleUrl` from run metadata) for logs
263- Timeout / very long run → pass `--timeout <seconds>` to `apify actors call`
264- `No results` → broaden the keyword, switch to the Fallback Actor, then use the **Escalation** discovery command (under Step 1) if both fail
265- `proxy is required` → add `"proxy": {"useApifyProxy": true}` to the Actor input
266- `Platform not detected` → default to `apify/e-commerce-scraping-tool` with `generic` intent
267
268## Gotchas
269
270- **`--input --json` is a trap.** It returns the full ~250 KB actor object, not the schema. Use `apify actors info ID --input --user-agent apify-awesome-skills/apify-ecommerce 2>/dev/null` (no `--json`) for the clean schema; only dig into `.taggedBuilds.latest.build.inputSchema` if you specifically need it as JSON.
271- **The Primary actor has no `maxResults` field.** Its caps are mode-specific (`maxProductResults`, `maxReviewResults`, `maxSellerResults`, `maxSearchEngineResults`, `maxDeliveryResults`). Setting `maxResults` does nothing and the run scrapes unbounded.
272- **The Primary handles most intents via the right input mode** (URLs → `detailsUrls`/`listingUrls`; query → `keyword` or `searchEngineKeyword`), including competitor, search-intent, classifieds, automotive, real-estate, website-marketplace, and events. It genuinely **can't** do `tech-stack`, `seo-audit`, `store-enrichment`, `product-matching`, `ads-intelligence`, `content-discovery` (Pinterest), or `tiktok-shop` — route those straight to the Fallback.
273- **`apify actors call -i` expects valid JSON on one line.** For inputs with URL arrays or quotes, write a file and pass `-i @input.json` instead of inlining — shell quoting silently corrupts complex inputs.
274- **`datasets get-items` always streams over the network.** Save to a file once (`> file.json`), then run `jq` against the file — don't re-pipe the command into `jq` repeatedly or you re-download every time.
275- **`apify actors search --sort-by popularity` ignores relevance.** It returns the biggest-name scrapers regardless of your query (an "etsy" search surfaces Instagram/Google Maps Actors). For escalation discovery keep the default relevance sort and filter on `stats.totalUsers`/`actorReviewRating` instead.
276- **`marketplaces` values are full domain slugs**, e.g. `["www.amazon.com", "www.ebay.com"]` — not `"amazon"` or display names. Delivery mode is even narrower: `marketplacesDelivery` only accepts `["www.doordash.com", "www.instacart.com"]` (no UberEats — use the `e-commerce/ubereats-reviews-scraper` fallback for that). Always confirm accepted values from the `--input` schema's `enum` before guessing.