Build a more efficient connector with trigger usage webhooks
You can now receive a webhook from Flow that lets you track which stores are using your triggers in workflows. Use this data to make your apps more efficient and reduce the load on your web servers. For example, you can send trigger data to only those stores that need it. Learn more.
Recommended: Improve your security when identifying actions
Your HTTP POST payload now contains an ID that you can use to identify an action. Previously, the only way to identify an action was to use the URL. The payload is digitally signed, whereas the URL is not. Use the ID (
action_defintion_id) from the payload to identify your actions. Learn more.
When you receive an action, you can respond with a 202 status code to indicate that you received the action, but that you haven’t processed it. Flow will resend the payload (with the same
action_run_id) at a later time, so you have more time to process the action. Learn more.
Status code corrections
Flow will accept only a 200 status code for a successful response. If you currently use another 2xx code for successful responses, then you need to change it so that there is no disruption in your connector. Learn more.
HMAC header name change
The name of the HMAC header in Shopify Flow action HTTP POST requests is now the same as the other Shopify webhooks. The HMAC header name is now
X-Shopify-Hmac-SHA256. Learn more.
Where can I learn more?
Learn more in the connectors for Shopify Flow developer documentation, or contact firstname.lastname@example.org and a member of our engineering team will be happy to help out.