n8n Templates APInot_yet_determined.com ↗
Access n8n workflow templates via API. Search by keyword or category, get full workflow JSON with nodes and connections, find similar templates, and list by creator.
curl -X GET 'https://api.parse.bot/scraper/95a44f30-07ab-4697-93f1-75aded2038fe/search_templates?rows=3&query=slack' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for n8n workflow templates with optional keyword and category filters. Returns paginated results sorted by creation date (newest first).
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| rows | integer | Number of results per page. |
| query | string | Search keyword to filter templates by name or description. |
| category | string | Filter by category name (e.g. 'Engineering', 'AI', 'Marketing'). |
{
"type": "object",
"fields": {
"workflows": "array of workflow template summaries including id, name, totalViews, user, description, createdAt, and nodes",
"totalWorkflows": "integer total number of matching templates"
},
"sample": {
"data": {
"workflows": [
{
"id": 12345,
"name": "Scrape physician profiles from BrowserAct into Google Sheets and notify Slack",
"user": {
"id": 98533,
"name": "Madame AI Team | Kai",
"username": "madame-ai",
"verified": true
},
"nodes": [],
"price": 0,
"createdAt": "2026-01-01T06:03:29.887Z",
"totalViews": 52,
"description": "Scrape physician profiles from BrowserAct to Google Sheets...",
"purchaseUrl": null
}
],
"totalWorkflows": 1363
},
"status": "success"
}
}About the n8n Templates API
The n8n Templates API exposes 5 endpoints for searching, browsing, and retrieving workflow templates from the n8n template library. Use search_templates to query by keyword and category, or get_template_details to fetch a full workflow JSON including every node, connection, and analytics field for a specific template ID. The API also covers per-user template listings and category-based similarity matching.
Search and Browse Templates
The search_templates endpoint accepts a query string, a category name (such as 'AI', 'Engineering', or 'Marketing'), and pagination controls (page, rows). It returns an array of workflows, each carrying id, name, totalViews, user, description, createdAt, and a nodes array — enough to render a template card and understand what services a workflow touches. The totalWorkflows integer tells you how many results match your query across all pages.
The list_all_templates endpoint iterates through the full catalog sorted newest-first. Pass a limit to cap the result set or omit it to walk the entire catalog. The response returns count (templates in this response), total (full catalog size), and the same workflows array shape as search results. This is useful for building indexes or monitoring when new templates appear.
Full Workflow Details and Similarity
get_template_details takes a numeric template_id and returns the complete template object: id, name, views, totalViews, createdAt, description, the full workflow object with nodes and connections, user info, and categories. The workflow field contains the actual n8n workflow JSON, which you can import directly into an n8n instance.
get_similar_templates accepts a template_id and an optional limit. It resolves the template's category, then returns an array of other templates in that same category along with a category_id field identifying which category drove the match. get_user_templates accepts a username and optional limit, returning all published templates from that creator — useful for browsing work by a specific contributor.
- Index the full n8n template catalog and keep a local mirror synced by polling
list_all_templatesfor newcreatedAtvalues. - Build a template search UI that lets users filter by
categoryand keyword usingsearch_templates. - Auto-import workflow JSON from
get_template_detailsinto a self-hosted n8n instance via the n8n REST API. - Generate 'you might also like' suggestions in a workflow tool by querying
get_similar_templateswith the active template's ID. - Audit which node types are most commonly used by scanning the
nodesarray across all templates returned bylist_all_templates. - Retrieve all templates published by a specific contributor using
get_user_templatesand display them on a profile page. - Track popularity trends over time by storing
totalViewsfrom repeatedsearch_templatesorget_template_detailscalls.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does n8n have an official developer API for its template library?+
What does `get_template_details` return beyond what the search results include?+
get_template_details returns the full workflow object containing the complete nodes and connections arrays — the actual importable workflow JSON. Search and list results return only a summary nodes array used for display. get_template_details also returns per-template category assignments and both views and totalViews analytics fields.How does `get_similar_templates` determine which templates are 'similar'?+
template_id, then queries for other templates in that same category. The category_id field in the response shows which category was used. Templates are not matched by node type, description embedding, or any semantic signal.Does the API expose template version history or changelogs?+
createdAt timestamp and the current workflow JSON per template; there is no revision history or diff data. You can fork this API on Parse and revise it to add an endpoint that tracks version changes if the source exposes that data.Can I filter `search_templates` by node type — for example, to find all templates using the Slack node?+
search_templates endpoint filters by query keyword and category name only; there is no dedicated node-type filter parameter. The nodes array is present in each result, so you can filter client-side after fetching. You can fork this API on Parse and revise it to add server-side node-type filtering as an additional parameter.