Filters can be described as a set of conditions that tell the Smart Action whether or not to run when triggered. You can add multiple filters to ensure the Smart Action only runs when the data passed by the trigger matches ALL the configured filters. If any filter does not match then the Smart Action will not run.

 

If you don't add any filters then the Smart Action will ALWAYS run when triggered.

 

Filters consist of 3 parts:

- Variable: A certain value passed by the selected trigger (such as the product name)

- Operator: The comparison to perform between the variable value and the entered input

- Input: The value to compare the variable with

 

Most variables are of text value (such as store or product name), however some might be numbers (price) or timestamps (date/time). Each value type has their own set of "operators".

 

For date/time operators, the input field placeholder will display which format to enter dates and times in (this is based on your system's locale info).

 

The operators for text values are as follows:

mceclip0.png

Note: All text operators are NOT case-sensitive 

 

- Equals: Input must EXACTLY match the variable value

  Example 1: Input: "Jordan", Value: "Jordan 1 Retro", Match: False

  Example 2: Input: "Jordan 1 Retro", Value: "Jordan 1 Retro", Match: True

 

- Not equals: Input must NOT match match the variable value

  Example 1: Input: "Jordan", Value: "Jordan 1 Retro", Match: True

  Example 2: Input: "Jordan 1 Retro", Value: "Jordan 1 Retro", Match: False

 

- Contains: The variable value must contain the input

  Example 1: Input: "Jordan", Value: "Jordan 1 Retro", Match: True

  Example 2: Input: "Retro", Value: "Jordan 1 Retro", Match: True

 

- Not contain: The variable value must NOT contain the input

  Example 1: Input: "Jordan", Value: "Jordan 1 Retro", Match: False

  Example 2: Input: "Yeezy", Value: "Jordan 1 Retro", Match: True

 

- Contains any: The variable value must contain ANY one text from the list separated by a coma

  Example 1: Input: "Jordan, Yeezy, Dunk", Value: "Jordan 1 Retro", Match: True

  Example 2: Input: "Yeezy, Dunk", Value: "Jordan 1 Retro", Match: False

 

- Contains all: The variable value must contain ALL text from the list separated by a coma

  Example 1: Input: "Jordan, Yeezy, Dunk", Value: "Jordan 1 Retro", Match: False

  Example 2: Input: "Jordan, Retro", Value: "Jordan 1 Retro", Match: True

 

- Not contain any: The variable value must NOT contain ANY one text from the list separated by a coma

  Example 1: Input: "Jordan, Yeezy, Dunk", Value: "Jordan 1 Retro", Match: False

  Example 2: Input: "Yeezy, Dunk", Value: "Jordan 1 Retro", Match: True

 

- Not contain all: The variable value must NOT contain ALL text from the list separated by a coma

  Example 1: Input: "Jordan, Yeezy, Dunk", Value: "Jordan 1 Retro", Match: True

  Example 2: Input: "Jordan, Retro", Value: "Jordan 1 Retro", Match: False

 

A common use of filters would be to use "positive" and "negative" keywords to only create/start tasks if the product restocked matches these keywords.

For example, in the main task creator you might enter "jordan, 1, retro, -gs, -kid" to find a product whose name contains "jordan", "1" and "retro" and does NOT contain "gs" or "kid". For Smart Action filters you would use contains all for positive keywords and not contain any for negative keywords like so:

mceclip2.png

Filters are very important in ensuring that a Smart Action only runs when desired. Please make sure to double check your filters before saving/enabling the Smart Action to avoid potentially unwanted checkouts!

 

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.