> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/review-workflow/literature-search/add-search.md). # Add Search Add records to your nest through an automatic search or imported search files. Add a search to bring records into your nest before **Screening**. Choose the method that matches where you built your search strategy.

Decision tree for choosing between an automatic search and imported search files based on your review. — Choose the search method that matches your review.

### Choose How To Add Your Search


Add an Automatic Search	Run a saved query in a supported database.	Automatic Search
Import Search Files	Add results from searches you ran elsewhere.	Import Search Files

### Build Your Search With AI


Explore AI Tools in Search	Generate or explore queries before finalizing your search strategy.	AI Tools in Search

### Add Sources From Outside Databases


Other Sources	Add records from gray literature, PDFs, and other sources.	Other Sources

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nested-knowledge.com/review-workflow/literature-search/add-search.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 `automate deployments from our CI pipeline` 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.