> For the complete documentation index, see [llms.txt](https://docs.opendialog.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attributes.md).

# Composite Attributes

Attributes can be *scalar* (store just one value), or they can be *composite.* Composite attributes store multiple attributes within them.

To create a composite attribute, one must create a Webhook Action (and webhook).

The only default composite attributes are the user and utterance attributes in the user context, however these are not actively promoted to the user. It is possible to query these attributes to get data related to the user or utterance (like the utterance text / callback ID).

The advantages of using a composite attribute: it is a way of grouping related data together and gives the possibility of acting on the group as a whole (i.e. rather than single attribute for each element of quote data, we can simply replace the whole quote attribute if the quote is refreshed).

Composite attributes are introduced by engineering (backend work) and may then be used by conversation designers.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attributes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.