Request a feature
Tell us what would make Workflow Forms better. How to send a feature request, what to include, and what happens next.
Tell us what would make Workflow Forms better. The more specific the goal, the better.
What makes a request easy to act on
You do not need to write a spec. A sentence is fine. But if you can, include:
- The goal - what you are trying to achieve in your store, not just the feature. "I want wholesale applicants to send their trade licence" tells us more than "add a file field".
- What you do today - the workaround you are using now, if any.
- Where it fits - the editor, a field type, the theme block, popups, the inbox, Shopify Flow, the API, or somewhere else.
- How often it matters - a daily annoyance and a once-a-year edge case get weighed differently.
A concrete example of the form you are trying to build always helps.
Good things to ask for
- A field type or layout block you are missing - see Fields and the field library for what exists.
- A form template you wish existed - see Create your first form.
- A popup trigger or targeting option - see Popups.
- Something in the Shopify Flow triggers or the API and MCP - see Shopify Flow triggers and Developer API and MCP.
Already possible?
A few things people ask for that already exist:
- An email for every submission - build it as a workflow, see Shopify Flow triggers.
- Showing a field only for certain answers and forms with several steps - see Conditions and multi-step forms.
- A form without touching the theme - see Direct link page.
What happens next
- We reply to confirm we have it, usually within a couple of business days.
- Related requests are grouped, so if others have asked for the same thing, yours adds weight.
- When something you asked for ships, we note it in the changelog.
Found a bug instead?
If something is broken rather than missing, use Report a bug - bugs are triaged ahead of feature requests. For anything else, Support lists every way to reach us.
