Send Admin API version out of date (uses 2024-04 API)

[brndanws]

Hi all. I've set up an automation to automatically ingest custom product types and map them to Category via Shopify Standard Taxonomy, which opens up access to standardised metafields. I'm using an Admin API action / productUpdate mutation to do this. The problem I'm having is that productUpdate only responds to mutations/schema from API 2024-04, while the current stable API version is up at 2024-10. The API since 2024-07 has deprecated productCategory / productTaxonomyNodeID and replaced it by "category" which takes a category ID as a string, and the standard taxonomy list has also had the taxonomy Node ID's deprecated/removed in favour of said category IDs. The "limitations" section in the reference document reads:

The Send Admin API request action has the following limitations:

• The action will display a list of Mutations and Mutation inputs from Shopify Admin API version 2024-04.

Suffice it to say, the action is is 2 API versions behind and Shopify don't even offer a list of node IDs anywhere any longer (all links to the list 404/have been removed). I was able to find one to use for my workflow/mutation, like so (triggered by product status change, if productType is one of x, y, z, then action productUpdate)

{
  "input": {
    "id": "{{product.id}}",
    "productCategory": {
      "productTaxonomyNodeId": "gid://shopify/ProductTaxonomyNode/775"
    }
  }
}

This works and the category is assigned using the deprecated properties. For instance, 775 used above corresponds with Arts & Entertainment > Hobbies & Creative Arts > Musical Instruments > String Instruments > Guitars  in the old node ID list.

... but there are now further sub categories (Acoustic Guitars, Electric Guitars, Bass Guitars, Classical Guitars) used in the standard taxonomy which are not accessible by node ID / have no node IDs assigned / are not present in the now "deleted" taxonomy list. If I attempt to use the new "category" property to assign these sub categories my products (gid://shopify/TaxonomyCategory/ae-2-8-7-2-4 is Guitars > Electric Guitars for instance) it fails with error: Ran into exception: Mutation had errors: "Variable $input of type ProductInput! was provided invalid value for category (Field is not defined on ProductInput)"

So I guess my question is: when will Flow / this action be brought up to the current API version? is there a roadmap for this? Is there a different way for me to be doing this which doesn't require me to use deprecated properties in the mutation? It's bizarre that it is so far behind as a first party product.

Thanks for any help you can provide,
Brendan

[paul_n]

Yes, there is a roadmap. Recent API versions have brought many breaking changes and Flow tries to help merchants manage breaking changes. It's a lot of work across the entire API. 

We have a project that will enable Flow to more quickly adopt API versions but we need to finish building it. So not sure sure when the next version bump will happen but not in Q4. 

[leelandio]

Paul,

Just chiming in to express my interest in API version update for Flow.

Really just need Order.shippingAddress.validationResultSummary

We want to trigger on Order Create > Check if validationResultSummary shows ERROR || WARNING > Hold order fulfillment

But, validationResultSummary is not present on the current API Version.

I'm in the middle of (learning) how to write a custom Flow Action extension that will do what we need; but, I'm struggling 😂

Do you have any recommendations for a potentially simpler approach that can do what we need:

Order Create > Check if validationResultSummary shows ERROR || WARNING > Hold order fulfillment

[RPiii]

Flow now supports Admin API version 2024-07.

[Vault_Ally]

Psst! Thank you for your post, because you helped me solve an issue myself.

Take the URL for the nodes that's giving a 404, and throw it in the Wayback Machine. It was archived March 2024. That'll get you through until they update the API!