---
title: "Request a feature - Workflow Suite"
description: "Tell us what would make Workflow Suite better: a trigger, an action, a template. What to include, and what people ask for that already exists."
canonical: "https://docs.workflow-suite.app/help/request-a-feature"
---

# Request a feature

Tell us what would make Workflow Suite better. The more specific the goal, the better.

**Form: Contact**

## 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 tell my warehouse when an order with a fragile item comes in" tells us more than "add a field".
- **What you do today** - the workaround you use now, if any.
- **Where it fits** - a trigger, a step, the editor, the run history, the API, or somewhere else.
- **How often it matters** - a daily annoyance and a once-a-year edge case are weighed differently.

A concrete example of the workflow you are trying to build always helps.

## Good things to ask for

- A **template** you wish existed. See what is there in [Start from a template](https://docs.workflow-suite.app/start-from-a-template.md).
- A **ready-made action** with a simple form for something you now do with a raw mutation. See [Ready-made Shopify actions](https://docs.workflow-suite.app/shopify-actions.md).
- A **trigger** for a change you cannot react to yet. See [Choosing a trigger](https://docs.workflow-suite.app/choosing-a-trigger.md).
- A rough edge in the **editor**, **testing** or the **run history**.
- Anything in the **API or MCP** surface. See [Developer API and MCP](https://docs.workflow-suite.app/developer-api-and-mcp.md).

## Already possible?

A few things people ask for that already exist:

- **Doing something Shopify offers but the app has no form for** - every mutation and every query of the Shopify Admin API can be picked from a list. See [Every Shopify mutation and query](https://docs.workflow-suite.app/shopify-mutations-and-queries.md).
- **Reacting only when one field changed, with the old and the new value** - see [Change triggers with before and after values](https://docs.workflow-suite.app/change-triggers.md).
- **Calling another system, or being called by one** - see [HTTP request](https://docs.workflow-suite.app/http-request.md) and [Incoming webhooks](https://docs.workflow-suite.app/incoming-webhooks.md).
- **Exchanging files over SFTP** - see [Files, SFTP and downloads](https://docs.workflow-suite.app/files-sftp-and-downloads.md).
- **Logic that is too special for steps** - write it in JavaScript or Liquid. See [Run code and functions](https://docs.workflow-suite.app/run-code.md) and [Liquid script step](https://docs.workflow-suite.app/liquid-step.md).
- **Going over your plan's runs without upgrading** - see [Plans, runs and extra runs](https://docs.workflow-suite.app/plans-runs-and-extra-runs.md).

## Known limits we are aware of

You do not need to report these, but tell us if one of them blocks you, because that helps us weigh them:

- Sending email from a Google or Microsoft 365 mailbox is not available yet. SMTP works.
- Code steps cannot reach Files or SFTP.
- Uploads through the Files page and the API are capped at 3.5 MB.

## 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.

## Found a bug instead?

If something is broken rather than missing, use [Report a bug](https://docs.workflow-suite.app/help/report-a-bug.md). Bugs are looked at before feature requests. For anything else, [Support](https://docs.workflow-suite.app/help/support.md) lists every way to reach us.