Mechanic can now monitor Shopify jobs the same way it already monitors bulk operation queries, and return the completed JSONL results to your task using the existing event.

Bulk operation mutations are useful when you need to run the same Shopify Admin API mutation many times. Your task prepares a JSONL file where each line contains the variables for one mutation run, uploads that file to Shopify, starts the bulk mutation, and then waits for Shopify to finish processing it asynchronously.

Each result object represents the GraphQL response for one JSONL input line. This lets your task inspect which mutation runs succeeded, and which returned GraphQL errors or mutation .

This uses the same variable as bulk operation queries. If a task handles both operation types, check : for bulk operation queries, or for bulk operation mutations.

We also added task code editor snippets for common bulk operation starters:

https://learn.mechanic.dev/core/shopify/bulk-operations

Mechanic now supports custom Shopify webhooks.

This gives advanced users a new way to receive Shopify webhook events in Mechanic, with Shopify filtering deliveries before they arrive, customizing payload fields, including metafields, and routing events onto custom event topics.

This also unlocks something new for Mechanic: Shopify metaobject webhook event topics.

You can now create custom Shopify webhooks for:

Each metaobject webhook uses a filter, so you can subscribe to the exact metaobject definition your task cares about. This filter is required by Shopify.

What this is good for:

A practical example: product updates.

With a regular subscription, every enabled task listening to that topic receives every product update. If you have 20 product-update tasks, all 20 are triggered, and each task has to decide whether the update matters.

With a custom Shopify webhook, Shopify can filter first, and Mechanic can route only the matching deliveries to a purpose-specific topic, like . That gives you a cleaner one-to-one path from a Shopify event to the task or workflow that should respond.

Most Shopify-triggered tasks should still use regular subscriptions. Custom Shopify webhooks are for cases where Shopify-side filtering, payload customization, metafields, or metaobject events matter before the event reaches Mechanic.

A few gotchas:

We also cleaned up Mechanic’s Settings area, removing the old tab layout and making the growing set of settings easier to scan and navigate.

Learn more:

When preparing event webhooks to send to apps like Mechanic, Shopify uses payloads as defined by a specific version of their Webhook API.

Effective immediately, Shopify events in Mechanic now use webhook payloads from version 2026-04 of the Shopify Webhook API.

‼️ Shopify has flagged these webhook API changes as "Action Required" (source):

Mechanic now has app-wide keyboard shortcuts.

Use to toggle Ask Mechanic (our built-in AI assistant), to open the shortcuts sheet, and sequence shortcuts like to jump home.

You can also jump straight to the task library, events, settings, help, or a new task without reaching for the mouse.

Small feature, big quality-of-life upgrade.

Task exports now include each task’s unique ID.

This doesn’t change how imports work. If you import task JSON that contains an ID, Mechanic ignores it during import. The ID is included only for external record keeping, so you can reliably identify a task outside of Mechanic even if the task title changes later.

This is especially useful if you work with exported tasks in another tool and need a stable reference that isn’t tied to the task name.

Mechanic now includes a built-in AI assistant called . It's available directly inside the app, look for the ✨ button in the bottom-right corner of any page.

Ask Mechanic has access to Mechanic's complete documentation and Shopify's GraphQL Admin API schema and docs (Shopify Dev MCP), so it can answer platform questions, help you find the right task from the library, and explain how features work, all without leaving the app.

Ask Mechanic can search Mechanic's task library, pull up full task code and documentation, look up Shopify's Admin API, and validate your GraphQL queries. When it suggests a task, you can open the code directly in the task editor with one click.

Ask Mechanic is a great starting point, but if you're writing tasks in an AI coding tool like Claude or Codex, check out the full suite of AI tools for Mechanic — including the MCP server for searching docs and the task library, and Agent Skills for task-writing skillls.

You can now collect user input when running tasks from Shopify admin action links. If a task includes options, the Run tasks page will show those fields and pass values into the run as input.<name> (with still supported for compatibility). This appears when exactly one task is selected; in batch mode, the same input is applied to every selected resource.

When preparing event webhooks to send to apps like Mechanic, Shopify uses payloads as defined by a specific version of their Webhook API.

Effective immediately, Shopify events in Mechanic now use webhook payloads from version 2026-01 of the Shopify Webhook API.

‼️ Shopify has flagged these webhook API changes as "Action Required" (source):

works across positional, mapped, and GraphQL action tags. Add it inline; Mechanic moves the value into the action’s meta - no block syntax needed.

skips the follow-up mechanic/actions/perform event, this can be your event history quieter.

They can be used alongside each other.

Examples

Mechanic now supports some new OAuth-powered connections, making it easier than ever to link your favorite tools. 🚀

👉 Airtable Demo Task

👉 Slack Demo Task

For power users! Interact directly with Google Drive, Sheets, and Docs APIs — unlocking full REST API access via OAuth2.

👉 Google Demo Task

Can’t wait to see what you build! ✨