n8n Workflow Opportunities – Templates, Nodes & View Changes avatar

n8n Workflow Opportunities – Templates, Nodes & View Changes

Pricing

from $1.20 / 1,000 saved observations

Go to Apify Store
n8n Workflow Opportunities – Templates, Nodes & View Changes

n8n Workflow Opportunities – Templates, Nodes & View Changes

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.

Pricing

from $1.20 / 1,000 saved observations

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Features

Limited permissions

Share

n8n Workflow Opportunities — illustrative workflow

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.

{
"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.

{
"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.

{
"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. 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

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

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.