> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Deep Research node

> Research a question across the open web with a budgeted, multi-pass agent, and file the cited result into a knowledge base.

## Overview

The **Deep Research** node investigates a question across the open web and files a cited report into a Knowledge Base. It is a budgeted, multi-pass agent: it plans the work, sends sub-researchers to search and read pages, grades what they bring back, and keeps going until the budget runs out or it has enough to report.

Unlike a [Custom Agent](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/custom-agent-node.md), you do not write the method. The research prompt is built into the node, so you describe the subject and the node decides how to pursue it.

> [!NOTE]
>
> **The result always lands in a Knowledge Base.** Research is filed as text so retrieval nodes and other agents can reach it later. A rendered document is optional, and off by default.

***

## Adding a Deep Research node

Open your workflow in **Integration Designer**, then pick **Deep Research** from the **AI Agents** group in the left node panel, alongside **Custom Agent** and **Intent Classification Agent**.

***

## Configuring the node

**researchQuestion** `string` *required*

What the node should investigate. Bind workflow data with `${...}` placeholders, and add any standing guidance you want the node to follow.

**Example:**

```
Research ${topic}. Prefer primary sources.
```

There is no **Instructions** field on this node. The research method itself is built in, so this field carries the subject and your guidance, and nothing about how to search.

**researchDepth** `string`

How far the node fans out, chosen from four options.

**Default:** `Standard`

**Quick**, **Standard** and **Deep** apply budgets tuned by the platform, shown under the control as a summary such as `24 passes · 6 tool calls per sub-researcher`:

| Depth | Passes | Tool calls per sub-researcher |
| - | - | - |
| **Quick** | 12 | 4 |
| **Standard** | 24 | 6 |
| **Deep** | 48 | 10 |

**Custom** replaces the summary with two fields you set yourself:

| Field | What it controls |
| - | - |
| **Passes** | How many model calls the whole run may make. More passes let the node dig further, and cost more. |
| **Tool calls** | How many searches and page fetches each sub-researcher may make before it has to report back. |

> [!NOTE]
>
> **The number of sub-researchers is always the node's decision.** It is not a setting, on any depth.

**sources** `object`

Which parts of the open web the node may read. Leave both lists empty to allow anything.

Open **Manage lists** to edit them:

| List | Effect |
| - | - |
| **Allow only** | When set, the node may read **only** these domains. |
| **Deny** | Domains the node must never read, even when no allow list is set. |

> [!WARNING]
>
> **An allow list is a hard restriction. Nothing outside it is read.** An over-strict list yields no sources and fails the node.

Each list holds up to **50** entries and takes either mode:

* **Static** — type hostnames such as `reuters.com`. Anything that is not a hostname is rejected, and a duplicate is refused with `Already in the list`.
* **Dynamic** — bind a single `${...}` expression that resolves to the whole list, such as `${allowedDomains}`. Anything past the first 50 entries is ignored at runtime.

**storeResponse** `object` *required*

Where the report is indexed so retrieval nodes and other agents can reach it. All three fields are required.

| Field | Description | Default |
| - | - | - |
| **Knowledge Base** | The Knowledge Base to write into. **Store** stays locked until you pick one. | — |
| **Write mode** | **Append Content** adds to what is there, **Replace** overwrites it. | `Append Content` |
| **Store** | The store inside that Knowledge Base. | — |
| **Metadata values** | Optional metadata attached to what is written. Shows `No metadata values` when empty. | — |

> [!WARNING]
>
> **Check the store name.** An unrecognised name creates a new store rather than failing, so a typo produces a second store that looks empty instead of an error you can see.

**generateReport** `boolean`

Renders the research as a document in addition to filing it as text, and lets you choose the format and where it lands.

**Default:** `false`

The research is always filed as raw text for the Knowledge Base, so turning this off does not lose the result. Turn it on when someone needs a document to read.

**subResearcherModel** `string`

The model the sub-researchers use, set on the **AI Model** tab.

**Default:** `Same as orchestrator`

A cheaper model here is the usual way to make a wide fan-out affordable, since the sub-researchers do most of the calls.

**responseKey** `string` *required*

The key the node's output lands under in workflow state.

**Default:** `responseKey`

> [!NOTE]
>
> This node has no **Request timeout** setting. The shared timeout does not apply to it, so the control is not shown rather than shown and ignored.

***

## Related resources

> [card] [Custom Agent node](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/custom-agent-node.md)
>
> Agents where you write the instructions and attach the tools

> [card] [Knowledge Base overview](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/knowledge-base-integration/knowledge-base-overview.md)
>
> Where the research is filed, and how to retrieve it


## Related topics

- [FlowX.AI 5.12.0 Release Notes](https://docs.flowx.ai/release-notes/v5.x/v5.12.0-september-2026/v5.12.0-september-2026.md)
- [AI node types](https://docs.flowx.ai/6.x/ai-platform/agent-builder/node-types.md)
- [Deployment guidelines v5.12](https://docs.flowx.ai/release-notes/v5.x/v5.12.0-september-2026/deployment-guidelines-v5.12.md)
- [FlowX.AI 5.9.x to 6.0.0 changelog](https://docs.flowx.ai/release-notes/v6.x/5.9-to-6.0-changelog.md)
- [Evaluations](https://docs.flowx.ai/6.x/ai-platform/evaluations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.