---
url: https://gudhub.com/docs/understanding-gudhub/gh-elements-structure/gh-elements-overview/
title: "GH-Elements Overview\n                #"
description: "gh elements are flexible UI elements with lots of options for useful and comfortable configuration. There are more than 100 different elements in GudHub. Each o"
lang: uk
updated: 2026-09-08T15:32:24.485Z
---

# GH-Elements Overview [#](https://gudhub.com/docs/understanding-gudhub/gh-elements-structure/gh-elements-overview/#gh-elements-overview)

**gh-elements** are flexible UI elements with lots of options for useful and comfortable configuration. There are more than 100 different elements in GudHub. Each of them carries out its unique functions. This provides the ability to create multifunctional applications.

The most interesting feature of gh-elements is that they does not tied to only GudHub. That means, you are free to add all elements to other sites and use them there.

Despite such distinctions between gh-elements they can be divided into three types:

-   Inputs
-   Outputs
-   Actions

**Inputs** aim to receive data from the user for storage and use in _outputs_ and _actions_.

**Outputs** display the interpreted data in items.

**Actions** do not work with data at all. So, they cannot be filtered out. They perform some action to get certain result.

GH-elements can be placed anywhere within the views or even other elements. The simplest example is table which contains element and their outputs.

## Development [#](https://gudhub.com/docs/understanding-gudhub/gh-elements-structure/gh-elements-overview/#development)

Every gh-element is stored in GudHub as an object in [field\_list](https://gudhub.com/docs/understanding-gudhub/application/field-list/) of the application. In turn, these objects contains element location, name, data model and interpretations.

Copy

```json
{
    "app_id": 24290,
    "data_model": {},
    "data_type": "text",
    "field_id": 625327,
    "field_id": 625327,
    "field_name": "Text",
    "field_priority": 0,
    "name_space": "text"
}
```

| Name | Type | Description |
| :-- | :-- | :-- |
| app\_id | `number` | _ID of application where the gh-element is located_ |
| data\_model | `object` | _contains standard data properties; [details...](#data-model)_ |
| data\_type | `string` | _contains the type of data_ |
| field\_id | `number` | _ID of the field where the data type is located_ |
| field\_id | `number` | _ID of the field where the data type is located_ |
| field\_name | `string` | _the name field with this data type_ |
| field\_priority | `number` | _shows field priority for filtering_ |
| name\_space | `string` | _unique field ID in text format within current application_ |

### Data Model [#](https://gudhub.com/docs/understanding-gudhub/gh-elements-structure/gh-elements-overview/#data-model)

Each gh-element has its own unique data model with different varieties of properties. The only one that is the same for everyone is an array of interpretations, about that you can read in [Interpretation chapter](https://gudhub.com/docs/core-api/interpretation/).