> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/double-braces-functions/comparison-functions.md).

# Comparison functions

Learn about comparison functions in the Digibee Integration Platform and how to use them.

The comparison functions make comparisons of boolean inputs and are available for components that support Double Braces expressions. To know how to provide information to the components using this resource, refer to [Double Braces Functions](/documentation/connectors-and-triggers/double-braces/double-braces-functions.md).

## AND <a href="#and" id="and"></a>

By using Double Braces, you can combine the function with the access to the input JSON element of a component.

In the AND comparison function, both provided values must be "true" to return "true".

### **Syntax**

```
AND( boolean1, boolean2, …, booleanN )
```

In the example below, the "false" value will be returned:

```
{
"and": {{ AND( true, false ) }}
}
```

{% hint style="info" %}
the `null` value is considered as `false`. The return of this function will be `true` or `false`.
{% endhint %}

## NOT <a href="#not" id="not"></a>

By using Double Braces, you can combine the function with the access to the input JSON element of a component.

The NOT comparison function returns the opposite received value.

### **Syntax**

```
NOT( boolean )
```

In the example below the "true" value will be returned:

```
{"not": {{ NOT( true ) }}}
```

{% hint style="info" %}
the `null` value is considered as `false`. The return of this function will be `true` or `false`.
{% endhint %}

## OR <a href="#or" id="or"></a>

By using Double Braces, you can combine the function with the access to the input JSON element of a component.

In the OR comparison function, at least one of the provided values must be "true" to return "true".

### **Syntax**

```
OR(boolean1, boolean2, …, booleanN )
```

On the example below, the "true" value will be returned:

```
{
"or": {{ OR( true, false ) }}
}
```

{% hint style="info" %}
the `null` value is considered as `false`. The return of this function will be `true` or `false`.
{% endhint %}

## XOR <a href="#xor" id="xor"></a>

By using Double Braces, you can combine the function with the access to the input JSON element of a component.

The XOR comparison function will only return "true" if the provided values are opposite. Example: TRUE and FALSE or FALSE and TRUE.

With the support to multiple boolean values, the strategic function resolution is made in pairs, from the left to the right. Example: (TRUE and FALSE and TRUE) = FALSE or (FALSE and TRUE and FALSE and FALSE) = TRUE .

### **Syntax**

```
XOR(boolean1, boolean2, …, booleanN )
```

In the example below, the "true" value will be returned:

```
{
"xor": {{ XOR( true, false, true, true ) }}
}
```

{% hint style="info" %}
the `null` value is considered as `false`. The return of this function will be `true` or `false`.
{% endhint %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/double-braces-functions/comparison-functions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.