In some scenarios you may need to work only with bundles that fit specific criteria. Filters will help you to select those bundles.

You can add a filter between two modules and check whether bundles received from preceding modules fulfill specific filter conditions. If yes, the bundles will be passed to the next module in the scenario. If not, their processing will be terminated.

Filters can come in handy, when you, for example, create a scenario with the Watch posts trigger from the Facebook package and want to work with only posts containing a specific word or posts written by specific authors and the like.

Adding a filter

To add a filter between two modules, click on the connecting line between them. This will bring up a panel where you can enter a name for the filter to be created and define one or more filter conditions. For each condition, you can enter one or two operands and an operator that will determine the relation between them. In the operand field, you can enter values in the same way as you would map them.

In the example below you can see how to connect the Watch files trigger from the Dropbox package and the Upload a file action from the OneDrive package. The filter condition created between them is automatically applied on incoming bundles from the first module and only bundles containing the xml.ending in its name are allowed to pass to the next module.


For each condition you can use one of several different operators.

Basic operators

  • exists - checks whether a specific bundle item is filled in. Using this operator, you can create a filter that permits, for example, only Facebook posts containing a photo to go through to the next module in a scenario.
  • not exists - Not exists is the opposite of the above operator. It permits only those bundles where a specific item is not filled in.

Other operators

There is a number of other operators you can use: text comparison operators, numerical operators, time and date operators and operators for working with arrays.

Rate this article: