Previously, the URL for Flow Trigger Lifecycle Callback extensions were required to be absolute HTTPS URLs pointing to a web server. This required an already hosted system which made it inconvenient to test locally before deployment. Additionally, it required that the full URL be updated in addition to a Shopify app's when being used with a dynamically tunneled server whose URL might change.
Now, Flow Trigger Lifecycle Callback extensions support relative URLs in addition to absolute HTTPS URLs. This works similarly to relative URLs with Flow action extensions. Running app dev resolves your relative URL against your development tunnel URL and app deploy resolves against your app's
Use an absolute HTTPS URL when your endpoint is hosted outside your app or you want Flow to call the same URL in every environment. Protocol-relative URLs (such as ) aren't supported, and your app configuration must include an HTTPS application_url before you deploy with relative paths.
For more details, see the Flow trigger lifecycle callback configuration reference.