Skip to main content

​
Overview

Full-text search engine for n8n nodes using SQLite FTS5. Searches across node names, descriptions, and aliases with support for fuzzy matching and typo tolerance. Returns max 20 results ranked by relevance with commonly-used nodes prioritized. Performance: < 20ms even for complex queries

​
Parameters

​
query
string
required
Search keywords. Use quotes for exact phrases like “google sheets”.Examples:
  • "webhook" - Find webhook nodes
  • "database" - Find database nodes
  • "google sheets" - Exact phrase match
​
limit
number
default:20
Maximum number of results to return.
  • Default: 20
  • Maximum: 100
​
mode
string
default:"OR"
Search mode for matching keywords.
​
source
string
default:"all"
Filter by node source type.
​
includeExamples
boolean
default:false
Include top 2 real-world configuration examples from popular templates for each node.Adds approximately 200-400 tokens per node.

​
Response

​
results
array
Array of node objects sorted by relevance score.

​
Examples

{
  "query": "webhook"
}

​
Response Example

{
  "results": [
    {
      "nodeType": "n8n-nodes-base.webhook",
      "displayName": "Webhook",
      "description": "Starts the workflow when a webhook is called",
      "category": "Core Nodes",
      "relevanceScore": 15.8,
      "isCommunity": false
    },
    {
      "nodeType": "n8n-nodes-base.respondToWebhook",
      "displayName": "Respond to Webhook",
      "description": "Returns data for Webhook",
      "category": "Core Nodes",
      "relevanceScore": 12.4,
      "isCommunity": false
    }
  ]
}

​
Use Cases

  • Finding nodes when you know partial names
  • Discovering nodes by functionality (e.g., “email”, “database”, “transform”)
  • Handling user typos in node names (use FUZZY mode)
  • Finding all nodes related to a service (e.g., “google”, “aws”, “microsoft”)
  • Discovering community integrations for specific services
  • Finding verified community nodes for production use

​
Best Practices

Single keywords provide the broadest results. Use multiple words only when you need to narrow down.
// Good for discovery
{"query": "webhook"}

// More specific
{"query": "webhook trigger", "mode": "AND"}
When users might misspell node names, FUZZY mode is essential.
{"query": "slak", "mode": "FUZZY"}  // Finds "Slack"
{"query": "postgrs", "mode": "FUZZY"}  // Finds "Postgres"
After finding the right node, use get_node to get its configuration schema.
// 1. Search
search_nodes({"query": "http"})

// 2. Get details
get_node({"nodeType": "n8n-nodes-base.httpRequest", "detail": "standard"})
Filter by verified community nodes when recommending for production.
{"query": "pdf", "source": "verified"}

​
Common Pitfalls

AND mode searches all fields: AND mode searches across name AND description fields, not just node names. This can return unexpected results.
FUZZY with short queries: FUZZY mode with 1-2 character queries may return unexpected results. Use at least 3 characters.
Exact matches are case-sensitive: When using quotes for exact phrases, matches are case-sensitive.
Community nodes require installation: Community nodes must be installed via n8n npm install <package-name> before use.

get_node

Get node configuration schema

validate_node

Validate node configurations

search_templates

Find workflow templates

Build docs developers (and LLMs) love

Get started for freeTalk to us