Flow Gains Real-Time “Updated” Triggers for Orders, Customers, and More

Shopify Flow now offers eight new “updated” triggers—covering customers, orders, refunds, fulfillments, returns, collections, locations, and inventory items. Learn what changed, who it impacts, and how to implement the new triggers to automate real‑time responses in your store.

Flow Gains Real-Time “Updated” Triggers for Orders, Customers, and More
8 sections

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

  • Shipping address change alert – When a customer updates their shipping address after an order is placed, a Slack or email notification can be sent to the fulfillment team to avoid mis‑shipments.
  • Inventory sync – If an inventory item's quantity changes, trigger a webhook to update a third‑party ERP system in real time.
  • Collection management – Detect when a product is added to or removed from a seasonal collection and automatically apply or clear a discount metafield.
  • Refund follow‑up – When a refund is updated (e.g., partial to full), send a personalized email asking for feedback or offering a coupon.
  • Location updates – If a store’s location details change, update all related POS terminals via an API call.
  • Implementation Steps for Merchants

  • Open Flow – From your Shopify admin, go to Apps → Flow.
  • Create a new workflow – Choose “Create workflow” and select the appropriate “updated” trigger (e.g., Order updated).
  • Select fields – In the trigger settings, pick up to five fields you care about.
  • Add conditions (optional) – Use “If/Then” blocks to narrow the scope (e.g., only run if fulfillment_status changes to “delivered”).
  • Add actions – Choose from built‑in actions (Send email, Post to Slack, Update metafield) or custom webhook actions.
  • Test – Manually edit the watched field in a test order or customer record and verify the workflow fires.
  • Activate – Once verified, turn the workflow on for production use.
  • 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:

  • Webhook topic names – New topics are now exposed, e.g., orders/updated, customers/updated, inventory_items/updated. Subscribe to them via the Admin API as you would any other topic.
  • GraphQL schema – The 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 }

    }

    }

  • Rate limits – Updated triggers fire only when the watched fields change, which reduces noise and keeps you within Shopify’s webhook rate limits.
  • Testing – Use the GraphQL 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

  • Limit the number of watched fields – Each trigger allows a maximum of five fields; choose the most impactful ones to avoid unnecessary executions.
  • Combine with “Condition” blocks – Even if a field changes, you may only want to act when the new value meets certain criteria (e.g., shipping country equals "US").
  • Use throttling for external APIs – If your workflow calls third‑party services, add a delay or retry logic to handle burst traffic when many records update at once.
  • Monitor workflow runs – Flow’s run history shows which trigger fired and why; use it to fine‑tune field selections.
  • Document for teammates – Keep a simple markdown file in your repo describing each updated trigger you’ve implemented; it helps onboarding and audit.
  • 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.

    Tags
    Sources

    Related Articles

    Email and Text Receipts Now Mirror Your POS Printed Receipt

    Email and Text Receipts Now Mirror Your POS Printed Receipt

    Shopify POS receipts sent by email or SMS now use the same template as printed receipts, eliminating duplicate templates and simplifying compliance. Learn what changed, who it impacts, and how to update your settings and code.

    November 20, 20264 min
    Server Pixel Mutations Now Enforce App Access: What Developers Need to Know

    Server Pixel Mutations Now Enforce App Access: What Developers Need to Know

    Starting November 20 2026 Shopify’s eventBridgeServerPixelUpdate and pubSubServerPixelUpdate mutations require a user with app access. Learn what changed, who’s impacted, and how to adjust your code to avoid access‑denied errors.

    November 20, 20264 min
    Embedding YouTube & Vimeo Directly via File Reference Metafields in Shopify API 2027-01

    Embedding YouTube & Vimeo Directly via File Reference Metafields in Shopify API 2027-01

    Shopify’s 2027-01 API now lets file reference metafields store YouTube and Vimeo video URLs, unlocking seamless video embeds for merchants and developers. Learn what changed, who it affects, and how to implement the new feature today.

    November 20, 20265 min
    Why Your Shopify App Must Enable IP Allowlist by Tomorrow (Nov 20 2026)

    Why Your Shopify App Must Enable IP Allowlist by Tomorrow (Nov 20 2026)

    Shopify’s latest security deadline forces public and custom apps to add an IP allowlist. Learn what changed, who’s impacted, and step‑by‑step how to stay compliant before the November 20 cut‑off.

    November 19, 20265 min