Query

The Query data type is used to define logical rules. It is different from text, number, date, or table types because it represents a condition, not a value. A Query tells Monkedo how to compare two pieces of data and decide whether the result is true or false.

The Query data type appears only in some components, but its most important usage is inside the Condition component. When building automations, the Condition component allows your workflow to make decisions. Queries are used to evaluate these decisions. If the query is true, the automation follows the “True” path; if false, it follows the “False” path. This makes Query essential for branching logic, filtering, and controlling the flow of an automation.

A Query rule is made of three parts:

1. Input – the value you want to check. (Example: task status, price, name, date, email subject)

2. Comparison – what type of check you want to perform. (equal, contains, greater than, empty, etc.)

3. Value – the thing you compare the input to. (Example: “Completed”, 100, “urgent”, “2024-01-01”)

Comparison Options

• equal — true if the input is exactly the same as the value.

• not equal — true if the input and value are different.

• greater than — true if the input is greater than the value.

• greater than or equal — true if the input is greater than or equal to the value.

• less than — true if the input is smaller than the value.

• less than or equal — true if the input is smaller than or equal to the value.

• contains — true if the input includes the value anywhere inside it.

• not contains — true if the input does not include the value.

• in — true if the input matches one item in a list of values.

• not in — true if the input does not match any item in a list.

• empty — true if the input exists but has no value.

• no empty — true if the input has any value.

• set — true if the field exists.

• not set — true if the field does not exist at all.

• starts with — true if the input begins with the value.

• ends with — true if the input ends with the value.

• matches pattern (regex) — true if the input fits a regular expression.

• is alpha — true if the input contains only letters.

• is numeric — true if the input contains only numbers.

• is date — true if the input is a valid date.

Common Confusions for Comparisons

empty vs. not set:

• “empty” means the field exists but is blank;

• “not set” means the field does not exist.

contains vs. in:

• “contains” searches inside text;

• “in” checks whether the input is one of several listed values.

starts with vs. contains:

Beginning of text vs. anywhere in text.

AND / OR Logic in Query

You can combine multiple comparisons to build more advanced rules.

AND Rule

All conditions must be true. Example: Price > 100 AND Category = “Electronics”. Both must be true for the query to pass.

OR Rule

Only one condition needs to be true. Example: Status = “Active” OR Status = “Pending”. If either condition is true, the query passes.