> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/reports/findings/importing-findings-from-writeupsdb.md).
# Importing Findings from WriteupsDB
[**WriteupsDB**](/plextrac-documentation/product-documentation/content-library/writeupsdb.md) is a repository for all PlexTrac writeups. It categorizes, associates them with use cases, and facilitates reuse. By structuring and refining findings, writeups can be used in other deliverables, such as a report.
Once a writeup becomes a finding, it is a standalone object that is not impacted if the source writeup or repository is deleted or the same writeup added to another report is edited or deleted.
## Importing from WriteupsDB
Step 1: From the Reports module, click the report row or Readout under the "Actions" column.
Step 2: Click the **Findings** tab.
Step 3: Click **Add Findings**, then select **From WriteupsDB** from the pulldown menu.
Step 4: Search or use the provided filters to find the desired writeups to add, then click the box to select them.
Selected writeups to be added are shown in the column on the far right.
Step 5: Click **Add X Writeups** at the bottom of the page.
A confirmation message will briefly appear, and the writeups are added to the report and listed on the **Findings** tab.
---
# 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.plextrac.com/plextrac-documentation/product-documentation/reports/findings/importing-findings-from-writeupsdb.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.
