Yes/No

In Monkedo, the Yes/No data type is used to represent binary states such as true/false, enabled/disabled, or yes/no. It’s commonly applied in cases where you need a simple decision or status. For example:

A product may have a field to indicate Yes if it’s in stock and No if it’s not.
A task may have a field to indicate Yes for completion and No if it’s still pending.

Below is an example output from a component that provides a Yes/No value:

Setting Yes/No Inputs

Yes/No values can be set as inputs in components to enable or disable functionality. You can assign these inputs in two ways:

Manually in the info panel, where you’ll see Yes/No buttons next to each other. Simply click to select Yes or No; click again to deselect.
Dynamically, by connecting the output of another component to the Yes/No input of your target component.

Yes/No input from Google Sheets - Get Values component to indicate whether the first row of the table is header row (contains column names) or not (contains data).

Logic Components

Monkedo provides Logic Components to create and manage Yes/No values by evaluating multiple conditions. These components enable basic logical operations, as well as conversions to Yes/No values from other data types.

Convert to Yes/No

The Convert to Yes/No component transforms non-Yes/No values into a Yes/No result:

It outputs Yes if the value is not empty and not zero.
It outputs No if the value is empty or zero.

Example 1: Suppose a product has a stock amount field. You want to get a value indicating if it’s in stock or not. By connecting the stock amount to this component, this component will output No if the amount is 0, and Yes if the amount is 1 or more.

Example 2: Suppose in a task management application, tasks have an optional completion date. Completion date is set when task is completed and not set if it is not completed yet. If you want to get a value indicating whether the task is completed or not, you can connect the completion date value to the input of Convert to Yes/No component. The output will be Yes if completion date is set and No if completion date is empty.

AND Component

The AND component takes two Yes/No inputs:

It outputs Yes if both inputs are Yes.
Otherwise, it outputs No.

Example: Suppose you’re managing tasks where both the “task approval” and “document submitted” statuses must be Yes for the task to be considered complete. By connecting both conditions to the AND component, it will output Yes if both are met and No if either is missing.

OR Component

The OR component works similarly but is more lenient:

It outputs Yes if at least one input is Yes.
It outputs No only if both inputs are No.

This component is useful when you need a condition to be met if either of two statuses is true.

NOT Component

The NOT component inverts a Yes/No value:

It outputs No if the input is Yes.
It outputs Yes if the input is No.

For example, it’s helpful to check if a task is not complete by connecting its completion status to this component.

XOR Component

The XOR (Exclusive OR) component outputs Yes only if one of the inputs is Yes and the other is No:

If both inputs are Yes or both are No, it outputs No.

This is useful in scenarios where only one of two conditions should be true for a certain status to be met.

By using these Logic Components, you can manage Yes/No values to make complex evaluations easy and consistent in your Monkedo automations. Explore the component list for more ways to work with Yes/No data in your workflows.