Webhooks via TOML – Possibility of Filtering Based on Shop Metafields?

Hi folks,

We had a quick question (and a potential feature request) around app-managed webhooks.

We’d love to be able to filter webhook delivery based on shop metafields — not just the webhook entity itself. Currently, as I understand, the webhook filters only apply to the resource the webhook is associated with (e.g., orders, products, etc.).

However, enabling filtering by shop-level metafields could unlock significant value:

  • Apps could configure shop-specific webhook behaviors declaratively in the shopify.extension.toml file.
  • It would reduce the need for runtime config logic in our app servers to decide how to handle webhook payloads.
  • This would also streamline onboarding and maintenance for apps supporting a large number of merchants with varying requirements.

Is this something on the roadmap or worth considering for future support?

Would love to hear your thoughts!

Hi @Sakshi_Gupta

I’m sure you’re aware of this, but you can work around this issue by registering webhooks yourself through the Admin API based on the shop’s metafields.

It’s a bit more code to manage, but if you need that level of specificity that is a nice way to reduce your webhook load.

Yeah we are doing that today, but seems more like something we would love to not manage - reason being if we add a new webhook now to install it for older merchants we need to run a script, similarly if we do not want to continue with one.
At scale with larger number of merchants bit of a tedious thing to manage. Times when we change the handlers we need to completely reinstall the webhook !