ETA on External API calls

Hi!

On the roadmap, it is mentioned that external api calls are estimated to be delivered in Q1 of this year.

Is that still optimistically set? I know there’s still a couple of months left, but my intentions to use it have been increasing over the last few months.

External API calls for what exactly? Can you share more context here?

I guess Shopify Flow based off the category picked.

Currently available is the Admin API or external HTTPs but without a response to work with.

Can recommend using Arigato or Mechanic for more advanced automations with external API handling.

My most recent usecase would be to pull some data from an external API, so I can update a metafield with the value. This value is the exact same as the store credit value on a customer account.

I originally wanted to do this natively with Shopify, but I am unable to retrieve the store credit balance within Flows (that I am aware of). The merchant that requests this is not on a Plus plan, so creating an app is out of the equation.

Would use Arigato or Mechanic for this until Shopify Flow supports it.

So to answer your question; no one knows :yum: At least you got bumps for attention :clown_face:

Some form of fetch with return data should be delivered this year. We are currently figuring out what comes first, what’s part of the initial release, etc. Actually returning data is now trivial assuming you use Run code to parse it (I’m actually testing it now) and you only need Basic auth (and not OAuth). The larger part is how far we take the UX and improvements for secrets/authentication/etc.

2 Likes

As far as I know you cannot use any returned data from “Send HTTPs Request” and “Run Code” cannot do fetch requests at all, yet.

Only the Admin API Request action can return usable data - but that’s not helpful working with external APIs, public or private.

If this is possible in other ways, please let me know :yum:

If you have an app (or create one), you can build a task that returns data right now.

1 Like