n8n Workflow Templates Scraper avatar

n8n Workflow Templates Scraper

Pricing

from $0.02 / 1,000 workflow template saveds

Go to Apify Store
n8n Workflow Templates Scraper

n8n Workflow Templates Scraper

Search and export public n8n workflow templates with categories, integrations, author details, popularity metrics, and optional workflow JSON.

Pricing

from $0.02 / 1,000 workflow template saveds

Rating

0.0

(0)

Developer

Fetch Cat

Fetch Cat

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

2

Monthly active users

22 days ago

Last modified

Features

Limited permissions

Share

Collect public n8n workflow template metadata by keyword, with optional integration or category filters. Export template links, descriptions, visible views and pricing, connected nodes and available public author information. Optional workflow JSON is included only when exposed: collecting a template does not verify, configure or execute it.

Quick start

Search a familiar integration with a small explicit row cap, then open the dataset to inspect template links and source metadata before considering an import. The existing example combines two searches under one cap:

{
"searchQueries": ["slack", "google sheets"],
"maxItems": 25,
"integrations": ["Slack"],
"sort": "popular",
"includeWorkflowJson": false,
"includeAuthorDetails": true
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

What you get

One saved template row with its identity, source link, available description, view count, dates, price and purchase reference. Connected node and integration labels, plus a count of returned node summaries, support your own research. Optional public author fields and exposed workflow definitions can accompany the record, without establishing that a template is correct, current or ready to run.

Who is it for?

  • Automation consultants reviewing public examples before scoping client work.
  • Revenue and marketing operations teams shortlisting templates for known apps and use cases.
  • Agency and AI developers inspecting reusable patterns before configuring their own workflows.
  • Product and ecosystem researchers comparing visible template and creator metadata.

How you can use the data

  • Shortlist Slack and Google Sheets patterns. Use the existing two-query example and Slack integration filter with a small shared cap. Keep template links, integration labels and descriptions before judging suitability yourself.
  • Review optional workflow structure. Enable workflow JSON only when you need the exposed definition for inspection. Review nodes, credentials and configuration separately before any import or execution in your own n8n workspace: this Actor performs neither step.
  • Compare a bounded popularity sample. Request popular ordering for a small Slack search and retain totalViews, createdAt and template identity. Sorting affects the collected sample rather than proving the globally most popular workflows or that they work correctly.
  • Build your own creator and template research library. Keep public author links and optional profiles beside sourceQuery and collection time. Distinguish template price and purchase links from this Actor's usage fees, and compare repeat exports in your own destination rather than implying built-in monitoring.

Input settings

FieldTypeDescription
searchQueriesarray of stringsKeywords to search, such as slack, ai agent, crm, or google sheets.
maxItemsintegerMaximum number of templates to save across all searches.
categoriesarray of stringsOptional category name filters, such as Marketing, Sales, or Lead Generation.
integrationsarray of stringsOptional node/integration filters, such as Slack, Gmail, OpenAI, or Google Sheets.
sortstringrelevance, popular, or newest.
includeWorkflowJsonbooleanInclude available public workflow definitions for inspection. Adds one request per inspected candidate, including candidates later filtered out.
includeAuthorDetailsbooleanInclude public author username, avatar, bio, verified flag, and links.
proxyConfigurationobjectOptional proxy settings. Most runs do not need a proxy.

Supply at least one nonempty search query and set an explicit saved-template cap. The input schema defaults to ten rows and the form prefills five, while omitted runtime input falls back to twenty-five. Query order controls which candidates reach the shared cap. Repeated template IDs are considered once across queries.

Category and integration filters use case-insensitive partial matches, with any requested value matching within each filter group. When both groups are supplied, a row must match both groups. Popular and newest order the selected capped sample, rather than searching every template to guarantee the global most-viewed or newest results. Author information is returned metadata rather than an author-search control.

Output data

  • templateId, name, url, templateDescription
  • totalViews, price, purchaseUrl
  • createdAt, updatedAt
  • categories, integrations, nodes, nodeCount
  • authorName, authorUrl, optional authorDetails
  • optional workflowJson
  • sourceQuery, scrapedAt

Example output

This is the existing illustrative shape rather than a new extraction or proof that a template is working.

{
"templateId": 12345,
"name": "Scrape physician profiles from BrowserAct into Google Sheets and notify Slack",
"url": "https://n8n.io/workflows/12345",
"templateDescription": "Scrape physician profiles from BrowserAct to Google Sheets...",
"totalViews": 3522,
"price": 0,
"purchaseUrl": null,
"createdAt": "2026-01-01T06:03:29.887Z",
"updatedAt": null,
"categories": ["Lead Generation"],
"integrations": ["Code", "Google Sheets", "Slack"],
"authorName": "Madame AI Team | Kai",
"authorUrl": "https://n8n.io/creators/madame-ai",
"sourceQuery": "slack",
"scrapedAt": "2026-07-09T18:00:00.000Z"
}

The run's Search outcome and limits output links to RUN_SUMMARY. It reports saved and charged counts, per-query outcomes, unavailable optional fields and whether an inspected-result or user charge limit ended collection. A failed run can still contain useful saved rows. nodeCount counts returned node summaries, not verified executable steps.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The configured start event is charged after input and connection validation, before searching. A valid run can incur it even when no templates match. The remaining item-event budget also limits collection.

The item event is charged for saved templates after each result batch is made accessible. Saving and charging are separate operations. A storage or billing failure fails the run rather than claiming complete delivery, and previously saved rows remain accessible. Optional workflow definitions and public author fields do not create separate result events.

Set a small explicit template cap and enable workflow JSON only when useful. See the live Pricing tab for current rates and tier details. A collected template's own price or purchase link describes that template, not the Actor's charge.

Tips for best results

  • Use a specific familiar query. Existing examples include Slack, Google Sheets, lead generation, invoice and AI agent patterns.
  • Select integration and category filters deliberately. Their partial-match rules do not prove the workflow meets a business requirement.
  • Keep the saved-template cap explicit. Form, schema and runtime omission values differ.
  • Request workflow JSON only for inspection. Its retrieval adds work even for candidates later excluded by filters and does not execute or validate the workflow.
  • Review optional fields and links before reusing them. Views and creator metadata are source observations rather than performance guarantees.

Limits and caveats

  • Public template research only. Private n8n workflows and workspace credentials are outside scope. Review permissions and configuration yourself before importing a workflow. Public author metadata is not an author-search control or permission for unsolicited bulk outreach.
  • A bounded sample, not an exhaustive ranking. Filters can reduce output, and sorting applies only to collected templates. Duplicate IDs are considered once. Search queries, time, inspected pages and result sizes are bounded. See input help for the limits. A work-limit interruption retains available rows but fails incomplete extraction.
  • Optional data can be unavailable. Source fields can be null or omitted. A missing definition does not prove a template is private or deleted. Unexpected detail or requested-definition failures preserve available metadata but fail the run, with diagnostics, instead of claiming the missing data was successfully extracted.
  • Check the outcome as well as the rows. Valid searches with no matching records succeed empty with truthful summary reasons. Blocking, malformed responses and incomplete required extraction fail. Available buffered rows are saved on a later extraction failure. Interrupted searches do not automatically resume or repeat charges. Inspect the run status and summary before using a partial dataset.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~n8n-workflow-templates-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searchQueries":["slack"],"maxItems":50,"sort":"popular"}'

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/n8n-workflow-templates-scraper').call({
searchQueries: ['slack'],
maxItems: 50,
sort: 'popular'
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/n8n-workflow-templates-scraper').call(run_input={
'searchQueries': ['slack'],
'maxItems': 50,
'sort': 'popular',
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with n8n Workflow Templates Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's n8n Workflow Templates Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=fetch_cat/n8n-workflow-templates-scraper"
}
}
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use n8n Workflow Templates Scraper by Fetch Cat, or give it the identifier fetch_cat/n8n-workflow-templates-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

  • “Use Fetch Cat’s n8n Workflow Templates Scraper to collect up to 5 Slack templates with popular ordering, workflow JSON off and public author details on. Keep template URLs and visible views without calling the capped sample globally best or verified working.”
  • “Collect up to 5 n8n templates for google sheets with the Google Sheets integration filter, relevance ordering and workflow JSON off. Keep categories, authors and source links for my own automation shortlist.”
  • “Retrieve up to 5 n8n templates for ai agent with relevance ordering, public author details and exposed workflow JSON enabled. Keep the source links and definitions for inspection without importing, executing or validating them.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export the actual workflow JSON?

Yes. Set includeWorkflowJson to true to include the workflow definition when available.

Can I filter to only Slack or Google Sheets templates?

Yes. Use integrations, for example ["Slack"] or ["Google Sheets"].

Does this actor need a proxy?

Usually no. The public n8n template data is accessible with standard HTTP requests.

Can I scrape private n8n workflows?

No. This actor is for public n8n workflow templates only.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥