Shopify’s automation engine, Flow, just got a major upgrade. The new “updated” triggers let you react instantly when a customer, order, refund, fulfillment order, return, collection, location, or inventory item changes. No more scheduled jobs, no more work‑arounds—just real‑time workflows that fire the moment a field you care about is modified. In this post we break down the update, explain who should care, and give step‑by‑step guidance for merchants and developers ready to put the new triggers to work.
What’s New in Flow
Shopify Flow now includes eight additional trigger types: Customer updated, Order updated, Refund updated, Fulfillment order updated, Return updated, Collection updated, Location updated, and Inventory item updated. Each trigger mirrors the existing “Product updated” behavior—you select up to five fields to monitor, and whenever one of those fields changes, the workflow starts automatically. This eliminates the need for cron‑based checks or custom webhook scaffolding for many common scenarios.
Who Is Affected?
Both merchants and developers benefit, but in different ways. Merchants gain immediate, no‑code automation possibilities—think “Notify the fulfillment team when an order’s shipping address changes” or “Add a tag when a product is removed from a collection.” Developers, on the other hand, receive a cleaner set of webhook events and a standardized trigger schema, making it easier to build apps or custom integrations that rely on real‑time data changes.
How the Updated Triggers Work
When you create a new Flow workflow, you’ll now see the eight “updated” options alongside the classic “created” triggers. After selecting a trigger, you choose which fields to watch (up to five). For example, the Order updated trigger can monitor fields such as shipping_address, email, fulfillment_status, financial_status, or tags. If any of those fields change, Flow evaluates the workflow conditions and runs the actions you’ve defined.
Below is a JSON representation of a typical “Order updated” trigger configuration you might export from Flow’s UI:
{
"trigger": "order.updated",
"watched_fields": [
"shipping_address",
"fulfillment_status",
"tags"
]
}
Real‑World Use Cases
Implementation Steps for Merchants
No code is required, but the UI now surfaces the new trigger options, making it straightforward for non‑technical store owners.
Implementation Steps for Developers
Developers building apps that rely on Flow or Shopify webhooks should note the following changes:
orders/updated, customers/updated, inventory_items/updated. Subscribe to them via the Admin API as you would any other topic.flowTrigger mutation now accepts a watchedFields argument for the updated triggers. Example:graphql
mutation CreateFlowTrigger {
flowTriggerCreate(input: {
triggerType: ORDER_UPDATED
watchedFields: ["shipping_address", "tags"]
}) {
flowTrigger {
id
}
userErrors { field message }
}
}
flowTriggerTest endpoint to simulate field changes without touching live data.By updating your app’s subscription list and leveraging the new GraphQL mutation, you can give merchants a seamless experience that reacts instantly to data changes.
Best Practices & Tips
Conclusion & Next Steps
The new “updated” triggers turn Flow into a truly real‑time automation platform, giving merchants the agility to respond to critical data changes and developers a cleaner webhook landscape. Start by picking one of the eight new triggers that aligns with a pain point in your store, build a quick proof‑of‑concept workflow, and watch the time savings stack up. Need help setting up or want a custom integration? Reach out to a Shopify Expert or drop a comment below—let’s get your store running smarter, not harder.
