# WordPress Plugin Change Tracker (`afkdigital/wordpress-plugin-change-tracker`) Actor

Tracks WordPress.org plugin versions, updates, changelogs, and compatibility using verified data from the official WordPress.org plugin information API.

- **URL**: https://apify.com/afkdigital/wordpress-plugin-change-tracker.md
- **Developed by:** [AFK Digital](https://apify.com/afkdigital) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.60 / 1,000 successful plugin 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?

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

## WordPress Plugin Change Tracker

An Apify Actor for tracking WordPress.org directory plugin metadata. It reads only WordPress.org's public Plugin Information API (`api.wordpress.org/plugins/info/1.2/`) and supports plugin slugs and canonical WordPress.org plugin URLs.

### Supported fields

- Plugin name and publisher
- Current version and last-updated timestamp
- Changelog page URL and a change marker derived from the API changelog section
- WordPress minimum version, WordPress tested-up-to version, and PHP minimum version when supplied by WordPress.org
- Canonical WordPress.org source URL
- Comparison with the last successful snapshot in the persistent `wordpress-plugin-change-tracker-snapshots` Key-Value Store

No JetBrains, Atlassian, or other marketplace sources are supported. The Actor does not access or alter any other AFK Digital projects or marketplace listings.

### Input

```json
{
  "plugins": ["akismet", "https://wordpress.org/plugins/woocommerce/"],
  "requestDelayMs": 1000
}
```

Provide 1–50 unique plugin slugs or canonical URLs. Requests are sequential, limited to 2 MB responses, and time out after 15 seconds. The delay is 500–10000 ms (default 1000 ms).

### Output

Successful records use `baseline` the first time a plugin is checked, `unchanged` when compared fields match, and `changed` when a verified API field differs. Snapshots persist across Actor runs in the named Key-Value Store. `changes` identifies each changed field and its previous/current values. A WordPress.org API error or incomplete record yields `status: "error"`; that result does not overwrite the last successful snapshot and is not billed.

The changelog content is represented by a SHA-256 change marker; the Actor returns the official changelog page link rather than copying the full changelog into the output.

### Pricing

Pay-per-event bills one `plugin-checked` event per successful plugin record. Error records are not billed, and automatic dataset-item billing is disabled to avoid double charges. Current price: $0.0016 per successful plugin record, 20% below a comparable Apify Actor at $0.002 per check. Apify platform usage is included in the event price.

### Local development

```sh
npm install
npm test
APIFY_LOCAL_STORAGE_DIR=./storage node src/main.js
```

For publishing, build and push this folder using the account's Apify CLI authentication, then complete Store metadata and PPE event pricing in Apify Console.

# Actor input Schema

## `plugins` (type: `array`):

WordPress.org plugin slugs or canonical https://wordpress.org/plugins/{slug}/ URLs. Maximum 50.

## `requestDelayMs` (type: `integer`):

Sequential request delay, from 500 to 10000 ms. Default 1000 ms.

## Actor input object example

```json
{
  "plugins": [
    "akismet",
    "woocommerce"
  ],
  "requestDelayMs": 1000
}
```

# Actor output Schema

## `results` (type: `string`):

One dataset item per plugin checked.

# 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 = {
    "plugins": [
        "akismet",
        "woocommerce"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("afkdigital/wordpress-plugin-change-tracker").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 = { "plugins": [
        "akismet",
        "woocommerce",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("afkdigital/wordpress-plugin-change-tracker").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 '{
  "plugins": [
    "akismet",
    "woocommerce"
  ]
}' |
apify call afkdigital/wordpress-plugin-change-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,afkdigital/wordpress-plugin-change-tracker"
        }
    }
}
```

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/B8IGEseDKshjN5GEd/builds/wCMZgH0zpAcNgflfV/openapi.json