Workflow conditions allow you to skip certain steps in a workflow or terminate the workflow if conditions are met.

Conditions can be found under the Advanced section at the bottom of the workflow command.

Conditional logic requires 3 inputs

Condition Value: This is the field in the form that you would like to base your condition off of.
Operator: Indicates the field input for the action to occur.
Action: Indicates what the outcome of the trigger should be. Additionally, the Condition Value can also be a formula. For example, you can use a formula like =IF([trigger.Job #] = "", "True", "False") to dynamically evaluate conditions based on form data.

Operator Options

is True: Select if value is true; e.g. when a checkbox is checked in your form
is False: Select if value is false: e.g when an output of a previous step — like the rowFound output of a Select DataSet Row step — is false.
is Null: Select if input's value is null (i.e. it does not have a value); e.g. when a particular form field, such as a signature field is not filled in.
is Value: Select if input's value is populated. For example:
is True: You can use a formula like =IF([trigger.Job #] = "", "True", "False") to check if a field is blank and return "True" if it is.
is False: A formula such as =IF(AND(VALUE([trigger.Job #]) >= 8000, VALUE([trigger.Job #]) <= 8999), "True", "False") can be used to check if a value is outside a specific range and return "False" if it is.

Action Options:

Skip: If condition value and operator are met command step will be skipped
Terminate: If condition value and operator are met workflow will be terminated. Please note that this workflow will not show as failed. Examples:
Terminate: Use a condition like =IF([trigger.Job #] = "", "True", "False") to terminate the workflow if a required field (e.g., Job Number) is blank.
Skip: Use a condition like =IF(AND(VALUE([trigger.Job #]) >= 8000, VALUE([trigger.Job #]) <= 8999), "True", "False") to skip the step if a field value does not meet the desired range.

These inputs can be used on any action to skip the action or terminate the workflow if the condition is met. You can use several of these inputs in conjunction — for example, if you want to skip the step if a certain form field is false OR if another form field has no value, you can do that using the is False Skip Step and is Null Skip Step inputs together, as shown in the image below. However, you cannot use the same input twice — e.g. you cannot have two is Null Skip Step inputs in the same step.

With skip logic, the workflow will check skip first and then terminate. If a skip condition is met, it will just skip the step and not check the terminate criteria.

Troubleshooting Common Issues

If emails are sent regardless of the conditions, check the following:

Avoid Using Template Events:
- Template Events do not support step conditions and will always send emails. Replace them with step conditions on the Send Email workflow step.
Verify Step Conditions:
- Ensure the conditions are applied to the correct step (Send Email) and not to a separate step.
Check Field Name References:
- Use the exact field name in your formulas. For example, if the field is named Job #, do not use Job Number in the formula. By addressing these issues, you can ensure that emails are sent only when the specified conditions are met.

Example Scenario

Suppose you want to send an email only when the Job Number is between 8000 and 8999. You would:

Add a Form Completed trigger scoped to the relevant Template Folder.
Configure the Send Email step with the following conditions:
- Terminate the workflow if the Job Number is blank.
- Skip the email step if the Job Number is outside the range of 8000–8999. This setup ensures that emails are sent only for forms meeting the specified criteria.

Important Notes:

Template Events do not support step conditions and will always execute the associated action. Ensure conditions are placed directly on the relevant workflow step, such as the Send Email step.
When using formulas in conditions, ensure that field names match exactly as they appear in the template (e.g., Job # instead of Job Number).

Workflow Conditional Logic