September 23, 2026 · Ahmed · More by Ahmed
Shopify Flow's New Get Analytics Data Action
A new Shopify Flow action runs ShopifyQL queries on a schedule and turns the results into automation triggers, not just dashboard numbers.
Shopify Flow has always been a triggers-and-actions tool sitting next to your store's data, not inside it. Spring 2026 Editions changes that relationship for analytics specifically: a new Flow action called "Get Analytics data" runs a ShopifyQL query on a schedule and feeds the result straight into a workflow's conditions or actions.
Concretely, that means a report you'd normally have to open the Analytics dashboard to check can now decide, on its own, whether to notify a team, tag a product, or kick off another workflow step. Shopify's own worked example: a Flow runs daily, checks whether sales for a specific product have reached 90% of a $18,000 target, and when it crosses that mark, automatically notifies the marketing team to email customers that the product is selling out. That's the shift — the query result becomes a condition a workflow branches on, not just a number on a chart.
Part of a broader analytics push
The Analytics action shipped as one of five Spring 2026 Editions updates to Analytics — alongside prioritized Insights, chart annotations tied to store events, metafield and metaobject filtering, and metric targets with a progress gauge. Get Analytics data is specifically the piece that lets that reporting layer trigger action instead of just informing a dashboard someone has to check manually.
A separate batch of new Flow data actions
It also arrived close to a separate, unrelated batch of Flow additions: on March 24, 2026, Shopify shipped "Get data" actions for workflow runs, abandoned checkouts, inventory items, and pages, each returning up to 100 matching resources per call. The Get workflow run data action is worth calling out on its own — it surfaces a workflow's own retry attempts and timing details, which is what you'd reach for if you wanted a Flow workflow auditing the reliability of other Flow workflows rather than reading store data at all. The Get abandoned checkout data action gives Flow direct visibility into carts a customer started but didn't finish, useful for recovery or follow-up workflows that previously needed a dedicated app.
Where this changes what's practical
The useful pattern here is a scheduled ShopifyQL query standing in for a metric you'd otherwise have to check by hand: a daily sales-versus-target check, a session report sent to a channel, or a collection that updates itself based on which products are actually selling. None of that required custom code before Flow could read Analytics results directly — it required someone remembering to look. Whether that's worth building depends entirely on whether the ShopifyQL query you'd write is one you already run by hand today; if it is, this is the action that turns it into something that runs itself.