> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/records/research.md).

# Research selected records

Use **Web Research** to ask the same question about selected people or companies and retain the answers in Distro.

## Set up research

Connect [Parallel](/integrations/parallel.md) with your workspace's key. Research requests are billed to that provider account.

1. Select up to **50** records in Records.
2. Choose **Run an action → Web Research**.
3. Enter a **Research prompt** of up to **2,000 characters**.
4. Enter **1–10 Answer fields**, using lowercase names with letters, numbers and underscores.
5. Select **Run**.

For example:

```
Prompt: Find this company's funding stage and main competitor.
Answer fields: funding_stage main_competitor
```

Distro starts one task for each selected record. Answers are saved under keys such as `research:funding_stage`.

## Review the answers

Check Recent runs, then inspect sample records. Treat research as information to review before an important routing or CRM decision. Missing information is different from a confirmed negative answer.

Research changes Distro records. It does not automatically update the CRM or start a sequence. Map reviewed answers into a workflow or an explicit record writeback when you want to use them elsewhere.

For structured answers inside a workflow, use [AI and web research](/data-and-integrations/ai.md). The workflow research step has its own output schema and settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/records/research.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.