Attributes

For an introduction to attributes, read more here or enroll in the OD Academy.

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.