Hi. I have a feature request to the Shopify Flow Team.
When inspecting a Flow run log, Shopify’s native triggers display a convenient resource link directly on the trigger card.
This link is not available for triggers provided by third-party apps.
Is it possible to show the same resource link for third-party triggers as well? Currently, users have to expand the step data, manually find the resource ID, and navigate to the resource by editing the URL.
Hey @Yuri_K - thanks for flagging this. I can see how that would make run logs easier to inspect. Right now, Flow trigger extensions don’t expose a way for apps to specify the run-log resource link directly. Could you share what kind of resource you’d want linked here: an existing Shopify resource like an order/customer/product, or an app-owned resource/page? Also, would the link need to open Shopify Admin, your embedded app, or an external app URL?
Hope to hear from you soon.
Hi @Alan_G,
Thanks for looking into this!
Flow trigger extensions already support reference field types for Shopify resources (orders, customers, products, etc.): Flow trigger reference
My suggestion is that if a trigger payload contains one or more of these reference values, Flow should automatically display the corresponding resource links in the run log - the same way it does for native triggers.
No new API surface should be needed for this. Flow already has everything required: the resource type and the ID. It’s just a matter of rendering the link in the run log UI based on what’s already in the trigger payload.
The link should open the resource in Shopify Admin, so the behavior is consistent with what native triggers already do.
Hey @Yuri_K - thanks, that clarification helps a lot.
That makes sense as a Flow feature request for sure. Flow already has the resource type and ID in the trigger payload, so rendering the same kind of Admin resource link in the run log would make the third-party trigger experience more consistent with native triggers.
I’m going to pass this along internally, but for now, the current workaround is still expanding the step data and navigating from the resource ID manually, which I agree is not super ideal.
