Use a Filter Step
Use a filter step after a trigger to prevent workflows from executing if the filter query yields no matches. Filter steps are very useful when your workflow is looking for only specific data to fully execute through the workflow. Otherwise, data will come through via the trigger and be rejected by the filter, without your intervention.
Filter steps have two options:
- "Only continue if" the filter requirements are met
- "Stop execution if" if the filter requirements are met
Filters After Triggers
Filters that immediately follow triggers are handled differently than filters in the middle of a workflow. If a filter immediately follows a trigger, it’s a signal that anything not passing the filter should not be entered into the system as a record. If the trigger is later in the workflow, you’ll see records of the workflow being run, but stopping where it failed to pass the filter.
Add a Filter Step
To add a filter step to your workflow:
- After choosing Filter in the step choice panel, name the filter.
- Define the query for your filter to match against using the Filter Query Language. If no matches are found, no job will be created for the trigger event.
- Click Continue to save the step.
If you have further questions relating to InsightConnect, try starting a discussion in the Rapid7 Discuss community forum.