# Shopify Store Contact Extractor — Public Emails & Socials (`bin_ai_tools/shopify-store-contact-extractor`) Actor

Extract publicly listed merchant emails and social links from a supplied list of verified Shopify stores, without unreliable search-engine discovery.

- **URL**: https://apify.com/bin_ai_tools/shopify-store-contact-extractor.md
- **Developed by:** [Bin Bin](https://apify.com/bin_ai_tools) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$6.00 / 1,000 verified shopify contacts

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

## Shopify Store Contact Extractor — Public Emails & Socials

Paste known, public Shopify store URLs. The Actor verifies that each shop exposes a public Shopify products feed and collects **publicly posted business contact details** from its homepage and optionally its same-domain contact/about pages.

**No Google/Bing merchant discovery**, no user account login, no private APIs, no customer email data or purchased lead lists. Shopify stores with no public contact signals legitimately yield no result and no PPE charge; unsupported stores are reported as failed checks, not fabricated successes.

### Quick start

Use one to 25 known public Shopify store URLs. Start with one URL to confirm the contact signals before expanding the batch:

```json
{
  "storeUrls": ["https://sundaysproject.com"],
  "maxStoresPerRun": 5,
  "includeContactPages": true,
  "requireEmail": true,
  "requirePhone": false
}
```

The Actor does not search for merchants. Use APIFY-033 to discover candidate Shopify stores, then pass verified public store URLs here. Results are intended for public B2B research and outreach preparation, not private-person data collection.

### Output

One verified public contact record per merchant containing public business emails, phone links, social profiles, and publicly displayed address if available. The additive fields `schemaVersion`, `storeIdentityKey`, deterministic `contactIdentityKeys`, `qualificationStatus`, `shopifyVerificationEvidence`, `contactSignalTypes`, `contactSourcePageUrls`, and `retrievedAt` document why a public contact record was accepted. An OUTPUT record summarizes checks, skips, failures, Dataset deliveries, and actual charged events.

Use APIFY-035 when you already know the Shopify store URLs. APIFY-033 is the discovery product for keyword/niche searches and may also accept direct URLs; both products use the same normalized contact identity convention, while 035 never performs search-engine discovery.

### Billing

Event: `contact-result` for each delivered contact row. The current public Apify PPE configuration is **$0.006 per contact-result**; check the live Pricing tab for the authoritative rate. Unknown or unverified Shopify stores and stores without any public contact signal yield no charge. Dataset writes and PPE charging are not a single atomic transaction; cross-Run exactly-once recovery has not been established.
`OUTPUT` is an object, not a text blob. It reports requested/accepted/duplicate stores, input-cap handling, verified/failed/skipped stores, delivered versus billed contacts, channel-filter skips, and billing failures so repeated contact extraction can be audited.

# Actor input Schema

## `storeUrls` (type: `array`):

Paste known public Shopify storefront URLs; this Actor does not discover stores using search engines.

## `maxStoresPerRun` (type: `integer`):

Hard cap on the number of user-provided Shopify stores to verify per run.

## `includeContactPages` (type: `boolean`):

Checks up to three public same-domain contact/about pages for publicly published contact details.

## `requireEmail` (type: `boolean`):

Skip stores without publicly visible email before writing Dataset or charging.

## `requirePhone` (type: `boolean`):

Skip stores without publicly visible phone before writing Dataset or charging.

## `requestTimeoutSecs` (type: `integer`):

Maximum time for each public Shopify storefront or contact page request.

## Actor input object example

```json
{
  "storeUrls": [
    "https://sundaysproject.com"
  ],
  "maxStoresPerRun": 5,
  "includeContactPages": true,
  "requireEmail": false,
  "requirePhone": false,
  "requestTimeoutSecs": 20
}
```

# Actor output Schema

## `contacts` (type: `string`):

No description

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

Structured batch accounting is stored in the OUTPUT key-value record; the Apify output schema exposes it as a link because nested properties are not accepted by Cloud schema validation.

# 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("bin_ai_tools/shopify-store-contact-extractor").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("bin_ai_tools/shopify-store-contact-extractor").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 '{}' |
apify call bin_ai_tools/shopify-store-contact-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bin_ai_tools/shopify-store-contact-extractor"
        }
    }
}
```

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/E9lisPOdutPqWYfQC/builds/9P7QcoBuOcItlDSOg/openapi.json