> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/inventory/collect_data.md).
# Collect Data
{% hint style="info" %}
**Information**
The GLPI Inventory plugin is available in the menu **`Administration`** > **`GLPI Inventory`**\
If it is not installed, please go to the **marketplace**, and install the GLPI Inventory plugin
\
{% endhint %}
## Declaration of a data to be queried
{% hint style="info" %}
**Information**
In the following example, we are going to check that the user has the thunderbird icon on his desktop (which in this case is a portable application).
{% endhint %}
Go to the **`administration`** > **`GLPI Inventory`** > **`tasks`** > **`computer information`**
Then create a new item **`ajouter`** :
The next window will allow you to enter the following information:
* A name
* A comment
* A type
* Registry
* [WMI](broken://spaces/QFOh36etagWOcP9q4ECb/pages/uyV7vc1BgpEAKyDInQFN#comment-configurer-la-collecte-wmi)
* Search for a file
* Active or not
* Visible in a sub-entity or not
Once you've clicked on **`Add`**, a **`Collect configuration`** tab appears in the left-hand menu, allowing you to configure data collection for one of the following three options, depending on the chosen type:
* WMI Windows
* File search
* Windows registry
## Creating the task
Go to **`administration`** > **`GLPI Inventory`** > **`tasks`** > **`task management`**
Then create a new task with **`ajouter`** :
Create the task :
Then in **`Job configuration`**, add a job:
And configure the collect job in this task:
Once the job has been activated, prepared and taken over by the agent, you can see the result of the job execution here:
In the computer file, a new tab **`Collection information`** appears with the value found for the file:
---
# 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://help.glpi-project.org/inventory/collect_data.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.
