Reduce automations using 'Any of' tag conditions

One automation per tag adds up fast. If you have separate automations for multiple client groups—each with its own tag—but they all trigger the same action, the Any of condition type lets you replace all of them with one. It fires whenever a client has at least one of the specified tags.

Before you start: how “Any of” conditions work

Conditional automations in pipelines run when an account meets certain tag criteria. The condition type controls how those tags are evaluated:

• Any of—the automation fires if the account has at least one of the selected tags

• All of—the account must have all selected tags

• None of—the account must not have any of the selected tags

• Exclude all—the account must not have all of the selected tags simultaneously

You can read more about all condition types in this article .

Step-by-step setup

In this example, a firm sends the same tax organizer to all business clients—whether tagged S-Corp, C-Corp, or Partnership—using one automation instead of three.

Step 1. Create tags

Create a tag for each client group that should trigger the automation and apply them to your clients.

Step 2. Add the automation

In pipeline settings , go to the stage where the automation should run and add an automation . Set up the automation as usual—in this example, Create organizer.

Step 3. Add an “Any of” condition

Click Add conditions under the automation name:

1. Select all the tags that should trigger it—in this example, S-Corp, C-Corp, and Partnership.

2. Set the condition type to Any of.

3. Click Save.

The automation now fires for any client that has at least one of those tags.

Step 4. Test the setup

Apply one of the tags to a test client and move a job for that client into the stage. Confirm the automation triggers. Repeat with the other tags to verify all groups are covered.

Share

Link copied