# StoreSignal (`overload0x/storesignal`) Actor

- **URL**: https://apify.com/overload0x/storesignal.md
- **Developed by:** [said hammane](https://apify.com/overload0x) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 product checks

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?

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

## StoreSignal — Shopify Price & Restock Monitor

Track a small set of public Shopify products and receive structured evidence when a variant's price or availability changes. Designed for ecommerce operators, agencies, and automated workflows that need repeated observations.

### What each successful check returns

One dataset item per product: current variant prices and stock states, source URL, capture time, whether this is a first baseline, and the changes since the previous successful run of the same watchlist.

Supported events: `price_cut`, `price_increase`, `restocked`, `sold_out`, `variant_added`, and `variant_missing`. Missing does not mean discontinued. First baselines create no change events. A currency mismatch suppresses price comparisons; unknown stock does not become a false sold-out alert.

### Input

```json
{
  "urls": ["https://www.deathwishcoffee.com/products/death-wish-coffee"],
  "watchlist": "coffee-demo"
}
```

Use 1–20 HTTPS Shopify product pages. Locale prefixes are retained; collection prefixes and tracking parameters are normalized. Change the watchlist name for a fresh baseline. The example URL was checked during development; availability can change.

### Repeat monitoring

Run once to create baselines, then run the same input later. Baselines are stored in an Actor-owned named key-value store in the customer's Apify account. Separate watchlist names use separate stores. The console dashboard and this Actor have independent storage.

Create an Apify task with the input and add a daily schedule. Start with daily checks; increase frequency only when customer need and store access preferences justify it. Set a run timeout of 900 seconds and a per-run spending cap. Keep one active run per watchlist. Key-value storage does not provide an atomic distributed lock; overlapping jobs for the same watchlist are unsupported and can duplicate change observations. No schedule is enabled merely by downloading this package.

The dataset can be exported as JSON or consumed through Apify's APIs and workflow integrations. `OUTPUT` in the default key-value store contains the run summary; `ERRORS` contains unsuccessful checks. Failure records do not incur the custom success event fee.

### Scope and limits

- Public, anonymous Shopify product Ajax responses only. No headless browser, login, proxy rotation, CAPTCHA solving, or checkout access.
- Checks read the store's robots rules and stop on a blocked path, HTTP 403, or HTTP 429. Redirects require the final product URL as new input.
- DNS checks reject non-public address results. This is not a general-purpose URL fetch service.
- Currency is extracted from the corresponding product page. No currency is guessed. Price amounts are Shopify integer units divided by 100, including currencies for which Shopify appends two zeros.
- Prices can vary with locale, location, cookies, and store configuration. The recorded value is one anonymous observation. No estimate of revenue or inventory quantity is made.
- At most 1,000 variants per product. Large, malformed, or incomplete responses fail without replacing the last valid baseline. Missing variants remain explicitly ambiguous.
- Changes are observed only between checks; changes that happen and reverse between runs can be missed.
- No outbound email notifications or automatic price changes are built into this version.

### Local run

Requires Node 22. Run `npm ci`, place the input JSON at `storage/key_value_stores/default/INPUT.json`, then `npm start`. The SDK uses local storage when no cloud run environment is present. Named baseline stores persist across runs. Use a new watchlist name to reset.

### Deployment

Deploy this directory as an Apify Actor using the CLI or upload its source in Apify Console. Use **Limited permissions** from the first platform run. The Actor only uses its default storage and named stores it creates itself. Test a baseline, unchanged second run, source failure, and spend-limit stop before publishing. The full release process is in `LAUNCH.md`.

### Pricing status

Prelaunch software. The proposed custom event `product-check` costs **$0.02 per successful product check**, covering every returned variant. Platform configuration determines actual billing. Remove the default dataset-item synthetic event if enabling the custom success event, to prevent double charging. Any enabled Actor-start event must be disclosed separately. Test execution costs before finalizing this price. No earnings or uptime claims are made.

### References

- [Shopify product API](https://shopify.dev/docs/api/ajax/reference/product)
- [Apify Actor permissions](https://docs.apify.com/actors/development/permissions/migration-guide)
- [Apify pay-per-event pricing](https://docs.apify.com/actors/publishing/monetize/pay-per-event)

Implementation and commercial rights belong to the project owner; no third-party product imagery or descriptions are bundled. The merchant named in the example is not affiliated with StoreSignal.

# Actor input Schema

## `urls` (type: `array`):

1–20 public HTTPS product URLs. Collection and locale prefixes are supported. Store access restrictions are respected.

## `watchlist` (type: `string`):

Use the same name across scheduled runs to preserve baselines. Use a different name for a fresh baseline. Run only one job per watchlist at a time.

## Actor input object example

```json
{
  "urls": [
    "https://www.deathwishcoffee.com/products/death-wish-coffee"
  ],
  "watchlist": "default"
}
```

# Actor output Schema

## `productChecks` (type: `string`):

Successful product checks with variant prices, availability, timestamps, baselines, and detected changes.

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

Requested and delivered product counts, failures, detected changes, and spending-limit status.

## `errors` (type: `string`):

Product URLs and error details for unsuccessful checks. Empty when all checks succeed.

# 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 = {
    "urls": [
        "https://www.deathwishcoffee.com/products/death-wish-coffee"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("overload0x/storesignal").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 = { "urls": ["https://www.deathwishcoffee.com/products/death-wish-coffee"] }

# Run the Actor and wait for it to finish
run = client.actor("overload0x/storesignal").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 '{
  "urls": [
    "https://www.deathwishcoffee.com/products/death-wish-coffee"
  ]
}' |
apify call overload0x/storesignal --silent --output-dataset

```

## MCP server setup

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

```

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/isZDLbt7MPk43Lsx5/builds/LXJag9rzlUlPyym7o/openapi.json