Webhook filter enhancements
Release date: 15th October 2025
In this release we've made some enhancements to webhook filtering, providing developers with greater flexibility in controlling when webhooks requests are sent. The In and Equals filters now support arrays, which allows you to filter on multiple delivery keys. A new Is Present filter checks for the existence of a specified field, so you can now filter on fields that may not be present in the webhook payload.
The Is Present filterLink copied!
Fields such as locale and workflow state will only be included in webhook payloads when they have a value set, and not all of the payloads for each webhook event will include these values. Using the Is Present filter you can check for the existence of a specified JSON path, such as payload.workflow, and the filter condition will only be passed if the field exists in the payload.
In the example shown below, we've set the webhook trigger to "content item- updated" and the payload for this event will only include the workflow status if one is set for the content item.
The Is Present filter is selected with a JSON path of $.payload.workflow. The filter condition will only be met (and the webhook request sent) when a workflow status is included in the payload.
Filtering on array valuesLink copied!
The In and Equals filters now support arrays, and one of the uses for this is to filter on the value of multiple delivery keys.
In the following example we're using the "content item- updated" webhook event and setting multiple "In filter values to check for variant delivery keys set to "mens/shoes" or "womens/shoes". If either of these conditions is met then the filter condition will pass.
To filter on the variant delivery key values array we use the following syntax:
_meta.deliveryKeys.values[*].value.
The path will depend on the webhook payload, but in this case it is:
$.payload.body._meta.deliveryKeys.values[*].value
