Shopify Next Generation Events Developer Preview
Configure event subscriptions in shopify.app.toml with field‑level triggers and a custom GraphQL query to receive only the data you need.
Add a subscription block to shopify.app.toml, specify field‑level triggers and a GraphQL query, and test the event payload to ensure it matches your application logic.
Summary
Shopify has released a developer preview of Next Generation Events, a new event system that gives developers fine‑grained control over when events fire and what data they carry. The preview introduces field‑level triggers, so a subscription to product.variants.price will only fire when the price changes, ignoring title edits or status changes. Subscriptions are defined in shopify.app.toml and include a GraphQL query that specifies the exact payload, eliminating over‑fetching and the need for a second API call. Each delivery now contains a fields_changed list that lists the exact entity paths that triggered the event, along with query_variables used to fetch the payload.
The unstable API version exposes Product and Customer topics, and a query_filter can be applied to skip events that do not meet current state conditions, such as only delivering for active products. The event payload includes the full data returned by the query, the fields_changed array, and the query_variables, making it straightforward to process the event without inferring state. Developers can test the preview by adding a subscription block to shopify.app.toml and observing the JSON structure shown in the documentation. The preview is subject to change, so monitoring the API documentation for updates is recommended.
Key changes
- Field‑level triggers allow subscriptions to fire only on specified field changes.
- Subscriptions defined in shopify.app.toml with a GraphQL query for custom payload.
- Delivery payload includes fields_changed array listing exact entity paths that triggered the event.
- Delivery payload includes query_variables used to fetch the data.
- query_filter can be applied to skip events that do not meet current state conditions.
- Unstable API version exposes Product and Customer topics in preview.
- Subscriptions live in code, version‑controlled, and deployable.