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 of the GraphQL Admin API include:
-
Advanced querying of metafields and metaobjects: We've expanded the resources that you can query by metafield value to include Companies and Company Locations. We've also expanded how you can query metafield values on Products, Orders, and Metaobject entries to include greater than and less than comparisons, prefix matching, and boolean operators (AND, OR, NOT). (changelog)
-
Access transactions on the Return object: You can now access transaction data directly on the
Returnobject that is included on triggers related to returns. (changelog)
-
New return reason definitions: You can now use the new
ReturnReasonDefinitiontype to capture more granular, category-specific return reasons when managing returns. This replaces the previousReturnReasonon theReturnobject that is included on triggers related to returns. ThereturnCreateandreturnRequestmutations also accept this field as an input when using the mutation in a Send Admin API request action. (changelog)
- orderUpdate mutation now includes phone field: This field allows merchants to update the customer phone number for an order, overwriting the existing phone number, when using the mutation in a Send Admin API request action. (changelog)
For more information about how Flow uses the GraphQL, visit the documentation. To learn more about changes introduced in version 2026-01, visit the Developer changelog.
