Flow adopts version 2026-01 of the GraphQL Admin API

Topic
API
Published

This summary was written by ShopDigest AI from Shopify Changelog’s report. Read the full story ↗

Flow now uses version 2026-01 of the GraphQL Admin API, which includes new options for building automations. Some of the changes in version 2026-01…

Overview

Flow now uses version 2026-01 of the GraphQL Admin API, introducing new capabilities for building automations. The update expands querying options for metafields and metaobjects, adds transaction data to return triggers, and introduces more granular return reason definitions.

Key Changes

  • Advanced metafield querying: Companies and Company Locations can now be queried by metafield value, and Products, Orders, and Metaobjects support greater/less than comparisons, prefix matching, and boolean operators.
  • Return object now includes transaction data on return-related triggers.
  • New ReturnReasonDefinition type replaces ReturnReason, allowing category-specific return reasons; returnCreate and returnRequest mutations accept this field.
  • orderUpdate mutation now includes a phone field to update customer phone numbers.

Frequently asked questions

What version of the GraphQL Admin API does Flow now use?

Flow now uses version 2026-01 of the GraphQL Admin API. This version includes new options for building automations, such as advanced metafield querying and updated return handling.

What new querying capabilities are available for metafields in Flow?

The update expands metafield querying to include Companies and Company Locations. It also adds greater than and less than comparisons, prefix matching, and boolean operators (AND, OR, NOT) for Products, Orders, and Metaobject entries.

How has return handling changed in Flow with version 2026-01?

Return triggers now provide direct access to transaction data on the Return object. Additionally, a new ReturnReasonDefinition type replaces the previous ReturnReason, allowing more granular, category-specific return reasons when managing returns.

Can merchants update customer phone numbers on orders using Flow?

Yes, the orderUpdate mutation now includes a phone field. This allows merchants to update the customer phone number for an order, overwriting the existing number, when using the mutation in a Send Admin API request action.

About this story

Topics covered
Published
15 Jan 2026
Originally published at