For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). This page is also available as [Markdown](https://docs.pandium.com/getting-started/anatomy-of-an-integration/pandium.yaml-spec/schema.md).

The PANDIUM.yaml’s schema properties are a collection of string to object mappings that determine the name and type of each configuration in the connection settings page. The object to which the property name is mapped must contain the `type` prop. Pandium currently supports the following types, many of which can take additional props:

### Boolean

```yaml
bool_input:
  type: boolean
  default: true
```

In this example `bool_input` is the name of the config. When presented to the end user, they will see a checkbox that is checked because the default is set to true. When a run happens this config will be injected into the environment as `PAN_CFG_BOOL_INPUT`.

#### Props

| Prop      | Values                | Note                          |
|-----------|-----------------------|-------------------------------|
| default   | true or false         |                               |

### Integer

```yaml
integer_input:
  type: integer
  default: 0
  min: -1
  max: 10
```

In this example, `integer_input` is the name of the config. When presented to the end user, they will see a number selector that is restricted to integers, with the value 0 being presented as the starting value. The end user will be able to enter an integer between -1 and 10. When a run happens, this config will be injected into the Environment as `PAN_CFG_INTEGER_INPUT`.

#### Props

| Prop     | Values         | Note                     |
|----------|----------------|--------------------------|
| default  | an integer     |                          |
| min      | an integer     | negatives allowed         |
| max      | an integer     |                          |

### Number

```yaml
number_input:
  type: number
  default: 1.3333333
```

In the above example, `number_input` is the name of the config. When presented to the Integration Hub user, they will see a number selector with the value 1.3333 presented as the starting value. When a Run happens this config will be injected into the Environment as `PAN_CFG_NUMBER_INPUT`.

#### Props

| Prop     | Values       | Note         |
|----------|--------------|--------------|
| default  | any number   |              |
| min      | any number   | negatives allowed |
| max      | any number   |              |

### String

```yaml
string_input:
  type: string
```

In the above example, `string_input` is the name of the config. When presented to the Integration Hub user, they will see a text box that is empty being the starting value. When a Run happens this config will be injected into the Environment as `PAN_CFG_STRING_INPUT`.

#### Props

| Prop     | Values                | Note                                                              |
|----------|-----------------------|-------------------------------------------------------------------|
| default  | any valid unicode string |                                                               |
| format   | null