Frequently asked questions

A workflow is one trigger plus steps. A run is one execution of it for one event. Plans count runs, not steps: a run with sixty steps is one run. See How a workflow runs: triggers, steps and runs.

No. Test, Test this step and debug sessions are free, also when you choose Run for real. Events a trigger filter rejects and runs that were not started are free too. Run now, Run again, scheduled runs and real runs over the API count. See Plans, runs and extra runs.

Yes. In a preview, conditions and reads run for real: Shopify queries, reads from the key-value store, listing and downloading from a server. Every step that would change something only reports what it would do: Shopify actions and mutations, HTTP requests, emails, chat messages, code, writes and uploads. Choose Run for real when you want the changes. See Test, preview and debug.

Orders, customers, draft orders, checkouts, fulfillments and companies are protected customer data. Shopify delivers those events only to an app it has approved for that data, on top of the permission you grant in the app. Product, inventory, discount and content workflows are not affected. See Permissions and store data access and contact Support.

A change trigger compares an event with what the app saw before. The first time it sees a resource, it only remembers it. When you turn the workflow on, the app reads your existing data in the background so that the next change counts; until that has reached a resource, its first change only sets the starting point. See Change triggers with before and after values.

Loop protection works against it in three ways: it recognises the echo of a workflow's own change within about 30 seconds, it ends chains of workflows that trigger each other after 5, and it turns off a workflow that starts more than 10 times in 60 seconds for the same resource. The first layer works with a time window, not with proof, so build workflows that do not loop in the first place. See Loop protection.

The app turns a workflow off itself when it started more than 10 times within 60 seconds for the same resource. You get an alert, and the editor shows the reason. Fix the cause, usually with a trigger filter, and select Turn on. See Loop protection.

Any mail server or email service with SMTP. Sending from a Google or Microsoft 365 mailbox is not available yet. Workflow emails always go out through your own sender, never through a shared relay. See Send email and email senders.

They are best effort. They are reported by the shopper's browser, only with the visitor's analytics consent, and an ad blocker or a closed tab drops an event without a trace. Use them for signals and counters, not for anything that must happen for every shopper. See Storefront behaviour triggers.

No. Code steps cannot reach Files or SFTP. Use the Files, Download file and File transfer steps, and hand their text results to the code through the step results. See Files, SFTP and downloads and Run code and functions.

The largest file depends on your plan: 5 MB on Free, up to 50 MB on Unlimited. Uploads through the Files page and the Developer API are capped at 3.5 MB per file; larger files arrive through the Download file and File transfer steps. All attachments of one email together can be 10 MB. See Files, SFTP and downloads.

A Shopify query step reads one page of results, and the templates for whole-store jobs read one page per run. They are built so that the next run finds what is left. Let the job run more often, or raise the page size within the limits of Repeat for each. See Recipe: nightly cleanup with Repeat for each.

Some mutations need a permission Shopify does not let this app ask for, or only hands out on application, for example subscription contracts and taxes. The step's docs box says so, and the step would fail when it runs. See Every Shopify mutation and query.

Yes, when the failure is temporary and repeating the step cannot apply something twice: a busy server, a throttled Shopify call, a connection that was never made. A POST that may have arrived, code that ran and failed, and validation errors are not repeated. See Automatic retries.

Save them on the Secrets page and use them by name. Values are encrypted, cannot be read back, and are masked in run results. Never type a password into a step, and never send us a secret's value. See Secrets.

No. Billed extra runs are turned on and capped in the app only, on the Home page, by a person. The API shows the current setting. See Plans, runs and extra runs.

Yes. The app has an MCP server. With a read & write key an assistant can look up triggers and actions, draft a workflow, validate it and simulate it as a preview. Granting permissions and reading secrets stay with you. See Build workflows with an AI assistant over MCP.

In the European Union, on Google Cloud in the region europe-west1 (Belgium). Run data and secrets are stored encrypted. Run history is kept for 30 to 180 days, depending on your plan. See Data, privacy and hosting.

Everyone with access to the app in your Shopify admin can see and edit every workflow, function and permission. Nobody can read a secret's stored value. Shopify's staff permissions decide who has access to the app.