Changelog

Latest updates and improvements.

Admin API 2027-01 release candidate per workflow, 2026-10 catalogs updated

Shopify's Admin API 2027-01 release candidate in the step picker, and the 2026-10 mutations and queries brought up to date.

Shopify API

  • Admin API 2027-01 (release candidate) can be chosen per workflow. Under Shopify Admin API version a workflow can now name 2027-01 for its Admin API (GraphQL) and Liquid script steps, next to 2026-10 (the default) and 2026-07. The pickers then list that version's 530 mutations and 296 queries. Shopify can still change a release candidate until it is released on 2027-01-01; the label (release candidate) disappears on that day. Ready-made actions, code steps and triggers keep running on 2026-10. See Every Shopify mutation and query.
  • New in 2027-01: the mutations appDowngradeAccessScopes and identityProviderSubjectDelete and the query analyticsSchemas. Removed in 2027-01: the automaticDiscounts query (use discountNodes with the filter method:automatic) and the marketCurrencySettingsUpdate mutation (use marketCreate and marketUpdate). A workflow on 2027-01 that still uses one of them cannot be turned on, and the docs box says Removed after 2026-10.
  • The 2026-10 mutations and queries match Shopify's documentation of today: new search filters (for example created_at on productVariants, markets and rollouts), the order and fulfillment operations also accept the buyer membership orders permission, new examples, and marketingEngagementsDelete is marked deprecated.

Ask Sidekick from the setup guide and from failed runs

Improved

  • Ask Sidekick from the setup guide. Every step of the setup guide on the dashboard has an Ask Sidekick button. It opens Shopify's assistant with a ready question about that step, for example how to create your first workflow or grant a permission, in the language of your admin. The button shows wherever Sidekick is available in your admin.
  • Ask Sidekick why a run failed. A failed workflow run shows Ask Sidekick why this failed. Sidekick looks the run up by its id and explains which step failed and how to fix it.

Workflow Suite 1.3.0

A storefront trigger for the shipping step of the checkout, with two templates.

New

  • Checkout shipping selected. Starts when a shopper has chosen a shipping method, before payment. The event carries the shipping total, the number of shipments the order would go out in, shipping as a percentage of the merchandise subtotal, the order total, the number of items and the selected delivery option per shipment (title, type, description, cost and cost after discounts). No contact details; a signed-in shopper's customer id, as with the other storefront triggers. Best effort and consent-gated like every storefront trigger. See Storefront behaviour triggers.
  • Two templates in Storefront behaviour: Notice checkouts that split into several shipments (3 or more) and Notice checkouts with unusually high shipping (20 percent or more of the goods). Both keep the threshold in the trigger filter, so a checkout below it starts nothing and costs nothing. See Start from a template.

Workflow Suite 1.2.0

Sidekick, signed incoming webhooks, and a round of fixes.

New

  • Ask Sidekick about your workflows. Shopify's assistant can look up which workflows are on, the steps and open problems of a workflow, runs by status and date and the steps of one run, run numbers, the triggers, steps and templates the app offers, and the granted permissions. Read-only; event data and step results are never passed on.
  • Signature check for incoming webhooks. The Incoming webhook trigger can ask for an HMAC-SHA256 signature of the request body, made with a secret from the Secrets page (hex, sha256=<hex> or base64, in a header you name). A request without a valid signature is answered with 401 and starts nothing. See Incoming webhooks.

Fixed

  • Inventory, refund, location and transfer mutations picked in the Shopify Admin API step work. Shopify refuses these 16 mutations without an idempotency key; the step now carries one per run and step, so a retry is applied once. The stock function templates and the AI generator follow the same rule. See Every Shopify mutation and query.
  • Run again uses the event exactly as it was, with its before and after values.
  • After Turn on, the editor says what is missing: the permission banner shows again, and a new warning appears when Shopify does not send the events of the workflow's trigger.
  • The test input follows a changed trigger; the dashboard's date button shows the range that was picked; the debugger leads with the outcome and the last step results when a session ends.
  • "Unsaved changes" no longer stays up for a name with a trailing space, an empty function test input or a schedule typed while the schedule is off.
  • Help page: the break-even between extra runs and the Unlimited plan was wrong (it is about 73,000 extra runs on Starter and 53,000 on Grow); run limits read "per 30 days".

Changed

  • Run now asks first: it starts a real run with the trigger's sample event.
  • Incoming webhook URLs are shown on shopify.workflow-suite.app. URLs handed out before keep working.
  • In Shopify Flow, write the Data of "Run a Workflow Suite workflow" with Flow's json filter: a variable inside plain quotes breaks on a value that holds a double quote. See Start a workflow from Shopify Flow.

Developer API and MCP

  • Function run payloads come back PII-masked, like workflow run payloads.
  • CANCELLED is a valid run status filter; the trigger list leaves out triggers that cannot be used and carries verified; list_triggers accepts the sources waiting and workflow; a test email takes one slot of the execute budget. See Developer API and MCP.

Workflow Suite 1.1.1

Fixed

  • The editor no longer says "Unsaved changes" after a save. With some steps (for example a Slack message) the bar stayed up although the workflow was saved, and Turn on kept saving again.
  • The function editor shows one tab at a time again, and the step picker one view.

Permissions

  • The script tag permission and the script tag operations in the step picker are gone: Shopify no longer accepts new script tags and stops running them in March 2027.

Workflow Suite 1.1.0

Shopify's Admin API 2026-10, Rollout triggers and several barcodes per variant.

Shopify API

  • Admin API 2026-10 is the default. Workflows, ready-made actions, code steps and triggers run on Shopify's October 2026 version. A workflow can still name 2026-07 for its Admin API and Liquid steps. See Every Shopify mutation and query.
  • The mutations and queries of 2026-10 in the step picker, among them the new Rollout queries.
  • Worth knowing on 2026-10: a search that filters by a metafield which is not set up for filtering fails with an error instead of being ignored; changing the shipping address of an unfulfilled order recalculates its taxes; an order with nothing left to fulfill reports FULFILLMENT_NOT_REQUIRED instead of UNFULFILLED.

Triggers

  • Rollouts (6): a Rollout created, updated or deleted, and a change added to, updated in or removed from a Rollout. Needs the new Rollouts permission.
  • Requested order edits (3): a customer asks for a change to an order, and the request is resolved or declined.
  • Product variant barcode changed also starts when one of several barcodes of a variant is added, changed or removed, and carries the whole list before and after. See Change triggers with before and after values.
  • New fields in Shopify's events: the selling plan of an order line, the transfer of an inventory shipment, the request time of a return, the barcodes of a variant.

Permissions

Functions

  • The ERP templates for creating and updating products, looking up variants and exporting orders accept and return a variant's list of barcodes.

Workflow Suite 1.0.0

Workflow Suite is here: events in, a visual editor, steps out. Build automations for your Shopify store on a canvas, with real code where you need it, and see exactly why every run happened.

New here? Start with Introduction to Workflow Suite and Build your first workflow, or pick one of the 161 templates: Start from a template.

296 triggers

  • Shopify events for products, variants, collections, orders, draft orders, customers, companies, discounts, inventory, fulfillment, content, markets, locations and more. See Shopify events.
  • Change triggers with before and after values. Tags added or removed, price, status, title, vendor, SKU, note, line items, fulfillment and financial status, addresses, out of stock and back in stock, unit cost. The event carries the old value, the new value and the difference, so a rule can say "price decreased" or "tag VIP added". See Change triggers with before and after values.
  • Metafield and metaobject triggers: a watched metafield changed on products, variants, orders, customers, collections, companies, blogs, articles and pages; metaobject entries created, updated or deleted, or one field changed. See Metafield and metaobject triggers.
  • Storefront behaviour: product viewed, added to cart, search, checkout started, custom events, left without purchase. Collected in the shopper's browser with analytics consent, best effort. See Storefront behaviour triggers and Abandoned checkout and left without purchase.
  • Schedules with presets or cron, incoming webhooks with a secret URL, manual runs and workflows started by another workflow. See Schedules, Incoming webhooks and Manual runs and workflows started by another workflow.
  • Filter any trigger before a run starts: Trigger filters.

A visual editor with real code

Steps

Shopify Flow in both directions

  • Send to Shopify Flow: a step that starts your Shopify Flow workflows with an event name and data of your choice, through the Flow trigger Workflow Suite event. See Send events to Shopify Flow.
  • Run a Workflow Suite workflow: a Shopify Flow action that starts one of your workflows from any Flow trigger, with data from the Flow workflow. See Start a workflow from Shopify Flow.

Reliability

Recipes and tutorials

Recipe: tag high-value orders, Recipe: low stock alert to Slack, Recipe: back in stock, publish again, Recipe: abandoned checkout follow-up, Recipe: send new orders to an ERP, Recipe: email a daily file from SFTP, Recipe: let another system set stock by SKU, and step-by-step tutorials such as Tutorial: tag high-value orders and tell Slack, Tutorial: react to a price drop with a before-and-after rule and Tutorial: debug a workflow step by step.

For developers

Everything the app does is available over the REST API and the MCP server with scoped keys (read, write, execute): workflows, runs, simulate and validate, the trigger and action catalogs, key-value store, files, secrets, email senders and alerts. Build workflows with an AI assistant over MCP. See Developer API and MCP and Build workflows with an AI assistant over MCP.

Permissions and plans

Store data access is granted per resource on the Permissions page and can be revoked at any time. See Permissions and store data access. Plans: Free, Starter, Grow and Unlimited. The unit is the workflow run; test runs, filtered and suppressed runs are free. See Plans, runs and extra runs.