Users initially struggled to trigger email notifications when Shopify Forms are submitted, as form submissions weren’t available as a Flow trigger. A Shopify representative confirmed this limitation and noted the team was working on a solution.
Current Solution:
Shopify now supports form submission workflows through the “Metaobject entry created” trigger in Flow. When a Shopify Form is created, it automatically generates a metaobject that can be selected in this trigger.
Implementation Steps:
Install Shopify Flow app
Create workflow using “Metaobject entry created” trigger
Select the metaobject definition corresponding to your form
Add email actions (internal or marketing emails)
Key Limitations:
“Send Marketing Email” action only works for customers subscribed to marketing emails
For transactional/confirmation emails to non-subscribers, users must use third-party email apps via “Send HTTP Request” or other email actions
Shopify Forms lacks support for hidden fields or capturing submission URL/page context
Cannot easily differentiate between specific forms without custom tagging
Workarounds:
Some users report using alternative platforms (Klaviyo, Go High Level CRM) for more flexible form-to-email automation. The native Shopify Forms automation section offers basic email sends but lacks granular control per form.
Summarized with AI on October 28.
AI used: claude-sonnet-4-5-20250929.
I’ve installed Flow and now want to set up a flow that sends an email to the email address inputted into the Shopify Forms form when the form submit is successful.
I’m looking at triggers and Shopify Forms doesn’t show up as something I can choose as a trigger. It’s not listed under “Shopify” or under available apps.
Admitting I made an assumption that Shopify Flow and Shopify Forms would just simply work together out of the box. Shouldn’t have done that…
But is there a way to create this straightforward flow?
For anyone who is trying to set up an automatic email send once someone submits your Shopify Form, I’ve learned that you can do this.
At the bottom of the set-up page for your Shopify Form there is a section labeled “Automations and workflows”. Click on “Manage” and you land on a page where you can set up the email send. Pretty straightforward to do.
Work is being done, yes. Not sure of timeline yet. It may seem trivial, but forms require a new type of event because each form can potentially be custom per shop. And you might only want to subscribe to events from a single form.
Good idea, I first thought the same, but it’s not a viable solution. You unfortunately cannot select a specific tag in the triggers, only “tag is added”, meaning all tags. So, this automation started sending out “first purchase discounts” to clients who had just made a purchase in my case.
This seems like such a standard option to include, I don’t understand why this functionality originally existed but then got removed if I read the comments above correctly.
This is exactly what I needed, and this thread is the only place I managed to find it. I feel like a “Form Submitted” trigger even just as an alias that comes from the Forms app would make this far more clear. Either way thanks for the solution!
I need to get the URL that a form was submitted on. Looks like this can be done using the {% form %} tag, but not the Forms app. Can a form built using the {% form %} tag create a new metaobject entry?
In general, it doesn’t seem like the Forms app has the ability to handle hidden fields or pass their values, if they did exist, to the default metaobject entries for each response.
Hey Paul! I would like to suggest that as a feature, then. If not the full hidden fields, then at least the “URL submitted on” feature.
Example 1: Contact form “ask a question” on a product page. Know which product a customer is asking about. Having a dropdown “select from one of the following 789 products” – not reasonable. “Input the product URL here” – seems very unprofessional, bad UI. Different form per product – Not possible.
Example 2: Contact form on a store location page template. Say the business has multiple locations and has a Template that is being used for each store location. To know which location the customer is contacting, without an unnecessary dropdown to select the store (it is bad UI in forms to ask customers info that you should already know), the business would need to make a separate Template and a separate Form for each store. Not good.