n8n Nodes Directory Scraper

Scrape the public n8n integrations and nodes directory into a clean Apify dataset. This Actor extracts one item per n8n node or integration, including package names, descriptions, categories, core/community/trigger flags, popularity metadata, public URLs, and logo links.

Use it to build searchable automation catalogs, monitor new community nodes, enrich integration intelligence, and compare the n8n ecosystem without manually browsing the website.

What does n8n Nodes Directory Scraper do?

The Actor fetches https://n8n.io/integrations/, reads the public serialized page payload, applies your filters, and saves structured node records.

It is HTTP-only and does not require an n8n account.

Key capabilities:

• ✅ Extract public n8n node and integration metadata
• ✅ Filter by search term, category, and node type
• ✅ Separate core, community, trigger, and regular nodes
• ✅ Save category names and category URLs
• ✅ Capture package/internal names for technical matching
• ✅ Export JSON, CSV, Excel, HTML, or API results from Apify

Who is it for?

Automation agencies use it to map which apps are supported by n8n before proposing workflow builds.

SaaS partnership teams use it to check whether their product, competitors, or adjacent tools already have n8n integrations.

Developers use it to discover community packages, trigger nodes, and integration metadata for internal catalogs.

Growth teams use it to monitor the automation ecosystem and identify high-fit integration opportunities.

Data teams use it to enrich CRM, product, or marketplace records with n8n support signals.

Why use it?

The n8n website is useful for humans, but teams often need the same information in a repeatable dataset.

This Actor gives you:

• 📦 Structured rows instead of manual copy-paste
• 🔎 Search and category filters
• 🧩 Node-type flags for segmentation
• 🔗 Public detail URLs for follow-up research
• 🕒 Repeatable runs for monitoring new integrations
• ⚙️ API-friendly output for enrichment workflows

Data you can extract

Field	Description
displayName	Human-readable n8n node name
packageName	Internal/package identifier when exposed
description	Public node description
slug	n8n URL slug
url	Public n8n detail page URL
categories	Category names
categoryUrls	Public category page URLs
categoryDetails	Category name and URL objects
isCoreNode	Whether the node is a core n8n node
isTrigger	Whether the node is marked as a trigger
isCommunityNode	Whether it is a community node
mostPopular	Popularity flag from the directory payload
popularity	Numeric popularity value when present
createdAt	Creation timestamp when present
logoUrl	Public logo or icon URL
logoIcon	Icon key when exposed
aliases	Alternate names or aliases
scrapedAt	Actor scrape timestamp

How much does it cost to scrape n8n nodes?

The Actor uses pay-per-event pricing.

You pay a small start fee for each run and a per-item fee for every node saved to the dataset. Keep maxItems low for tests and increase it for production exports.

Exact prices are shown on the Apify Store page and in your run cost summary.

Input options

n8n directory URLs

Use the default URL for the full public integrations directory:

[{ "url": "https://n8n.io/integrations/" }]

Search text

Use search to match node names, package names, slugs, descriptions, aliases, and categories.

Examples:

• slack
• google
• ai
• webhook

Category contains

Use category when you want a category-focused export, such as:

• Communication
• Marketing
• Developer Tools
• Productivity

Node type

Choose one of:

• all
• regular
• trigger
• core
• community

Maximum nodes

Use maxItems to cap your dataset size. The prefilled value is intentionally small so your first run stays inexpensive.

Example input

{
  "startUrls": [{ "url": "https://n8n.io/integrations/" }],
  "search": "slack",
  "nodeType": "all",
  "maxItems": 25
}

Example output

{
  "displayName": "Slack",
  "packageName": "n8n-nodes-base.slack",
  "description": "Consume Slack API",
  "slug": "slack",
  "url": "https://n8n.io/integrations/slack/",
  "categories": ["Communication"],
  "categoryUrls": ["https://n8n.io/integrations/categories/communication/"],
  "isCoreNode": true,
  "isTrigger": false,
  "isCommunityNode": false,
  "mostPopular": true,
  "popularity": 0.95,
  "createdAt": "2021-01-01T00:00:00.000Z",
  "logoUrl": "https://.../slack.svg",
  "aliases": ["chat"],
  "scrapedAt": "2026-06-03T00:00:00.000Z"
}

Values vary based on the current public n8n directory payload.

How to run it

1. Open the Actor on Apify.
2. Keep the default n8n integrations URL.
3. Add an optional search or category filter.
4. Choose a node type filter if needed.
5. Set maxItems.
6. Click Start.
7. Download the dataset or consume it via API.

Tips for better results

• Start with maxItems: 25 to validate your filter.
• Use nodeType: community to find third-party package opportunities.
• Use nodeType: trigger when researching event-driven workflow options.
• Leave search empty to export the broad directory.
• Schedule recurring runs if you want to monitor new integrations.
• Combine category and nodeType for focused market maps.

Integrations and workflow ideas

• Send new community nodes to Slack every week.
• Load all nodes into Airtable as an integration catalog.
• Enrich CRM records with whether an app appears in n8n.
• Build a searchable internal n8n capability database.
• Compare n8n integration coverage against Zapier, Make, or your product roadmap.
• Monitor new nodes in AI, marketing, CRM, developer tools, and communication categories.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/n8n-nodes-directory-scraper').call({
  search: 'slack',
  nodeType: 'all',
  maxItems: 25,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/n8n-nodes-directory-scraper').call(run_input={
    'search': 'slack',
    'nodeType': 'all',
    'maxItems': 25,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~n8n-nodes-directory-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"search":"slack","nodeType":"all","maxItems":25}'

MCP usage

You can use this Actor through Apify MCP with Claude Code, Claude Desktop, and any MCP-compatible agent. Use the actor-specific tools URL so the client exposes only this scraper.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/n8n-nodes-directory-scraper

Claude Code setup:

$claude mcp add apify-n8n-nodes "https://mcp.apify.com/?tools=automation-lab/n8n-nodes-directory-scraper"

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-n8n-nodes": {
      "url": "https://mcp.apify.com/?tools=automation-lab/n8n-nodes-directory-scraper"
    }
  }
}

Example prompts:

• "Find all n8n community nodes related to AI and summarize package names."
• "Export trigger nodes from the n8n directory and group them by category."
• "Check whether Slack, HubSpot, and Notion have public n8n integrations."

Scheduling

Schedule the Actor weekly or monthly to keep a current snapshot of the n8n integration ecosystem.

Common monitoring patterns:

• Weekly new community node review
• Monthly product integration coverage report
• Category-specific market intelligence feed
• Partner ecosystem tracking

Data freshness

The Actor reads the public n8n directory at run time. Results reflect what the website exposes during that run.

If n8n changes its page structure, the Actor may need an update. The output includes scrapedAt so you can track when each row was collected.

Limitations

This Actor scrapes the public directory, not private n8n accounts.

It does not log into n8n.

It does not execute workflows.

It does not install or validate community packages.

It only returns data that is publicly visible in the n8n integrations directory payload.

Legality

The Actor collects publicly available directory information. You should use the data responsibly, respect n8n's terms, avoid excessive run frequency, and comply with applicable laws and your internal policies.

Do not use scraped data for spam or abusive automation.

FAQ and troubleshooting

Why did I get fewer items than maxItems?

Your filters may match fewer nodes than requested. Remove search, broaden category, or use nodeType: all.

Why are some fields null?

The Actor only saves fields exposed by the public page payload. Some nodes may not have popularity, icon, alias, or date values.

Can I scrape detail pages too?

This version focuses on the directory payload for speed and reliability. Detail-page scraping can be added later if users need fields that are not in the directory data.

Related scrapers

• https://apify.com/automation-lab/n8n-workflow-scraper
• https://apify.com/automation-lab/zapier-app-directory-scraper
• https://apify.com/automation-lab/make-templates-scraper
• https://apify.com/automation-lab/app-store-scraper

Changelog

0.1

Initial version: public n8n integrations directory extraction with filters and structured dataset output.

Support

If you need additional n8n fields, category coverage, or detail-page enrichment, open an issue on the Apify Actor page and include your run ID.