Match any incoming messages to your integration flow with the Filter integration connector

Programming language:


Current state:


Provider of the connector:

Type of license:

Apache 2.0

What makes this component very useful to integrators is that you not only can filter data with it, but you can send the data that doesn’t fit (in other words, gets rejected) to some other integration flow (aka. fork).

Please take into consideration that only those integration flows that start with a webhook can be selected as a reject flow.

About Filter integration connector

This is an open source connector to pass through an incoming message if it matches the condition specified in the configuration of your integration flows. It was developed specifically to run on platform.

Due to its role in the integration workflows, the Filter integration connector only supports the action functionality, which means that you can use it to execute a certain event. In the case of this particular connector, it filters incoming data based on arbitrary expression.

Follow the Documentation link above to find what you need to do to set it up and to see a few examples.

Like with all other connectors that are under the Apache license, you can clone it and enhance it yourself to include more functionalities out of the box. Alternatively, you can contact our pre-sales team at ps[at] if you prefer our developers to extend the Filter integration connector for you.

Filter integration_screenshot


PLEASE NOTE: You need to be registered on the integration platform in order to use the Filter integration connector. You can sign up for a free 14-day trial here.