> 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/csv-findings-templates.md).

# CSV Findings Templates

PlexTrac understands the importance of simplifying the process of importing findings and other data into the platform, whether for a specific report or multiple reports and assets. To facilitate this, PlexTrac offers CSV templates and scripts that help streamline the import process and make it more efficient.

CSV templates serve as pre-defined structures that align with the required format for importing data. These templates specify the fields and corresponding data types expected when importing findings or other information. Users can leverage these templates to ensure that their data is correctly mapped and formatted for import, minimizing errors and ensuring consistency.

Two CSV options are available to import findings into a report. Consult the table below to determine the most suitable solution for your needs.

| Report Findings CSV Import                                    | Python General CSV Import                                                    |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Imports to a single report                                    | Imports to multiple reports                                                  |
| Request is processed on the backend in less than five minutes | Each finding is processed individually and can take up to several hours\*    |
| Must order CSV columns to match template schema exactly       | CSV columns are mapped to findings on a finding and sequence is not relevant |
| Imports to select finding fields only                         | Imports to all finding and asset fields                                      |
| Does not import client and report information                 | Imports client and report information                                        |

\*The script can create parsed findings in PlexTrac by sending API calls to create each finding individually (which results in an extended script runtime) or by generating a PTRAC file. Manually importing the generated PTRAC file takes the same time as the PlexTrac Report Finding CSV Template. 

{% hint style="info" %}
The generated PTRAC only contains the report and finding information. Asset information will not be added.
{% endhint %}

### Report Findings CSV Template 

Please click on the box below to access instructions and a downloadable CSV file that can serve as a template for uploading findings into a report. The CSV file contains fields pre-filled with sample values.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th>used in</th><th>accepted file types</th><th><select multiple><option value="ba7c14c1fa02401289b0893e52d560ba" label="field mappings" color="blue"></option><option value="05e94a2ac08c47daa95dd9eefd1ae410" label="instructions" color="blue"></option></select></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Report Finding Template</strong></td><td>Findings/Reports</td><td>CSV</td><td></td><td><a href="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2FQHq5PL7CcgSirJ5j7dxq%2Fcsv-xxl.png?alt=media&amp;token=361595e0-27bf-40b9-845e-9bf4c9ac8714">csv-xxl.png</a></td><td><a href="/plextrac-documentation/product-documentation/reports/findings/csv-findings-templates/using-report-findings-csv-template.md">Using Report Findings CSV Template</a></td></tr></tbody></table>

### Python General CSV Template

Click on the box below to learn about importing data through the PlexTrac API using a script. The script requires two CSV files: one for importing data and another for field mappings.

This script is designed to help users import data into multiple clients and reports. It works by parsing a CSV file and creating client, report, finding, and asset objects. Once the objects are generated, the script uses the PlexTrac API to import and create them in the user's tenant.&#x20;

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th>used in</th><th>accepted file types</th><th><select multiple><option value="ba7c14c1fa02401289b0893e52d560ba" label="field mappings" color="blue"></option><option value="05e94a2ac08c47daa95dd9eefd1ae410" label="instructions" color="blue"></option></select></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Python General Template</strong></td><td>Findings/Reports</td><td>CSV</td><td></td><td><a href="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2Fk9dGK2dkf8baKsreZi2r%2Fcsv-xxl.png?alt=media&amp;token=488cd859-8c53-470b-8902-399db68f7ff9">csv-xxl.png</a></td><td><a href="https://github.com/PlexTrac-Labs/general-csv-import">https://github.com/PlexTrac-Labs/general-csv-import</a></td></tr></tbody></table>


---

# 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/csv-findings-templates.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 `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.