Shopify Store Leads Scraper
Pricing
from $2.17 / 1,000 item extracteds
Shopify Store Leads Scraper
Discover public Shopify merchant domains and enrich them with storefront contacts, social profiles, metadata, and source provenance.
Pricing
from $2.17 / 1,000 item extracteds
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Features
Share
Discover public merchant domains from Shopify's curated Examples pages with Shopify Store Leads Scraper. Export storefront metadata, public contact details and linked social profiles for ecommerce prospect research.
This is a curated directory export, not a search engine for every Shopify store. Contact enrichment is optional and public fields may be missing.
Quick start
Open the Actor, paste this input and select Start. When the run finishes, open its dataset to review the leads.
{"maxItems":10,"enrichStorefronts":true,"maxEnrichmentPagesPerStore":2}
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Choose an example to start with a small, preconfigured input.
- Export Shopify merchant leads — Discover merchant domains and enrich public storefront contact and social details.
What you get
- Merchant discovery: domains listed on Shopify's public Examples pages.
- Source context: outbound merchant link, document-order rank and source capture time.
- Optional enrichment: storefront title, description, visible Shopify signals, public emails, phones and linked social profiles.
- Partial leads: enrichment status and a failure reason when enrichment is incomplete.
Who is it for?
- Shopify app vendors and agencies: build a starting list for merchant research.
- Partnership teams: inspect public storefronts and social profiles.
- Market researchers: export curated merchant examples for further analysis.
Input settings
| Setting | JSON key | Purpose |
|---|---|---|
| Shopify Examples pages | startUrls | Optional Shopify-owned source URLs. Empty input uses the main Examples page. |
| Maximum leads | maxItems | Limit saved leads to 1–5,000. The form default is 20. |
| Enrich storefronts | enrichStorefronts | Collect public contact and social details. Default: true. |
| Extra pages per store | maxEnrichmentPagesPerStore | Check up to 0–10 linked contact/about/support pages. Default: 2. |
| Skip previously scraped domains | skipPreviouslyScraped | Skip domains in history when reusing the same key-value store. Default: false. |
| Require Shopify signal | failOnNoShopifySignal | Only save stores with a detected public Shopify signal. Default: false. |
| Request timeout | requestTimeoutSecs | Per-request limit of 3–120 seconds. Default: 20. |
Input recipes
For a source-only domain export:
{"maxItems":50,"enrichStorefronts":false}
For an enriched list restricted to detected Shopify signals:
{"maxItems":25,"enrichStorefronts":true,"failOnNoShopifySignal":true}
The raw runtime fallback for an omitted maxItems is 25. The input form/schema supplies 20. Set an explicit limit for consistent API and form requests.
Output data
Each saved row represents one merchant domain. This synthetic shape-only example illustrates source-only output, not an observed merchant record:
{"domain":"merchant.example","storeUrl":"https://merchant.example/","sourceUrl":"https://merchant.example/","sourceRank":1,"sourceCapturedAt":"2026-10-25T12:00:00.000Z","myshopifyDomain":null,"shopifyDetected":false,"title":null,"description":null,"emails":[],"phones":[],"socialLinks":{},"enrichmentStatus":"not_requested","failureReason":null,"scrapedAt":"2026-10-25T12:00:01.000Z"}
| Fields | Meaning |
|---|---|
domain, storeUrl | Normalized merchant domain and storefront URL. |
sourceUrl, sourceRank, sourceCapturedAt | Merchant link discovered on the source page, its document-order rank and capture time. |
myshopifyDomain, shopifyDetected | Publicly detected Shopify domain and signal. |
storeCurrency, storeCountry, storeProvince, storeCity | Currency and location from the shop's own settings, the same wherever the run happens. |
storeLocale | Language of the storefront page as served. |
themeName, themeVersion, themeStoreId | Shopify theme the store is built on, its version and Theme Store ID; null for custom themes. |
logoUrl | Store share image or logo. |
title, description | Storefront metadata, or null when unavailable. |
emails, phones | Contact arrays containing value and supporting sourceUrls. |
socialLinks | Linked social profiles grouped by platform. |
enrichmentStatus, failureReason | Enrichment outcome and optional diagnostic. |
scrapedAt | Time the lead row was created. |
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
The start event is charged once when extraction starts. The item event is charged for each saved merchant lead row, including a retained row with partial or failed enrichment.
Enrichment requests are not separate item charges. Skipped domains and stores excluded by the Shopify-signal filter do not produce item charges. The start charge can still apply when no leads are saved.
See the live Pricing tab for current rates and discounts.
Tips for best results
- Start with a small limit. Review a few leads before requesting more.
- Choose source-only output for domains. Leave enrichment off when contacts are not needed.
- Keep contact checks bounded. Increase extra pages only when the additional public context is useful.
- Reuse storage deliberately. History-based skipping requires the same key-value store. Saving a task alone does not share history between runs.
Limits and caveats
- Discovery is limited to merchant links on the supplied Shopify-owned source pages. There is no keyword, category, country or arbitrary merchant-domain search.
- Public contacts can be absent, stale or noisy. Emails are not verified and phone-like text may not be a business phone number.
- Enrichment can be partial or fail when a storefront is unavailable or blocks requests. Source leads are normally retained unless the Shopify-signal filter excludes them.
- Requiring a Shopify signal while disabling enrichment saves no leads. A missing signal does not establish that a store is not Shopify-powered.
- The source rank is document order, not popularity. A source page with no recognized merchant links currently fails the run.
- There is no built-in contact-change detection, product sampling, sitemap export, private Shopify Admin access, customer data or order data.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~shopify-store-leads-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"maxItems":10,"enrichStorefronts":true}'
After completion, request GET https://api.apify.com/v2/datasets/DATASET_ID/items using the returned dataset ID and secure authentication.
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/shopify-store-leads-scraper').call({maxItems: 10, enrichStorefronts: true});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/shopify-store-leads-scraper').call(run_input={'maxItems': 10, 'enrichStorefronts': True})for item in client.dataset(run['defaultDatasetId']).iterate_items():print(item)
MCP and AI agents
You can ask your AI assistant to collect data with Shopify Store Leads Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Shopify Store Leads Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/shopify-store-leads-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Shopify Store Leads Scraper by Fetch Cat, or give it the identifier fetch_cat/shopify-store-leads-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Find ten merchants from Shopify's curated examples and show me their public contact details.”
- “Get twenty merchant domains without contact enrichment and prepare a spreadsheet from the results.”
- “Collect fifteen merchant examples with public social profiles, then summarize which returned leads have Instagram links.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Can I find any Shopify store by keyword or country?
No. The Actor discovers curated merchant examples from Shopify-owned source pages, not the whole Shopify merchant population.
Can I export Shopify store leads through an API?
Yes. Use the API examples above, then read the returned run's dataset. JSON preserves nested contacts and social links. CSV and Excel are also available through dataset export.
Does it need a Shopify login?
No. It reads public source pages and public storefront pages. It does not access private Shopify Admin information.
Why are contacts empty or enrichment marked partial?
The pages checked may contain no matching contacts, or a storefront/contact page may be inaccessible. Check enrichmentStatus and failureReason. Neither proves a merchant is private or deleted.
Does skipping previously scraped domains work across all runs?
Only when the runs reuse the same key-value store containing SEEN-DOMAINS. Normal task reuse does not by itself guarantee shared storage.
What is charged when enrichment fails?
A saved source lead still counts as an item even when enrichment fails. A start charge applies once extraction begins. See the live Pricing tab for current rates.
Which alternatives cover product catalogs or app research?
Use Shopify Products Scraper for public product catalogs and the Shopify App Store tools below for app research.
Related Actors
- Shopify Products Scraper — Export public product catalogs.
- Shopify App Store Scraper — Research apps serving merchants.
- Shopify App Reviews Scraper — Collect public merchant feedback about apps.
- Website Contact Finder — Find contacts on known websites.
- Ecommerce Product Page Scraper — Extract known public product pages.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥