# Get Material Property

## Overview

![The Get Material Property Node with Two Example Outputs.](/files/aHfwhj3vVBclM8ynshkH)

The **Get Material Property Node** returns a property, or properties, of a **Material**. These properties are given their defining names in the **Attributes**. The names can be found by hovering over an **Attribute** of any of the **Shading Models** found in the [**Material Editor**](/incari-studio/modules/material-editor.md), copying it, and pasting it here. The **Node** pictured above shows two possible outputs.

Some examples of these property names are:

| Attribute       | Property Name          |
| --------------- | ---------------------- |
| Albedo          | base\_coat\_albedo     |
| Environment Map | environment\_map       |
| Use Alpha       | use\_alpha             |
| Blending        | diffuse\_map\_blending |

[**Scope**](/incari-studio/toolbox/overview.md#scopes): **Scene**, **Function**, **Prefab**

## Attributes

![Get Material Property Node Attributes with Two Example Outputs.](/files/qN7qZDEU7aLhVS7yUqfb)

| Attribute   | Type         | Description                                                                                                                                                                                                                                                                                |
| ----------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `Property`  | **String**   | Each `Property Element` is split into two parts, with `Property` being the first. This is the defining name of the **Material** property that should be returned. There is an established naming convention which can be found by hovering over the **Attributes** of a **Shading Model**. |
| `Data Type` | **Dropdown** | Each `Property Element` is split into two parts, with `Data Type` being the second. The data type of the property.                                                                                                                                                                         |

## Inputs

| Input             | Type           | Description                                                                 |
| ----------------- | -------------- | --------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**      | A standard **Input Pulse**, to trigger the execution of the **Node**.       |
| `Material ID`     | **MaterialID** | The ID of the **Material** whose property, or properties, will be returned. |

## Outputs

| Output             | Type                        | Description                                                                                                                            |
| ------------------ | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse**                   | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |
| `PROPERTY`         | Determined by **Attribute** | A new output will show when one is added in the **Attributes**. Its data type and name will match that set in the the input element.   |

## See Also

* [**Set Material Property**](/incari-studio/toolbox/incari/material/setmaterialproperty.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.incari.com/incari-studio/toolbox/incari/material/getmaterialproperty.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.