# WooCommerce Store Leads Scraper — 1M+ Stores, Emails & Tech (`ordesign/woocommerce-store-leads`) Actor

Find active WooCommerce leads across 1M+ indexed stores in 140+ countries with DNS MX-checked emails, phones, socials, live SKU counts, USD prices & product titles. Filter by catalog size & 64 installed/missing plugins (Klaviyo, Meta Pixel, Judge.me) — pay-as-you-go at $4.50/1k.

- **URL**: https://apify.com/ordesign/woocommerce-store-leads.md
- **Developed by:** [Or Cohen](https://apify.com/ordesign) (community)
- **Categories:** Lead generation, E-commerce, Automation
- **Features:** Limited permissions
- **Stats:** 3 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

$4.50 / 1,000 qualified woocommerce store lead (mx-verified email)s

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

Find active WooCommerce stores from an index of **1M+ WooCommerce entries** across 140+ countries (100+ countries with at least 100 stores each)—or enrich your own domain list—and get DNS MX-checked business emails, phone numbers, social links, catalog size, USD prices, and installed plugins. You only pay for stores that return a usable email.

- **Filter 1M+ WooCommerce stores** by country, traffic tier, theme, catalog size, USD price floor, and 64 plugins or pixels (installed or missing).
- **Live checks & noise filtering:** Confirms the storefront is active, the email domain accepts mail, and filtered tech tags (including Google Tag Manager) match live—filtering out parked domains, non-merchant sites, empty catalogs, and agency or plugin-vendor emails before billing *(see [Data Quality and Limitations](#data-quality-and-limitations) for known gaps)*.
- **$4.50 per 1,000 leads** ($0.0045 per lead). Dead stores, stores without emails, and `countOnly` previews are free.
- **Weekly pipelines:** `onlyNewLeads` skips stores you have already received.

***

### Use Cases

- **Agencies & SaaS Sales:** Target stores running ads (`meta-pixel`, `tiktok-pixel`) or a competitor (`mailchimp`, `yotpo`) while missing your tool (`klaviyo`, `judge-me`, `gorgias`).
- **3PLs, Packaging & BNPL:** Exclude tiny shops using `minSkus` and USD prices (`minPriceMaxUsd`, `minPriceMedianUsd`).
- **Wholesale & Partnerships:** Build stockist lists by `keywords` and `country` with emails, phones, and socials.
- **CRM Enrichment:** Pass your own `domains` list to check live WooCommerce activity, catalog size, and tech stack.

***

### Quick Start & Input

1. *(Optional, free)* Run with `countOnly: true` to preview how many stores in the 1M+ index match your filters (~5–10s).
2. Set `country`, `installedTech` / `missingTech`, and optional `minSkus` or `minPriceMaxUsd` in the **Input** tab.
3. Click **Start** and export leads from **Storage -> Dataset** to CSV, Excel, JSON, or Google Sheets.

> **Ready-to-Run Templates:** Check the **Tasks** tab for 1-click presets (missing Klaviyo, missing Judge.me, missing Gorgias/Zendesk, high-ticket 50+ SKUs, UK store leads, role-inbox-only German stores, and bulk domain enrichment).

#### Example Input

```json
{
  "country": "US",
  "missingTech": ["klaviyo"],
  "keywords": ["roaster", "espresso"],
  "minSkus": 10,
  "minPriceMaxUsd": 20,
  "onlyNewLeads": true,
  "dedupScope": "coffee-klaviyo-q4",
  "maxLeads": 100
}
```

#### Market-Sizing Preview (`countOnly`)

Pass `"countOnly": true` (free) to return matching store counts, sample domains, country/theme facets, and all 64 technology slugs:

```json
{
  "country": "US",
  "installedTech": ["meta-pixel"],
  "missingTech": ["klaviyo", "omnisend"],
  "onlyNewLeads": true,
  "countOnly": true
}
```

#### Main Input Filters

See the **Input** tab for all parameters and defaults. The filters most teams use are:

- `country`: Two-letter ISO country code (`"US"`, `"GB"`, `"DE"`, `"AU"`). Leave empty for worldwide.
- `installedTech` / `missingTech`: Plugins or pixels that must (or must not) be present. Matching is case-insensitive with typo suggestions.
- `keywords`: Niche keywords matched against the domain, page metadata, and product titles.
- `minSkus`, `minPriceMaxUsd`, `minPriceMedianUsd`: Catalog size and USD price floors (normalized across 150+ currencies).
- `emailTypes` / `preferPersonalEmails`: Filter to corporate role inboxes (`["role"]`, e.g. `info@`, `sales@`), named inboxes (`["personal"]`), or rank personal emails first. *(Note: named inboxes may constitute personal data under GDPR/UK GDPR; prefer `emailTypes: ["role"]` where required.)*
- `domains` / `excludeDomains`: Enrich a custom domain list or suppress existing clients.

#### Supported Technologies (64 Slugs)

- **Email, SMS & Popups:** `klaviyo`, `mailchimp`, `omnisend`, `attentive`, `postscript`, `drip`, `activecampaign`, `brevo`, `convertkit`, `privy`, `justuno`, `optinmonster`
- **Reviews & UGC:** `judge-me`, `yotpo`, `stamped`, `loox`, `trustpilot`, `okendo`
- **Support & CX:** `gorgias`, `tidio`, `zendesk`, `intercom`, `livechat`, `crisp`, `tawk-to`
- **Subscriptions & Funnels:** `woocommerce-subscriptions`, `recharge`, `bold-subscriptions`, `cartflows`, `funnelkit`
- **Payments & BNPL:** `stripe`, `paypal`, `klarna`, `afterpay`, `affirm`, `square`, `adyen`, `mollie`, `razorpay`, `sezzle`, `splitit`, `amazon-pay`
- **Ad Pixels & Analytics:** `google-analytics`, `meta-pixel`, `tiktok-pixel`, `pinterest-tag`, `snapchat-pixel`, `reddit-pixel`, `linkedin-insight`, `bing-ads`, `triple-whale`, `hotjar`, `microsoft-clarity`
- **SEO, Speed & Infra:** `yoast`, `rank-math`, `all-in-one-seo`, `wpml`, `weglot`, `wp-rocket`, `nitropack`, `cloudflare`, `elementor`, `shipstation`, `hubspot`

#### Cross-Run Deduplication (`onlyNewLeads`)

Enable `onlyNewLeads: true` (on paid Apify plans) to skip stores already delivered in earlier runs. History is stored in a named key-value store (`ecommerce-leads-seen`) in your Apify account. Set `dedupScope` (for example `"client-acme"`) to keep separate history per client or campaign.

***

### Output Example

Core fields buyers map (the full field list and descriptions are on the **Output** tab):

```json
{
  "domain": "acme-coffee-demo.com",
  "store_name": "Acme Coffee Roasters",
  "primary_email": "info@acme-coffee-demo.com",
  "email_type": "role",
  "phones": ["+18005550199"],
  "socials": { "instagram": "https://instagram.com/acme_coffee_demo_example" },
  "installed_tech": ["mailchimp", "judge-me", "google-analytics", "stripe"],
  "tech_sources": { "mailchimp": ["index", "html"], "google-analytics": ["index", "gtm"] },
  "theme_slug": "flatsome",
  "has_wc_api": true,
  "sku_count": 64,
  "currency": "USD",
  "price_median_usd": 24.0,
  "price_max_usd": 129.0,
  "categories": ["Single Origin Coffee", "Espresso Blends"],
  "sample_products": ["Single Origin Ethiopian Pour-Over 12oz"],
  "country": "US",
  "country_source": "store_api_currency",
  "crux_bucket": 100000,
  "verified_at": "2026-11-15T04:55:12Z"
}
```

- **Catalog fields when restricted:** When a merchant blocks public `/wp-json/wc/store/v1/products` access, `has_wc_api` is `false`, SKU/currency/price fields are `null`, and `categories` / `sample_products` are `[]`. Set `hasWcApi: true` (or `minSkus` / `minPriceMaxUsd`) to require catalog data.
- **`crux_bucket`:** CrUX traffic tier: lower values mean more popular sites (for example, `100000` means a top-100k site).
- **`RUN_SUMMARY`:** Saved to each run's Key-Value Store with candidates examined, `stop_reason`, and `skip_reasons`.

***

### Pricing & Cost Examples

- **Flat rate:** **$0.0045 per qualified lead** ($4.50 per 1,000), with no filter multipliers or contact-reveal fees.
- **Free skips & previews:** Dead stores, non-WooCommerce sites, stores without a DNS MX-checked email, `onlyNewLeads` / `excludeDomains` skips, and `countOnly` runs incur **$0** in lead fees (only Apify's ~`$0.00005` run-start compute fee applies).
- **Free plan & caps:** Free Apify accounts can test up to **25 sample leads/run** (up to **10 domains** in `domains` mode, plus unlimited free `countOnly` previews) with CSV, Excel, JSON, and Google Sheets export. Paid Apify plans unlock up to 10,000 leads/run, cross-run `onlyNewLeads` deduplication, and `excludeDomains`. Use **Max cost per run** to cap spend.

**Cost example:** 100 leads = **$0.45**; 1,000 leads = **$4.50**.

***

### Integrations, API & MCP

- **REST API & Python (`apify-client`):** Call `ordesign/woocommerce-store-leads` via SDK or sync HTTP (batches up to ~250 leads):

```bash
curl -X POST "https://api.apify.com/v2/acts/ordesign~woocommerce-store-leads/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"country": "US", "missingTech": ["klaviyo"], "onlyNewLeads": true, "maxLeads": 100}'
```

- **Clay:** Use **Pull Data from Apify Actor** on a scheduled Task, or **Run Apify Actor** to enrich a domain column via `domains`.
- **n8n, Sheets, Make & Zapier:** Import our [weekly n8n outreach workflow](https://api.apify.com/v2/key-value-stores/Icd4uCwNZBkuwxcuH/records/n8n_cartpulse_to_clay_smartlead.json) (**Workflows -> Import from URL**). Native Google Sheets, Make, and Zapier integrations also work directly.
- **MCP (Claude, Cursor, ChatGPT):** Connect `https://mcp.apify.com?tools=ordesign/woocommerce-store-leads`.

***

### Benchmarks & Comparison

Observed in test runs on 2026-11-14 (`n = 739` candidates attempted):

- **Email yield:** `72.3%` (`534 / 739` attempted candidates) passed live storefront, WooCommerce, and DNS MX email checks.
- **First-party email ratio:** `84.3%` (`450 / 534` qualified leads) returned an `@store-domain` address as `primary_email`, with agency and CDN emails filtered out.
- **Catalog coverage:** `~86%` of qualified leads in test runs (`461 / 534`); `~90%` of stores in the current `1M+` index.
- **Run speed:** Averages **~20–40 seconds for 100 leads** and **~4–6 minutes for 1,000 leads**.

Other Actors discover or check WooCommerce stores live (by niche, location, or your own domain list). CartPulse differs by combining a pre-built 1M+ index with live checks, `missingTech` filtering, USD price floors, and per-campaign dedup:

| | **CartPulse** | **Static Database Actors** | **Subscription Tools (Store Leads / BuiltWith)** |
| :--- | :--- | :--- | :--- |
| **Pricing** | Flat $4.50 / 1,000 leads; $0 for skips | ~$1.40–$10 / 1,000, sometimes with filter multipliers or dead-row charges | Typically $79–$499/month recurring plans |
| **Freshness** | 1M+ index + live storefront, Store API & Google Tag Manager checks | Typically pre-scraped snapshots | Periodic crawler snapshots |
| **Email Checks** | Live DNS MX-checked + `role` / `personal` classification | Often unverified static strings | Static lists without per-run MX checks |
| **Tech & Catalog Filters** | 64-slug `installedTech` / `missingTech` + USD price & SKU floors | Static plugin strings; catalog prices often absent unless paired with a live checker | Estimated product counts; tech filters may be tier-gated |
| **Deduplication** | Built-in `onlyNewLeads` + per-campaign `dedupScope` | Manual CSV or offset tracking | Manual list exclusions |

***

### Data Quality and Limitations

- **Heuristic noise filtering:** Filtering for non-merchant sites, parked domains, and agency or third-party emails is heuristic—some non-merchant sites or third-party emails can slip through, and some legitimate stores may be skipped. Report examples in the Issues tab.
- **WooCommerce only:** Non-WooCommerce domains (Shopify, Magento, etc.) in `domains` mode are skipped at no charge.
- **Store API availability:** Around `90%` of indexed stores expose a public Store API. Restricted stores return `null` for SKU and price fields unless `hasWcApi: true` is set.
- **Country inference (`country_source`):** Country-code TLDs map directly (`"cctld"`), while generic `.com` / `.shop` / `.store` domains use Store API currency, email TLD, HTML language, and phone signals. When no signal is found, generic TLDs default to `US` with `country_source: "index_default"`.
- **MX checks, not SMTP probing:** Validation confirms the email domain has active DNS MX records; individual mailboxes are not SMTP-probed.
- **Tech provenance (`tech_sources`):** `installed_tech` merges monthly index detections (`"index"`) with live storefront HTML/header checks (`"html"`), and parses Google Tag Manager (`"gtm"`) whenever `missingTech` is set or a required `installedTech` tag is not yet confirmed in HTML.

***

### Frequently Asked Questions

#### Why did I get fewer leads than `maxLeads`?

Narrow filter combinations can exhaust the matching store pool. Check `RUN_SUMMARY` in the run's Key-Value Store for `stop_reason` and `skip_reasons`.

#### How fresh is the data, and what is checked live vs. indexed?

The 1M+ store index refreshes monthly. On every run (`verified_at`), each returned lead's storefront status, `store_name`, emails, DNS MX records, phones, socials, Store API catalog/prices, and HTML tech signatures (plus Google Tag Manager containers for `missingTech` / unconfirmed `installedTech` filters) are fetched live; `tech_sources` shows whether each tag came from `"index"`, `"html"`, or `"gtm"`.

#### How long are past datasets and `onlyNewLeads` history kept?

Datasets are kept per your Apify plan's retention period—export them after a run, or rename the dataset to keep it indefinitely. Because `ecommerce-leads-seen` is a named key-value store, your `onlyNewLeads` deduplication history is retained indefinitely.

***

### Responsible Use & Attribution

- **Compliance:** Intended for B2B outreach and market research using public business contact details. Users are responsible for complying with CAN-SPAM, GDPR/ePrivacy (`emailTypes: ["role"]`), and PECR.
- **Bounded access:** Performs user-initiated, low-rate HTTP reads of public storefronts, Store API endpoints, Google Tag Manager scripts, and public contact pages (does not fetch or parse `robots.txt`).
- **Data sources:** Incorporates data from the [Google Chrome UX Report (CrUX)](https://developer.chrome.com/docs/crux) (licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/)), technology detections from [HTTP Archive](https://httparchive.org/), and domain rankings from [Tranco](https://tranco-list.eu/).
- **Opt-out:** Merchants can request domain exclusion via this Actor's Issues tab.

# Actor input Schema

## `country` (type: `string`):

Two-letter country code filter (e.g. US, GB, DE, AU, CA). Leave empty for all countries.

## `installedTech` (type: `array`):

Plugins or pixels from the 64-plugin catalog that MUST be installed (case-insensitive, with 'Did you mean?' typo suggestions). Supported 64 slugs — Email/SMS/Popups: klaviyo, mailchimp, omnisend, attentive, postscript, drip, activecampaign, brevo, convertkit, privy, justuno, optinmonster | Reviews: judge-me, yotpo, stamped, loox, trustpilot, okendo | Support: gorgias, tidio, zendesk, intercom, livechat, crisp, tawk-to | Subscriptions/Funnels: woocommerce-subscriptions, recharge, bold-subscriptions, cartflows, funnelkit | Payments/BNPL: stripe, paypal, klarna, afterpay, affirm, square, adyen, mollie, razorpay, sezzle, splitit, amazon-pay | Pixels/Analytics: google-analytics, meta-pixel, tiktok-pixel, pinterest-tag, snapchat-pixel, reddit-pixel, linkedin-insight, bing-ads, triple-whale, hotjar, microsoft-clarity | SEO/Speed/Infra: yoast, rank-math, all-in-one-seo, wpml, weglot, wp-rocket, nitropack, cloudflare, elementor, shipstation, hubspot.

## `missingTech` (type: `array`):

Plugins or pixels from the 64-plugin catalog that MUST NOT be installed on the store, verified live across storefront HTML and Google Tag Manager (case-insensitive, with 'Did you mean?' typo suggestions). Supported 64 slugs — Email/SMS/Popups: klaviyo, mailchimp, omnisend, attentive, postscript, drip, activecampaign, brevo, convertkit, privy, justuno, optinmonster | Reviews: judge-me, yotpo, stamped, loox, trustpilot, okendo | Support: gorgias, tidio, zendesk, intercom, livechat, crisp, tawk-to | Subscriptions/Funnels: woocommerce-subscriptions, recharge, bold-subscriptions, cartflows, funnelkit | Payments/BNPL: stripe, paypal, klarna, afterpay, affirm, square, adyen, mollie, razorpay, sezzle, splitit, amazon-pay | Pixels/Analytics: google-analytics, meta-pixel, tiktok-pixel, pinterest-tag, snapchat-pixel, reddit-pixel, linkedin-insight, bing-ads, triple-whale, hotjar, microsoft-clarity | SEO/Speed/Infra: yoast, rank-math, all-in-one-seo, wpml, weglot, wp-rocket, nitropack, cloudflare, elementor, shipstation, hubspot.

## `keywords` (type: `array`):

Optional keywords matched against domain name and store niche tokens (e.g. coffee, skincare, supplements).

## `maxLeads` (type: `integer`):

Maximum number of DNS MX-checked store leads to produce (Free-plan runs are capped at 25 sample leads).

## `countOnly` (type: `boolean`):

When enabled, queries the 1M+ store index and returns total matching stores, sample domains, market-sizing facets (top_countries, top_themes, has_wc_api_count), and all 64 available_tech_slugs with $0 in lead fees.

## `minSkus` (type: `integer`):

Optional minimum catalog size (sku_count from the WooCommerce Store API). Stores with fewer SKUs are skipped at $0 in lead fees.

## `minPriceMaxUsd` (type: `integer`):

Optional minimum threshold for a store's highest product price (price_max) converted to USD across 150+ ISO-4217 currencies. Keeps stores whose price_max_usd >= X ($0 in lead fees if below threshold).

## `minPriceMedianUsd` (type: `integer`):

Optional minimum threshold for a store's typical product price (price_median across canonical per-SKU prices) converted to USD across 150+ ISO-4217 currencies. Ideal for AOV/catalog qualification without single high-ticket outlier distortion ($0 in lead fees if below threshold).

## `emailTypes` (type: `array`):

Optional filter for contact email classification: select 'role' for corporate role inboxes only (info@, sales@, wholesale@, etc. — ideal for GDPR / ePrivacy minimization), 'personal' for named individual inboxes only, or leave empty / select both for all DNS MX-checked merchant emails.

## `preferPersonalEmails` (type: `boolean`):

When enabled, ranks DNS MX-checked first-party personal/founder emails (e.g. jane@brand.com) ahead of role inboxes for primary_email while falling back to role inboxes when no personal email exists. Named individual emails are personal data under GDPR/UK GDPR — review local rules before enabling in EU/UK campaigns.

## `theme` (type: `string`):

Optional theme filter (e.g. flatsome, astra, woodmart, divi, hello-elementor, storefront).

## `hasWcApi` (type: `boolean`):

When enabled, filters for stores exposing the public /wp-json/wc/store/v1/products catalog endpoint (SKU count & price range).

## `onlyNewLeads` (type: `boolean`):

When enabled on a paid Apify plan, automatically skips domains already delivered in previous runs using persistent history stored in your 'ecommerce-leads-seen' Key-Value Store (skipped on Free-plan sample runs). Ideal for scheduled weekly n8n/Make/Clay pipelines.

## `dedupScope` (type: `string`):

Optional campaign or client ID for onlyNewLeads (e.g. 'agency-client-a' or 'klaviyo-us-q4') so each client or campaign keeps separate deduplication history inside 'ecommerce-leads-seen'.

## `domains` (type: `array`):

Optional list of specific WooCommerce store domains or URLs to enrich live (e.g. \['acme-coffee-demo.com', 'alpine-skincare-demo.com']; Free-plan sample runs enrich up to 10 domains). When provided, CartPulse enriches these exact domains instead of querying the pre-indexed database.

## `excludeDomains` (type: `array`):

Optional list of domains or URLs to exclude from results before live scraping on paid Apify plans (e.g. existing clients, competitors, or suppression lists) without modifying your persistent onlyNewLeads history.

## `maxCruxBucket` (type: `integer`):

Optional popularity ceiling from Google Chrome UX Report: 1000 = major global brands, 10000 = large retailers, 100000 = established DTC brands, 1000000 = growing SMB stores, 10000000 = all indexed stores.

## Actor input object example

```json
{
  "country": "US",
  "installedTech": [],
  "missingTech": [],
  "keywords": [],
  "maxLeads": 10,
  "countOnly": false,
  "emailTypes": [],
  "preferPersonalEmails": false,
  "onlyNewLeads": true,
  "domains": [],
  "excludeDomains": [],
  "maxCruxBucket": 1000000
}
```

# Actor output Schema

## `leads` (type: `string`):

Dataset of DNS MX-checked WooCommerce store leads (or count_only preview item when countOnly is true).

## `runSummary` (type: `string`):

JSON diagnostics record in the default Key-Value Store containing candidates_examined, leads_billed, estimated_ppe_usd, stop_reason, and skip_reasons.

# 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 = {
    "country": "US",
    "maxLeads": 10,
    "onlyNewLeads": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("ordesign/woocommerce-store-leads").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 = {
    "country": "US",
    "maxLeads": 10,
    "onlyNewLeads": True,
}

# Run the Actor and wait for it to finish
run = client.actor("ordesign/woocommerce-store-leads").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "country": "US",
  "maxLeads": 10,
  "onlyNewLeads": true
}' |
apify call ordesign/woocommerce-store-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ordesign/woocommerce-store-leads"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ESz1hWOdK7YQeGGQd/builds/Ka4ccWtZzdrk1xLsT/openapi.json
