> 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-via-an-integration.md).
# Importing Findings via an Integration
Findings may be imported into PlexTrac via a licensed API integration and configured by an admin.
## Importing from an Integration
Step 1: Within the **Reports** module, click a report from the list to bring up the **Readout** tab.
Step 2: Click the **Findings** tab.
Step 3: Click **Add Findings** and select **Integrations** from the pulldown menu.
Step 4: Select the desired integration from the pulldown menu (the values shown in the pulldown menu are entered by the admin when the integration is set up).
{% hint style="info" %}
If an integration is not licensed or not configured by an admin, the option will not appear in the pulldown menu.
{% endhint %}
Step 5: Click **Continue with X** at the bottom of the page.
Step 6: The **Select Findings** tab appears with a list of filters and values that are tool-specific to an integration. Use the filters and facets to select the query parameters to determine which findings appear on the page.
Step 7: Click **Search** to retrieve the findings query results.
Step 8: Select the findings from the query results to import by clicking the box at the top left of the table header row or by selecting findings individually by clicking the box next to the finding.
At least one finding must be selected to continue.
Step 9: Click **Continue with X issues**.
Step 10: Insert desired tags associated with each finding and asset when imported (optional). Click **Import X Findings**.
Notifications will appear confirming that the import was successful.
{% hint style="info" %}
More information on specific tools, such as field mappings, can be found on the [admin integrations page.](/plextrac-documentation/product-documentation-1/account-management/account-admin/integrations-and-webhooks/integrations-api.md)
{% endhint %}
---
# 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-via-an-integration.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.
