Using Logic Conditions in Workflows

As your workflows grow, you may find yourself creating multiple workflows with the same trigger but different actions. Logic Conditions let you keep everything in a single workflow by creating multiple paths based on specific criteria, allowing the workflow to automatically decide what happens next.

A Logic Condition is a helper action available within Workflow Automation. It acts as a decision point in your workflow, evaluating specific data and directing the workflow down the appropriate branch.

Each branch can have:

This allows a single workflow to handle multiple scenarios automatically.

Once you have selected a workflow trigger:

When the workflow runs, Lawcus evaluates each branch and sends the record down the branch whose conditions are met.

Each branch contains a condition builder that allows you to define exactly when that branch should execute.

When creating a condition, you'll configure:

The field you want to evaluate.

This can come from:

The rule used to compare the field value.

Common examples include:

The value the field will be compared against.

Together, these settings determine whether a record should continue down a particular branch.
​

Let's say you have a workflow that triggers whenever a new matter is created.

You want matters tagged "Probate" to follow one process, while all other matters follow a different process.

Rather than creating separate workflows, you can use a Logic Condition to split the workflow into two branches.
​

Condition: Matter Tags contains "Probate"

Action: Create a task for the intake team.

Any matter that contains the Probate tag will enter this branch and perform the actions configured within it.
​

Condition: Matter Tags does not contain "Probate"

Action: Perform a different action, such as assigning a task, sending a notification, updating a field, or ending the workflow.
​

Any matter without the Probate tag will automatically be routed to this branch.

In this example, a single workflow can handle two different processes based on the information available on the matter.

A branch can contain more than one condition, allowing you to create more precise automation rules.
​

Use OR when any condition can qualify a record.

Example:

If either condition is true, the workflow will enter that branch.
​

Use AND when all conditions must be true.

Example:

The workflow will only enter the branch when both conditions are met.

This flexibility makes it easy to build workflows that respond to a wide range of business scenarios.
​

Logic Conditions are not limited to just two branches.

You can create as many branches as needed, with each branch evaluating its own set of conditions.

For example, you could create separate branches for:

Each branch can perform completely different actions while remaining part of the same workflow.
​

For more advanced automation, you can place a Logic Condition inside another branch.

For example:

This creates a structured workflow that can handle increasingly detailed decision-making without requiring multiple independent workflows.
​

Logic Conditions help you:

To get the most out of Logic Conditions:

Logic Conditions add powerful decision-making to your workflows by allowing records to follow different paths based on criteria such as tags, stages, custom fields, and other record data. This helps you automate actions more efficiently, reduce the need for multiple workflows, and manage complex processes from a single, organized automation.