> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/project-data/logic/queries.md).

# Queries

Queries are used to perform a search for a specific piece of information, and the result of the query will return that piece of information to be stored in an attribute, or to be used by a rule action (such as **set material** or **set property**)

There are currently four different types of Queries available in the UI:

* [**Node Queries**](https://community.threekit.com/platform-documentation/project-data/logic/queries/node-queries.md) - used to provide a list of nodes matching the search criteria for partial name or node-tags
* [**Metadata Value Queries**](https://community.threekit.com/platform-documentation/project-data/logic/queries/metadata-value-query.md) - used to fetch the value of a given metadata key, on either the parent Item or the items passed through an attribute, or on the current asset
* [**Asset Queries**](https://community.threekit.com/platform-documentation/project-data/logic/queries/asset-query.md) - used to fetch the most recent asset matching the given metadata key-value pairs. They show up as **Metadata Query** in the platform UI.
* [**Datatable Queries**](https://community.threekit.com/platform-documentation/project-data/logic/queries/datatable-query.md) - used to fetch specific data entries from a given Data 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://community.threekit.com/platform-documentation/project-data/logic/queries.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.
