Add search filters narrow down automatically via SDK/API similar to the asset bank

Welcome to the Community ​@perezdavid. Thank you for taking the time to ask your question. Indeed I can see why that can be frustrating. I can certainly create an insight for your request to send the product team and let you know if there are any updates.

In the meantime, it would be great to hear if any others have a similar use case and how they handle this.

Hello ​@Ryanne Perry , Thank you for generating this report. I think it can be very interesting for other users who are using the API.

Hi ​@perezdavid can you please clarify if you are referring to automations or filtering here? Or is it both?

• Automations, that are the dependencies and triggers that we create between metaproperties
• Filtering, that should be related to assets, and refers to Smart filters

Hi ​@Ryanne Perry 

I am referring to automations. For example in Bynder if I select the ‘Airline Equipment’ family, the subfamily only filters the values to that family because we have defined it that way in the automations.

On the other hand, through the API, despite selecting the ‘Airline Equipment’ family, the options in the subfamily are all:

Thank you,

David

This is helpful, thank you ​@perezdavid. I can confirm that the product team is working on a new Enrichment API that will make it possible to reuse the automations through integration. The current plan is to have this available sometime in the second half of the year.

Hey there ​@perezdavid — just wanted to clarify something on our end. We actually goofed a bit with the question; it should’ve been comparing uploading vs filtering, not automations. Automations are used in both cases, so that part applies either way.

From the screenshot you shared, it looks like you might still be referring to smart filtering. Here’s how that works:

Filtering takes other selected values into account — so while it doesn't directly apply automations in the moment, it can seem like it does. That’s because automations already did the work during upload, preventing incorrect options from being saved in the first place.

For example, let’s say you have automations set up for Country and City. During upload, it ensures that someone can’t tag a Belgian asset with a Dutch city. So no assets will have mismatched data like that.

Then, when you're filtering: if you pick “Netherlands” as the country, the system shows cities from assets where Country = Netherlands. Thanks to the automation, those cities will only be Dutch — because incorrect combos never made it in.

One more thing: if you were to push data in via the API (which doesn’t enforce automations), you could end up with mismatched values — like a Dutch city and Belgium as the country. And then those mismatches might surface in filtering.

Hope that clears things up a bit!