- Home
- Resources
- Integrations
- Brave Search
Brave Search n8n integrationAutomate Brave Search with n8n.
Need live web results inside a workflow? The Brave Search n8n integration adds 8 search operations on a single resource, from web and news results to places and LLM context. There is no trigger node, so a Schedule Trigger or a Webhook starts the run.
Community node This node is not shipped with n8n: it is a community package (@brave/n8n-nodes-brave-search) you install from Settings › Community nodes on a self-hosted instance. npm
Verified Trustpilot reviews · AI, automation & growth agency
What does the Brave Search n8n integration actually cover?
Once the package is in place, the node exposes one resource and 8 operations. Each one takes a query and returns structured items that the next node in the workflow can read, from a plain web search to news, images, videos, places, spelling checks, query suggestions and LLM context, all through the same credential.
A weekly competitor watch. A Schedule Trigger fires every Monday morning, the node runs default.news with a brand name as the query and Freshness set to pw, and every headline lands as a row in Google Sheets with its link. Nobody opens a browser tab to check what was published.
Enrichment before outreach. A list of company names arrives from a form, default.web looks each one up, and the first result feeds a short note posted to Slack so the sales channel sees the context before the call. The same run can push the summary into a Notion page when the account is worth a longer write-up.
Grounding an AI answer. default.llm_context returns pre-extracted web content sized for a model, which is the piece most RAG pipelines end up writing by hand. The workflow passes that context to the model, then stores the answer and its sources.
Reach for the HTTP Request node when Brave exposes an endpoint this node does not. HTTP Request calls any endpoint of the API and reuses the same credential through predefined authentication, so nothing needs to be re-entered.
Known limits are worth reading before you build. There is no Brave Search trigger, so every workflow starts somewhere else. Result counts differ per operation: 20 for a web search, 50 for news and videos, 200 for images. A few options depend on the plan attached to the key, such as Extra Snippets. And because the package is a community node, a self-hosted n8n is the safe assumption. Our n8n review covers how the platform itself holds up, and the n8n training goes through workflow building step by step.
How do you install and connect Brave Search in n8n?
- 01
Install the community package
Open Settings, then Community nodes, and install
@brave/n8n-nodes-brave-searchin version1.1.8. This step happens on a self-hosted instance, whether n8n runs through Docker or npm. On n8n Cloud, the hosted offer run by n8n, only verified community nodes can be installed, so check that status first. n8n charges nothing for the node itself. - 02
Create the Brave Search credential
Go to the Credentials menu and add a Brave Search credential. A credential is created once and reused across every workflow, so this is a one-time step even if ten workflows end up searching. The values come from the Brave Search API dashboard documentation. Once saved, the credential appears in the node's dropdown and you pick it there.
- 03
Run a first search
Add the Brave Search node to a canvas, select the Search the Web operation, and type a term in Query. Required fields block the node when left empty, so Query has to hold something. Execute the node on its own, read the items it returns, and only then wire the rest of the workflow to the fields you actually need.
What can the Brave Search node do?
The Brave Search node exposes 8 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Operations index
Search the Web
webWhat you see in n8n
Notes & use cases
Runs a standard web search on the Brave index and returns the result list for the query, ready to loop over in the next node.
Key parameters
- Query: required, the search term, capped at 400 characters and 50 words, often
{{ $json.query }}when it comes from a previous node. - Count: how many results come back, between 1 and 20. Combine it with Offset to walk through further pages.
- Result Filter: restricts the response to the types you want, such as
news,videosordiscussions. Left empty, every available type comes back.
Search for News
newsWhat you see in n8n
Notes & use cases
Same query, narrower index: this operation returns news coverage instead of the whole web, with a much higher result ceiling.
Key parameters
- Query: required, the term being monitored, with the same ceiling of 400 characters and 50 words.
- Count: the number of news results in the response, up to 50. Fewer may come back than requested.
- Freshness: filters by when results were discovered, from
pdfor the past 24 hours topyfor the past year.
Search for Images
imagesWhat you see in n8n
Notes & use cases
Returns image results for a term, with the largest result ceiling of any operation on this node.
Key parameters
- Count: the number of image results, up to 200 in a single call, though the response can be shorter.
- Safe Search: only two levels here,
offandstrict, unlike the three offered by the web search. - Language: the search language preference, which changes which sources the images are pulled from.
Search for Videos
videosWhat you see in n8n
Notes & use cases
Video results for a query, with the metadata that lets a workflow decide which ones deserve a human look.
Key parameters
- Count: the number of video results, up to 50, paired with Offset when one page is not enough.
- Freshness: the same discovery window as the news search, useful to keep only clips from the past 7 days with
pw. - User Interface Language: sets the response language, for instance
en-GBrather thanen-US.
Search for Places
place_searchWhat you see in n8n
Notes & use cases
Points of interest in an area. Nothing is strictly required here: leave Query empty and the API returns general points of interest for the area you name.
Key parameters
- Location: a plain-text place. For US cities prefer city, state and country, as in
san francisco ca united states, otherwise city and country. - Latitude and Longitude: decimal degrees, used together as an alternative to Location.
- Radius (meters): biases results toward the coordinates. It is not a strict boundary, and without it the search is global.
Check Spelling of a Query
spellcheckWhat you see in n8n
Notes & use cases
Takes a term and checks its spelling, which is the cheapest way to stop a typo from ruining a downstream search.
Key parameters
- Query: required, the term to check, with the usual limit of 400 characters and 50 words.
- Country: an associated country code used as a hint, defaulting to US.
- Language: an associated language code of two or more characters, defaulting to English.
Get Suggestions for a Query
suggestWhat you see in n8n
Notes & use cases
Expands a seed term into the queries people actually type around it, returned as a short list.
Key parameters
- Query: required, the seed term, with a maximum length of 400 characters and a word limit of 50.
- Count: the number of suggestions, minimum 1, maximum 20, default 5.
- Rich Results: enhances suggestions with richer data, and requires a paid Suggest subscription.
Get LLM Context
llm_contextWhat you see in n8n
Notes & use cases
Returns pre-extracted web content shaped for AI agents, LLM grounding and RAG pipelines, so the workflow skips the fetch-and-clean step entirely.
Key parameters
- Maximum Number of Tokens: the approximate size of the context, default 8192 and maximum 32768.
- Maximum Number of Snippets: how many chunks of text land in the context, default 50 and maximum 256.
- Context Threshold Mode: how strict the inclusion bar is, from
disabledtostrict.
Need help automating Brave Search with n8n?
A person reads every message.