Web Search

Let an AI agent search the web for current information while it works.

What it does

Web Search is a tool for an agent, not a step in the flow. It has no output port: you connect it to the Tools slot of a Tools Agent.

The agent sees a tool named web_search and calls it with a search query. The browser extension opens the chosen Engine in a background tab, reads the first page of results and returns them to the model as a list of title, url and snippet. The model only gets these result snippets, not the full pages.

It reads search results only, so no approval is needed.

When to use it

• The agent needs facts newer than its training: prices, releases, news, opening hours.
• The agent should find a source link to cite in its answer.

To run one fixed search as a step in the flow, use the Web Search page node instead. For encyclopedia facts, Wikipedia Query gives longer summaries.

Inputs and settings

Einstellung	Typ	Was es bewirkt
Engine	Choice	Which search engine to query. Options: duckduckgo, bing, brave. Standard: duckduckgo
Max Results	Number	Maximum number of results to return. Leave empty or 0 to return all first-page results.

A small Max Results, such as 5, keeps the model’s input short and the run cheaper. The model writes the query itself on each call.

Outputs

This node has no output port. It plugs into a slot on another node instead of passing items along.

• Tools slot of Tools Agent

The results go back to the model, not to the next node. The agent’s steps output lists each search it ran, and its response holds the final answer.

Dependencies and credentials

None. This node needs no connection and has no slots for other nodes.

The search runs in the AWFlow browser extension, so the workflow must run from the extension.

Example workflow

1. Get Selected Text reads a product name you highlighted, with Output field name text.
2. Tools Agent with Prompt Find the latest price and release date of {{ $input.text }}. Cite your sources., a Chat OpenAI model in Model, and Web Search connected to Tools with Engine brave and Max Results 5.
3. Display Markdown shows {{ $input.response }}.

Common issues

• The search fails right away. This node runs in the browser extension; install it or run the workflow from the extension.
• The model gets no results. The engine may have shown a captcha or changed its page layout. Switch Engine and try again.
• The answer is vague. Snippets are short. Raise Max Results, or ask the agent in the Prompt to search more than once with different queries.

Related nodes

• Tools Agent: the agent this tool plugs into.
• Web Search: one fixed search as a step in the flow.
• Wikipedia Query: encyclopedia summaries for the agent.
• HTTP Request Tool: let the agent read a specific API.