# N8n Workflow Templates Scraper (`automation-lab/n8n-workflow-template-marketplace`) Actor

Search and export public n8n workflow templates with creator, category, integrations, popularity, price, and update metadata.

- **URL**: https://apify.com/automation-lab/n8n-workflow-template-marketplace.md
- **Developed by:** [Stas Persiianenko](https://apify.com/automation-lab) (community)
- **Categories:** Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.92 / 1,000 item processeds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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?

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

## N8n Workflow Templates Scraper

Search and export **n8n workflow templates** as structured records for automation discovery, integration research, and recurring marketplace comparisons.

The Actor uses n8n's public template data and returns template identity, creator, category, nodes, integrations, popularity, price, creation metadata, and—when requested—the importable workflow JSON. It supports keyword search, exact workflow URLs, integration filters, category filters, view thresholds, and bounded result limits.

### What can you do with this Actor?

- Find templates for Slack, HubSpot, Google Sheets, AI agents, and other automation jobs.
- Compare creators, integrations, node counts, public views, and pricing in one dataset.
- Extract a specific public template from its `n8n.io/workflows/{id}` URL.
- Include the workflow blueprint for import analysis or node-level audits.
- Schedule repeat runs and compare datasets to spot new template records or changed public metadata.
- Export results through Apify as JSON, CSV, Excel, XML, RSS, or via API.

The Actor returns source data as observed during each run. It does not send alerts or maintain historical diffs by itself; connect scheduled runs to your own storage or comparison workflow for monitoring.

### Who is it for?

**Automation consultants** can map available templates before designing a client workflow.

**Product and market researchers** can compare popular integrations, creators, prices, and template coverage.

**n8n builders** can discover reusable blueprints and inspect node types before opening each template manually.

**Data teams** can feed a repeatable n8n template catalog into spreadsheets, warehouses, or dashboards.

### Why use this n8n workflow template scraper?

The result is designed for analysis rather than raw page archiving:

- one normalized record per matching template;
- separate human-readable integrations and internal node types;
- creator identity and verification state;
- public view and price signals;
- optional importable workflow JSON;
- exact URL and keyword-search input routes;
- no login, browser, or proxy required for public data;
- bounded retries and explicit errors instead of silent challenge pages.

### What data does it extract?

| Field | Meaning |
| --- | --- |
| `templateId` | Numeric n8n template identifier |
| `name` | Public template name |
| `description` | Creator-provided template description |
| `templateUrl` | Canonical public workflow URL |
| `creator` | Creator ID, name, username, verification, profile, and avatar |
| `categories` | Categories exposed for the template or its nodes |
| `integrations` | Human-readable node and integration names |
| `nodeTypes` | Internal n8n node type identifiers |
| `nodeCount` | Number of exposed nodes |
| `totalViews` | Public total view count |
| `recentViews` | Recent views when the detail endpoint exposes them |
| `price` | Public price; `0` means free and `null` means unavailable |
| `purchaseUrl` | Purchase link when present |
| `createdAt` | Template creation time reported by n8n |
| `status`, `reviewStatus` | Detail status fields when available |
| `workflowJson` | Optional importable blueprint |
| `scrapedAt` | Time this Actor produced the record |

Availability varies by template. Fields not exposed by n8n are returned as `null`, empty arrays, or omitted in the case of optional workflow JSON.

### Getting started

1. Open the Actor in Apify Console.
2. Enter a `searchQuery`, such as `slack`.
3. Optionally add required integrations, categories, or a minimum view count.
4. Set `maxItems` to control the result volume.
5. Enable `includeWorkflowJson` only when you need complete blueprints.
6. Click **Start**.
7. Open the **Dataset** tab to inspect or export results.

A useful first run is:

```json
{
  "searchQuery": "slack",
  "maxItems": 5,
  "includeWorkflowJson": false
}
```

### Input parameters

#### `searchQuery`

Keywords passed to public n8n template search. Search is ignored when `startUrls` is non-empty. Maximum length: 200 characters.

#### `startUrls`

Optional specific public workflow URLs, such as `https://n8n.io/workflows/11807`. Only n8n workflow URLs with a numeric template ID are accepted.

#### `categories`

Keeps templates matching any supplied category, case-insensitively. Category matching requires detail requests.

#### `integrations`

Keeps templates containing every supplied integration. Matching considers both human-readable integration names and internal node types.

#### `minViews`

Keeps templates whose public total view count is at least this number.

#### `maxItems`

Maximum matching records to save. Allowed range: 1–10,000. The Actor may scan more candidates when filters reject records.

#### `includeWorkflowJson`

When enabled, fetches each selected template's detail and adds its importable workflow blueprint. This mode is slower and produces larger dataset records.

### Example output

This shortened record reflects the current output shape:

```json
{
  "templateId": 11807,
  "name": "Answer multi-channel support queries with OpenAI RAG and Supabase",
  "templateUrl": "https://n8n.io/workflows/11807",
  "creator": {
    "name": "Example creator",
    "username": "examplecreator",
    "verified": true,
    "profileUrl": "https://n8n.io/creators/examplecreator"
  },
  "categories": ["AI", "Support"],
  "integrations": ["Slack", "Supabase", "OpenAI"],
  "nodeTypes": ["n8n-nodes-base.slack"],
  "nodeCount": 31,
  "totalViews": 3264,
  "recentViews": 323,
  "price": 0,
  "createdAt": "2025-12-15T00:09:52.569Z",
  "scrapedAt": "2026-08-30T14:40:00.000Z"
}
```

Creator values in this documentation are anonymized. Actual output contains the public creator metadata returned by n8n.

### Filter examples

Find templates that use both HubSpot and Google Sheets:

```json
{
  "searchQuery": "hubspot",
  "integrations": ["HubSpot", "Google Sheets"],
  "minViews": 1,
  "maxItems": 25
}
```

Extract one workflow with its blueprint:

```json
{
  "startUrls": [{ "url": "https://n8n.io/workflows/11807" }],
  "includeWorkflowJson": true,
  "maxItems": 1
}
```

### How much does it cost to extract n8n workflow templates?

The Actor uses pay-per-event pricing: one **Start** event per run plus one **Item processed** event per saved template. The item price decreases across Apify pricing tiers. The active price displayed in Apify Console is authoritative; the table and examples below are updated with the final deployed pricing before launch.

At the initial BRONZE configuration, the run start event is **$0.005** and each saved template event is **$0.0032**. For example, a 10-template run emits one start event and ten item events; a 100-template run emits one start event and 100 item events. Apify calculates the total from the active tier.

Filters do not charge for rejected candidates. Optional workflow JSON is included under the same per-item event and has no separate event charge.

### Monitoring new or changed templates

To monitor the public catalog:

1. Save a stable input with your query and filters.
2. Schedule the Actor daily or weekly.
3. Export each dataset to a durable table or warehouse.
4. Compare records by `templateId`.
5. Treat a new `templateId` as a new template and compare popularity, price, node, or creator fields for changes.

`createdAt` is the public template creation timestamp, not a guaranteed last-modified timestamp. `scrapedAt` records when your observation was made.

### Integrations and exports

Use Apify integrations to send results to:

- Google Sheets for a lightweight comparison catalog;
- webhooks for downstream automation;
- Make or Zapier for routing and notifications;
- cloud storage or a data warehouse for historical snapshots;
- Python, JavaScript, or BI tools through the Dataset API.

Dataset exports support standard Apify formats including JSON, CSV, Excel, XML, and RSS.

### Run through the Apify API

Replace `YOUR_TOKEN` with an Apify API token.

#### cURL

```bash
curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~n8n-workflow-template-marketplace/runs?token=YOUR_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"searchQuery":"slack","maxItems":10}'
```

#### JavaScript

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/n8n-workflow-template-marketplace').call({
  searchQuery: 'slack',
  maxItems: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("automation-lab/n8n-workflow-template-marketplace").call(
    run_input={"searchQuery": "slack", "maxItems": 10}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)
```

### Use with Apify MCP

#### Claude Code

Add the Actor to Claude Code:

```bash
claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/n8n-workflow-template-marketplace"
```

#### Claude Desktop, Cursor, and VS Code

Use this equivalent MCP JSON configuration in Claude Desktop, Cursor, or VS Code:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/n8n-workflow-template-marketplace"
    }
  }
}
```

Example prompts:

- “Find 20 public n8n Slack workflow templates and rank them by total views.”
- “Extract this n8n workflow URL with its importable workflow JSON.”
- “Build a comparison dataset of HubSpot templates that also use Google Sheets.”

### Reliability and limits

The Actor uses n8n's public JSON endpoints directly. It does not require a browser, account, or proxy.

Transient network errors, rate limits, and server errors are retried up to three times with backoff. Permanent invalid-input and 4xx responses fail the run rather than returning a misleading empty dataset.

Search scans at most 100 API pages per run. Highly restrictive filters may therefore return fewer than `maxItems`, even when the broader catalog contains more records.

Node metadata varies between templates. Some list records may expose no nodes; enabling workflow JSON or using an exact workflow URL fetches the richer detail record.

### Legality and responsible use

This Actor extracts public template metadata. Use it in accordance with n8n's terms, applicable laws, and the rights of template creators.

Do not use public creator metadata for harassment, unlawful profiling, or unsolicited bulk messaging. Do not redistribute paid workflow content unless you have the necessary rights. You are responsible for your use and retention of exported data.

This Actor is not affiliated with or endorsed by n8n.

### Troubleshooting

#### Why did my run return no records?

Check spelling and remove filters one at a time. A valid query can naturally have no matching templates. Integration filters require every supplied integration to be present.

#### Why is `workflowJson` missing?

Set `includeWorkflowJson` to `true`. Metadata-only runs omit the field intentionally for speed and smaller datasets.

#### Why was my URL rejected?

Only public `n8n.io/workflows/{numeric-id}` URLs are supported. Category pages, creator pages, shortened links, and other domains are not accepted as workflow URLs.

#### Why are some category or node arrays empty?

n8n does not expose identical metadata for every public template. Empty arrays describe the source response rather than a scraper error.

#### Can I scrape private workflows?

No. The Actor only accesses public n8n template data and does not accept credentials.

### FAQ

#### Can I export to a spreadsheet?

Yes. Download the dataset as CSV or Excel, or use Apify's Google Sheets integration.

#### Can I schedule recurring runs?

Yes. Use an Apify schedule with a saved task, then compare datasets by template `id`.

#### Does the Actor alert me when a template changes?

No. It produces timestamped snapshots. Connect the output to your own diff and notification workflow.

#### Is workflow JSON charged separately?

No. A saved template uses one `item` event whether or not the optional blueprint is included.

#### Does `maxItems` limit scanned candidates?

It limits saved matching records. The Actor can scan additional candidates to satisfy filters, within the bounded page limit.

### Related Automation Lab Actors

- [n8n & Make Integration Templates](https://apify.com/automation-lab/n8n-make-integration-templates) for cross-platform automation template research.
- [JSON to CSV Converter](https://apify.com/automation-lab/json-csv-converter) for custom downstream flattening and conversion.
- [Dataset Deduplication](https://apify.com/automation-lab/dataset-dedup) for removing repeated records from combined snapshots.

# Actor input Schema

## `searchQuery` (type: `string`):

Keywords to find in public n8n workflow templates, such as Slack, HubSpot, or AI agent.

## `startUrls` (type: `array`):

Optional public n8n.io/workflows/{id} URLs. When supplied, searchQuery is ignored.

## `categories` (type: `array`):

Keep templates matching any category, case-insensitively (for example AI or Marketing).

## `integrations` (type: `array`):

Keep templates containing every named integration, such as Slack and Google Sheets.

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

Keep only templates with at least this many total views.

## `maxItems` (type: `integer`):

Maximum number of matching workflow template records to save.

## `includeWorkflowJson` (type: `boolean`):

Fetch each template detail and include its workflow blueprint. This is slower than metadata-only extraction.

## Actor input object example

```json
{
  "searchQuery": "slack",
  "startUrls": [],
  "categories": [],
  "integrations": [],
  "minViews": 0,
  "maxItems": 20,
  "includeWorkflowJson": false
}
```

# Actor output Schema

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

Default dataset containing all matching workflow template records.

# 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 = {
    "searchQuery": "slack",
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("automation-lab/n8n-workflow-template-marketplace").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 = {
    "searchQuery": "slack",
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("automation-lab/n8n-workflow-template-marketplace").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 '{
  "searchQuery": "slack",
  "maxItems": 20
}' |
apify call automation-lab/n8n-workflow-template-marketplace --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,automation-lab/n8n-workflow-template-marketplace"
        }
    }
}

```

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/rPpvUW0owDNsn0mh2/builds/PVCGpKGbLZyFwJuzn/openapi.json