# n8n Workflow Opportunities – Templates, Nodes & View Changes (`maydit/n8n-workflow-opportunity-monitor`) Actor

Discover public n8n templates, match required integrations and track views or node changes. Use bounded search or exact-ID watchlists with source evidence; no workflow execution or credentials.

- **URL**: https://apify.com/maydit/n8n-workflow-opportunity-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** AI
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 saved observations

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

![n8n Workflow Opportunities — illustrative workflow](https://mayd-it.com/assets/actor-banners/n8n-workflow-opportunity-monitor-44ca1efdedf3.png)

## n8n Workflow Opportunities – Templates, Nodes & View Changes

Which public workflow templates fit the integrations my customer needs, and what changed? Shortlist reusable automation patterns using actual integration metadata and traceable source observations, without executing unreviewed workflows.

### Start with a small useful result

Built for automation agencies and integration consultants building a customer-specific shortlist or maintaining a workflow knowledge base. No API key or login is required. Press **Start** for at most three real public observations, or use one of the exact input recipes below. Each saved row includes `recordId`, `title`, `url`, `sourceUrl` and `observedAt`.

### What you get

One row is one public template observation with ID, title, creator display metadata, cumulative views, source-supplied recent views when available, an explicit price value when available, and distinct integration node types. `nodeCategories` describe the listed nodes, not a guaranteed template category. `descriptionExcerpt` is bounded to 2,000 characters; `descriptionHash` covers the original entire description, and `descriptionTruncated` identifies shortened output. No full workflow definitions, credential configurations, creator contact details or executable code are returned.

### Three practical recipes

#### Discover three public AI workflow templates

Read one bounded official search window and its declared total matches.

```json
{
  "mode": "search",
  "search": "ai",
  "searchLimit": 3,
  "maxResults": 3
}
```

#### Match two templates to an AI Agent requirement

Both exact public templates must include the requested node type; no workflow execution.

```json
{
  "mode": "watchlist",
  "templateIds": [
    "6270",
    "5819"
  ],
  "requiredNodeTypes": [
    "@n8n/n8n-nodes-langchain.agent"
  ],
  "maxResults": 2
}
```

#### Start a video-automation template watch

Track one public template and preserve exact view/node changes for later runs.

```json
{
  "mode": "watchlist",
  "templateIds": [
    "5035"
  ],
  "minViews": 100,
  "maxResults": 1,
  "comparePrevious": true,
  "snapshotName": "video-automation-watch"
}
```

### Scheduled monitoring and reliable comparisons

Set `comparePrevious: true` and a stable `snapshotName`. The first complete run saves a baseline and marks rows `new`; later runs identify `changed` or `unchanged` observations with `changedFields` and `previous`. `onlyChanges: true` suppresses unchanged output and can legitimately produce zero rows. Scope fields are part of the history key; a different watchlist/filter creates a separate scope. We never infer an item was deleted from missing search results.

A failed source, incomplete window, output truncation, deadline or spending cap prevents the baseline from advancing. Previously saved history remains intact. The last accepted billable row is retained even if it reaches your spending cap; rejected rows are never represented as saved. Concurrent history changes are detected instead of overwritten.

### Coverage and limits

- View counts are public counters, not unique visitors, successful executions, sales or guaranteed demand.
- Missing template price remains null; only an explicit numeric zero is marked free. Currency is not invented.
- The selected first-page window can be complete while `sourceUniverseComplete` is false. Search disappearance is never reported as catalog removal.
- Only documented anonymous template API endpoints are used. Its crawler robots policy is not permission to crawl HTML; no HTML crawling, login or restriction bypass is used.
- Up to 20 exact targets and 100 saved results per run; requests are paced by at least one second per source host. The time budget is capped at 120 seconds.
- HTTP 401, 403 or 429 stops remaining source requests. No proxies, login cookies or challenge bypass. Source errors are recorded in `SUMMARY`, never emitted as paid fake data rows.
- A valid filter with no matches can succeed with zero rows. An all-source failure fails honestly.

### Output and pricing

Download JSON or CSV from the dataset, read `SUMMARY` for completeness/source errors, and open the self-contained `RUN_REPORT` for a readable check. Store history is private to the account running the Actor.

The base rate is **$0.002 per confirmed saved observation**, plus **$0.00005 per Actor start**, with standard plan-tier discounts. One observation may contain several nested plans or node types; it remains one result. Source failures and unchanged rows suppressed by `onlyChanges` do not incur a result charge. Apify platform usage may apply according to your plan.

### Source and interpretation

Documented anonymous n8n template metadata API only. Search covers the requested first-page window, not the full catalog. No workflow execution, import-ready definitions, account API or credential export.

[Primary source documentation](https://docs.n8n.io/build/ways-of-building-workflows/use-templates.md). This is an independent tool, not an official product of the source provider. Ask questions or report a source change through this Actor’s Issues tab.

### Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

#### [MCP Registry Monitor - AI Integrations & Version Changes](https://apify.com/maydit/mcp-registry-change-monitor)

Build an automation research shortlist that includes both n8n templates and registered MCP servers.

1. Choose relevant integrations and vendors in each tool independently.
2. Record source-specific identifiers and authentication requirements before designing an automation.

A workflow node is not an MCP server identity. Neither listing proves code safety, production readiness or compatibility; no workflow or server is automatically executed.

#### [Website Content Change Monitor - Markdown & Chunks](https://apify.com/maydit/website-content-change-monitor)

Track the public documentation for integrations used in a shortlisted template.

1. Verify a relevant public documentation page for the selected integration.
2. Configure that accessible static page separately and review documented API changes alongside saved template metadata.

The template metadata does not prove that every linked page is accessible. This pairing does not import or run workflow definitions or provide credentials.

# Actor input Schema

## `mode` (type: `string`):

Search a bounded first-page window or monitor exact public template IDs.

## `search` (type: `string`):

Used in search mode by the official template search. Search order belongs to n8n, not a guaranteed popularity ranking.

## `templateIds` (type: `array`):

Required in watchlist mode, for example 6270. IDs from the public template library; no private workflow IDs.

## `searchLimit` (type: `integer`):

Ask for this many first-page results. Completion covers this selected window, not the full catalog. Filters apply after retrieval.

## `requiredNodeTypes` (type: `array`):

Complete public node type names, for example @n8n/n8n-nodes-langchain.agent or n8n-nodes-base.slack.

## `excludedNodeTypes` (type: `array`):

Exclude templates containing any listed complete node type name.

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

Optional case-insensitive literal terms; matching terms are included in each output row.

## `minViews` (type: `integer`):

Filter using the published cumulative view counter. Views are not unique users, purchases or successful workflow runs.

## `maxResults` (type: `integer`):

Cap real output rows. A smaller cap than the matching selected window marks coverage incomplete and preserves the previous baseline.

## `comparePrevious` (type: `boolean`):

First complete run establishes history. Later complete runs add exact changes; incomplete source/output/spending-limited runs do not advance it.

## `onlyChanges` (type: `boolean`):

Enables comparison. A valid unchanged run can return zero rows. No missing-item removal inference.

## `snapshotName` (type: `string`):

Use a stable name for the same scope. Letters, numbers, underscore or hyphen; 1–80 characters.

## `maxRunSeconds` (type: `integer`):

Requests and pacing honor the remaining time. Time-limited runs preserve prior history.

## Actor input object example

```json
{
  "mode": "search",
  "search": "ai",
  "templateIds": [],
  "searchLimit": 3,
  "requiredNodeTypes": [],
  "excludedNodeTypes": [],
  "keywords": [],
  "minViews": 0,
  "maxResults": 3,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default",
  "maxRunSeconds": 120
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

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

No description

## `report` (type: `string`):

No description

# 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 = {
    "mode": "search",
    "search": "ai",
    "templateIds": [],
    "searchLimit": 3,
    "requiredNodeTypes": [],
    "excludedNodeTypes": [],
    "keywords": [],
    "minViews": 0,
    "maxResults": 3,
    "comparePrevious": false,
    "onlyChanges": false,
    "snapshotName": "default",
    "maxRunSeconds": 120
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/n8n-workflow-opportunity-monitor").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 = {
    "mode": "search",
    "search": "ai",
    "templateIds": [],
    "searchLimit": 3,
    "requiredNodeTypes": [],
    "excludedNodeTypes": [],
    "keywords": [],
    "minViews": 0,
    "maxResults": 3,
    "comparePrevious": False,
    "onlyChanges": False,
    "snapshotName": "default",
    "maxRunSeconds": 120,
}

# Run the Actor and wait for it to finish
run = client.actor("maydit/n8n-workflow-opportunity-monitor").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 '{
  "mode": "search",
  "search": "ai",
  "templateIds": [],
  "searchLimit": 3,
  "requiredNodeTypes": [],
  "excludedNodeTypes": [],
  "keywords": [],
  "minViews": 0,
  "maxResults": 3,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default",
  "maxRunSeconds": 120
}' |
apify call maydit/n8n-workflow-opportunity-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maydit/n8n-workflow-opportunity-monitor"
        }
    }
}
```

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/ue0bAFamNXairVX7k/builds/bJYbb953QefVAUVUN/openapi.json
