# Selector

We determine which element in the DOM the data we want to receive is in with the help of a selector. In this way, when we parse the HTML, muninn knows what data it needs to receive.

{% code title="HTML" %}

```markup
<div class="parent">
  <div class="blue">Blue Text</div>
</div>

```

{% endcode %}

Let's get the content of the element with the `blue` class.

{% code title="Config" %}

```javascript
{
    "blueText": ".blue" 
}
```

{% endcode %}

{% code title="Output" %}

```javascript
{
    "blueText": "Blue Text" 
}
```

{% endcode %}

### Alternative Selector

Now let's specify an alternative selector.

{% code title="Config" %}

```javascript
{
    "greenOrBlueText": ".green, .blue"
}
```

{% endcode %}

Since there is no element with `green` class, it will still get the content of the element with `blue` class.


---

# 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://wopehq.gitbook.io/muninn/config/selector.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.