Check condition

Plan availability #

Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.

When to use this node #

Conditional branching based on a yes/no logical check

Add Check condition to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

Build your first rule #

Use Check condition after a step that supplies the value you want to inspect. For example, ask for a customer's message, receive the text, then check whether it contains a particular phrase.

1. Add Check condition to the branch after the source step.
2. In Condition, use Add rule and select the source variable.
3. Choose As Text or As Number for that rule.
4. Select an operator, such as contains or is greater than.
5. Choose Value to enter a comparison value, or Variable to compare with another available variable.
6. Connect Yes for a matching condition and No for a non-matching condition.

Use the variable picker rather than typing a guessed reference. The source must have a value on the branch that reaches this node. Properties can provide reusable comparison values, such as a minimum order amount.

Choose text or number comparison #

Use text for an identifier such as 0012 when its exact spelling matters. Use number comparison for quantities: 10 is greater than 2, and numeric 10 equals 10.0.

Text rules and Ignore case #

Turn on Ignore case when differences such as Support, support, and SUPPORT should match. Leave it off when capitalization must be significant.

equals checks the whole value. contains checks for a substring anywhere in the value. begins with and ends with check its edges. For example, I need support contains support, but does not equal support.

Text comparisons do not automatically remove spaces. yes differs from the same word followed by a trailing space. is empty checks for an empty string; a value containing only spaces is not empty. Normalize input with an appropriate text-processing step if your process should treat those values the same.

is empty and is not empty do not need a right-hand comparison value. Give other operators a meaningful value: an empty search term is not a useful keyword rule.

Numeric rules and missing input #

As Number parses both sides as numbers, including a value selected from another variable. Nonnumeric input such as ten or USD 20 can fail execution; it does not simply take No. Supply a plain numeric value such as 20 or 20.5.

Blank or whitespace-only operands are treated as zero in the current comparison behavior. If missing input must not count as zero, check it separately before the numeric rule. For example, first check As Text → is not empty, then validate or normalize the supplied number before comparing its amount.

Combine rules with AND and OR #

AND means every rule in that group must match. OR means at least one must match. Use Add group to place an AND group inside an OR group, or the reverse. Each group keeps its own combination rule.

For example, offer a priority path when a request has enough detail and either a high amount or a priority category:

AND
├─ Customer email is not empty
└─ OR
   ├─ Amount ≥ 100
   └─ Category = priority

Yes → Priority path
No  → Standard path

This is a visual explanation, not importable workflow JSON. Build the groups and rules in Condition. The email rule must match regardless of which rule matches inside the OR group. Flattening all three rules into one OR group would mean something different.

For Amount ≥ 100, choose As Number → is greater than or equal to and enter 100. For Category = priority, choose As Text → equals, enter priority, and turn on Ignore case. The short diagram labels stand for these editor settings.

Keep groups intentional and populated. An empty AND group matches and an empty OR group does not; do not rely on the initial empty group as your finished condition.

Compare a variable with another variable #

Choose Variable on the right side when the threshold comes from a Property or an earlier step. For example:

Select the actual variables in the editor. Property labels in this table are examples; they are not literal text you should type in place of a variable reference.

Design both outcomes #

Yes means the complete condition matched. No means it evaluated without matching. This node does not create a new result variable; its result is the selected branch. Invalid numeric data or other execution failures are different from No and should be addressed in input validation and run diagnostics.

For missing data, let the relevant path ask for the value again or provide a useful fallback. A condition is also useful after an API lookup to check an extracted value before sending a response that assumes the lookup succeeded.

If you pause this node, new runs skip its check and continue on its first branch, Yes. Review that branch before using pause to troubleshoot.

Test a boundary, not just a happy path #

For a numeric threshold, try a value below it, exactly equal to it, and above it. Also try missing input and a nonnumeric value. For text, try capitalization changes, spaces, a partial match, and no match.

For nested groups, test a case where only one OR rule matches and a case where an AND requirement fails. Check the actual branch in Workflow Activity. See branches and fallbacks for connecting the rest of the workflow.

Configure the fields #

Use the result #

This definition has no fixed public output variables. It may perform an action, or expose dynamic outputs after you configure response extraction, a table, or another resource. Check the variable picker after configuring the node.

Connect the next step #

This definition exposes these paths:

• Yes — branch 1.
• No — branch 2.

Connect each relevant outcome, especially any error or timeout path. Outputs can differ by outcome; check that a result exists before using it.

Test it in a workflow #

1. Configure this node with a small, recognizable test input or a test resource.
2. Check the variables from preceding steps and the connection selected in the inspector.
3. Save the workflow. For event-driven flows, generate the actual event; use Run only for a Manual workflow.
4. Open Workflow Activity and check the outcome before enabling wider use.

If something goes wrong #

• Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
• Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
• Follow the troubleshooting guide for a symptom-by-symptom checklist.

Related guides #

• Work with variables
• Understand branches and error handling
• Browse all nodes
• A/B Testing
• Analyze Image
• Ask Multiple Choice Question
• ChatGPT Task
• External API integration

Catalog coverage #

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.