> 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/integrations/parallel.md). # Parallel Web Research Use Parallel to answer focused questions about a person or company from public web sources. ## Connect An admin opens **Settings → Integrations → Parallel** and enters a Parallel API key. Saving verifies access by reading task runs; it does not start research. Live research is billed to your Parallel account. ## Research in a workflow Add **Web Research** and identify the lead or company. Write a narrow question, define the requested output fields and review the supported processor choice. Example: “Does this company sell security software? Return the answer and the evidence URL.” Use the returned fields in a later condition only after deciding how to handle missing or uncertain answers. ## Research selected records Use [Records → Web Research](/records/research.md) to run a batch with named answer fields. Record research answers are stored under research fields; they do not automatically update the CRM. ## Verify Inspect the answer and evidence, rather than using completion status as proof of factual accuracy. Test a known company and an ambiguous one. Check the key, quota, task error and output mapping if the step fails. A workflow simulation uses sample research; it does not contact Parallel or establish that a source is available. For deterministic routing, define a fallback when research returns no usable answer. --- # 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/integrations/parallel.md?ask=&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.