---
title: "Request a feature - Workflow Functions"
description: "Tell us what would make Workflow Functions better. How to send a feature request, what to include, and what happens next."
canonical: "https://docs.workflow-functions.app/help/request-a-feature"
---

# Request a feature

**Form: Send a feature request**
Tell us what would make Workflow Functions better. The more specific the goal, the better.
- Your email (email, required)
- Store URL (text)
- Area (select)
- What would you like to see? (textarea, required)
- OK to email me a follow-up (checkbox)

Workflow Functions is shaped by what merchants and developers actually need. If something is missing, awkward, or would save you time, we want to hear it. Use the form above, or reach us another way below.

## Prefer another channel?

- **In-app chat** - open any page of Workflow Functions in your Shopify admin and use the chat bubble in the corner. This is the fastest route and keeps your request tied to your store.
- **Email** - write to us with your idea. Include your store URL so we can follow up.

We read every request.

## 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 to notify my warehouse when a high-value order comes in" tells us more than "add a webhook option".
- **What you do today** - the workaround you are using now, if any.
- **Where it fits** - the Flow trigger, the editor, permissions, secrets, the API, or somewhere else.
- **How often it matters** - a daily annoyance and a once-a-year edge case get weighed differently.

Screenshots and short examples always help.

## Good things to ask for

- A **template** you wish existed. If you have written a function others would use, you can also publish it yourself - see [Using templates](https://docs.workflow-functions.app/using-templates.md).
- A **Shopify resource or field** you need to read or write that is not available yet - see [Permissions and store data access](https://docs.workflow-functions.app/permissions-and-store-data-access.md).
- A rough edge in the **editor**, **testing**, or **run history** - see [How to create a function](https://docs.workflow-functions.app/how-to-create-a-function.md) and [Run history and troubleshooting](https://docs.workflow-functions.app/run-history-and-troubleshooting.md).
- Anything in the **API or MCP** surface for automating your functions - see [Developer API and MCP](https://docs.workflow-functions.app/developer-api-and-mcp.md).

## 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 and, when it is significant, on the blog.

## Found a bug instead?

If something is broken rather than missing, send it the same way and include the function, the run (from [Run history and troubleshooting](https://docs.workflow-functions.app/run-history-and-troubleshooting.md)), and what you expected to happen. Bugs jump the queue.

## Next steps

- [Introduction to Workflow Functions](https://docs.workflow-functions.app/introduction-to-workflow-functions.md) - what the app can already do.
- [How to create a function](https://docs.workflow-functions.app/how-to-create-a-function.md) - build your first function.