In some scenarios, you may need to only work with bundles that fit specific criteria. Filters will help you to select those bundles, easily.
You can add a filter between two modules and check whether bundles received from the preceding modules fulfill specific filter conditions or not. If yes, the bundles will be passed on to the next module in the scenario. If not, their processing will be terminated.
An example of how handy filters are, is if you were wanting to create a scenario with the Facebook trigger Watch posts and wanted to work only with posts containing a specific word or posts written by a specific author, a filter would make sure you received only these posts and nothing else.
To add a filter between two modules, click on the connecting line between them. This will bring up a panel where you can enter the name for the filter that is 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 Dropbox trigger Watch files and the OneDrive action Upload a file. The filter condition created between them (file name with xml.ending) is automatically applied to incoming bundles from the first module and only bundles containing the xml.ending in its name are allowed to pass on to the next module.
For each condition, you can use one of several different operators.
There are a number of other operators you can use: text comparison operators, numerical operators, time and date operators, and operators for working with arrays.
Copying of filters is currently not natively supported by the scenario editor, though if you use the Google Chrome web browser, the following workaround can be employed: