> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/content-management/driver-packs/driver-packs-node.md).
# Driver packs Node
This covers the Driver packs node that automates the import of driver packs available from the 2Pint driver pack API, same as the catalog used in the "Inject cloud drivers" step.
This node can be found inside of the Deployments blade, under DeployR.
To use this feature, simply search for a specific device for which drivers are needed in your environment, click the "Select" toggle, then an import button will magically appear in the upper left section of the frame, that can be pressed to start the process.
This example will show searching for an HP ZBook Studio G10, then importing the desired pack. Using the search key words studio G10, a list of options appears:
Using the sort feature on the OS name assists in finding the desired pack. Note that duplicate do appear, which is causes especially on HPs that have additional meta data, this is being looked into, but for now, select one of the packs needed, then click Import:
A confirmation prompt will appear with overview of how many packs will be imported, in this example, just 1:
Once OK is clicked, a message will slide in from the buttom right.
To monitor the process, logs are generated on the DeployR server in the DeployR content log folder, prefixed with the name "ImportOEMDriverPack-" and suffixed with a random GUID. Opening the log will show the status of downloading, extracting generating the content item and uploading into DeployR:
It will now show in the Content items area:
### Updates to Driver Pack Catalog
The Catalog is refreshed several times a day, there might not be any changes, but there are processes that scan the OEMs several times a day looking for changes, if there are, then the catalog is updated to reflect the addtional driver packs released.
---
# 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://documentation.2pintsoftware.com/deployr/content-management/driver-packs/driver-packs-node.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.
