diff --git a/SUMMARY.md b/SUMMARY.md index 9c7bd42..f1e933b 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -68,6 +68,7 @@ * [Events](core/events/README.md) * [Topics](core/events/topics.md) + * [Event topics list](platform/events/topics.md) * [Parent and child events](core/events/parent-and-child-events.md) * [Tasks](core/tasks/README.md) * [Subscriptions](core/tasks/subscriptions.md) diff --git a/core/actions/email.md b/core/actions/email.md index c309f28..a45a5a6 100644 --- a/core/actions/email.md +++ b/core/actions/email.md @@ -163,3 +163,9 @@ For more on this, see [File generators](file-generators/). {% endtab %} {% endtabs %} + +## Related + +* [Email](../../platform/email/) — email platform features, including custom domains, DMARC, and receiving inbound email +* [Email templates](../../platform/email/templates.md) — reusable email layouts and styling +* [File generators](file-generators/) — generate PDFs, CSVs, and other attachments for your emails diff --git a/core/actions/file-generators/README.md b/core/actions/file-generators/README.md index 3d60604..4a6a539 100644 --- a/core/actions/file-generators/README.md +++ b/core/actions/file-generators/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Generate files from Mechanic tasks — PDF, CSV, ZIP, plaintext, and base64 formats for attachments and downloads. +--- + # File generators **File generators** are invoked by [**actions**](../) to create new files, using options provided by the action, and handing the resulting file back to the action for further use. In this way, [**tasks**](../../tasks/) can make choices about what files to generate, and what to do with the results. diff --git a/core/actions/http.md b/core/actions/http.md index e76783f..721fb80 100644 --- a/core/actions/http.md +++ b/core/actions/http.md @@ -165,3 +165,9 @@ mechanic/actions/perform response_body: action.run.result.body %} {% endif %} ``` + +## Related + +* [Working with external APIs](../../techniques/working-with-external-apis/) — patterns for authenticating and integrating with third-party services +* [Responding to action results](../../techniques/responding-to-action-results.md) — inspect HTTP responses and react to them in a follow-up task run +* [Preventing action loops](../../techniques/preventing-action-loops.md) — guard against re-triggers when combining HTTP actions with event subscriptions diff --git a/core/actions/integrations/README.md b/core/actions/integrations/README.md index d9d3289..cb5a93c 100644 --- a/core/actions/integrations/README.md +++ b/core/actions/integrations/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Connect Mechanic tasks to third-party services — Airtable, Google Sheets, Slack, Shopify Flow, and more. +--- + # Integrations These actions allow your Mechanic tasks to speak to other app and systems :) Use Mechanic to integrate your Shopify store with other apps like Airtable, Google, Slack, and more. diff --git a/core/actions/shopify.md b/core/actions/shopify.md index a88eb20..28c6ff5 100644 --- a/core/actions/shopify.md +++ b/core/actions/shopify.md @@ -141,3 +141,10 @@ This example shows how the query and variables may be built up separately, and p {% endtab %} {% endtabs %} + +## Related + +* [Reading Shopify data](../shopify/read/) — query products, orders, customers, and more using GraphQL in Liquid +* [Writing Shopify data](../shopify/write.md) — overview of writing data to Shopify +* [Responding to action results](../../techniques/responding-to-action-results.md) — inspect Shopify mutation results in a follow-up task run +* [Preventing action loops](../../techniques/preventing-action-loops.md) — guard against re-triggers when modifying resources you subscribe to diff --git a/core/events/README.md b/core/events/README.md index c2910b1..fa6b5bf 100644 --- a/core/events/README.md +++ b/core/events/README.md @@ -21,6 +21,12 @@ Each event carries **data** that tasks can use. For a Shopify webhook event, thi For a complete reference of available event topics, see [Topics](topics.md). +## What happens next + +When an event arrives, Mechanic creates a [**run**](../runs/) to process it. Each run evaluates every [task](../tasks/) that subscribes to that event's topic. If a task generates [actions](../actions/) (like a Shopify API call or an email), those actions are queued and performed after the task run completes. + +This is the core execution flow: **Event** → **Task Run** → **Action Run(s)**. To learn more, see [Runs](../runs/). + {% hint style="info" %} Incoming events may be selectively skipped using [event filters](../../platform/events/filters.md). For handling high-frequency events, see [Debouncing events](../../techniques/debouncing-events.md). {% endhint %} diff --git a/core/shopify/admin-action-links.md b/core/shopify/admin-action-links.md index 89f7b72..a777f85 100644 --- a/core/shopify/admin-action-links.md +++ b/core/shopify/admin-action-links.md @@ -9,7 +9,7 @@ description: >- For supported resources, you'll find **"Send to Mechanic"** links within the Shopify admin. These links point to a Mechanic app URL that translates selected Shopify resources into Mechanic events for on-demand processing. Depending on the user's resource and task selections, their submission may result in one or more new events. Event data consists of the latest stable REST Admin API representation of the selected resource(s). {% hint style="warning" %} -**Important**: Starting **Feb 1, 2025**, the `product` and `variant` resource types will no longer include full REST Admin API data in these events. Instead, only resource IDs (`id` and `admin_graphql_api_id`) will be included, due to Shopify REST API deprecations. If you need additional product or variant details (e.g. title, vendor, etc.), you must fetch them via Shopify's GraphQL API. +**Important**: As of **Feb 1, 2025**, the `product` and `variant` resource types no longer include full REST Admin API data in these events. Only resource IDs (`id` and `admin_graphql_api_id`) are included, due to Shopify REST API deprecations. If you need additional product or variant details (e.g. title, vendor, etc.), fetch them via Shopify's GraphQL API. {% endhint %} Tasks can qualify for this style of on-demand Shopify resource processing by subscribing to event topics like **mechanic/user/{resource}** (singular) for individual processing, and **mechanic/user/{resources}** (plural) for batch processing. See [Supported resources](admin-action-links.md#supported-resources) below for a complete table of resources and event topics. @@ -21,7 +21,7 @@ Shopify admin action links are a form of [**run link**](../../platform/integrati
Resource objectURL parameterIndividual mode event topicBatch mode event topic
Customercustomermechanic/user/customermechanic/user/customers
Orderordermechanic/user/ordermechanic/user/orders
Draft orderdraft_ordermechanic/user/draft_ordermechanic/user/draft_orders
Productproductmechanic/user/productmechanic/user/products
Product variantvariantmechanic/user/variantmechanic/user/variants
Collectioncollectionmechanic/user/collection
{% hint style="warning" %} -**Note**: After **Feb 1, 2025**, `product` and `variant` events will only include resource IDs: +**Note**: As of **Feb 1, 2025**, `product` and `variant` events only include resource IDs: ``` { diff --git a/core/shopify/events/README.md b/core/shopify/events/README.md index e7278c0..6274fda 100644 --- a/core/shopify/events/README.md +++ b/core/shopify/events/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Respond to Shopify webhooks in Mechanic — subscribe to store activity and handle changes to orders, products, customers, and more. +--- + # Responding to events Shopify uses webhooks to notify apps like Mechanic about new activity. Mechanic supports every type of Shopify webhook in its set of [**Shopify event topics**](../../../platform/events/topics.md#shopify). By setting up [**subscriptions**](../../tasks/subscriptions.md) to these topics, a task may respond to any supported type of Shopify activity. diff --git a/core/shopify/read/README.md b/core/shopify/read/README.md index 09fbcec..5708242 100644 --- a/core/shopify/read/README.md +++ b/core/shopify/read/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Read Shopify store data in Mechanic tasks — GraphQL queries, bulk operations, and the shopify Liquid filter. +--- + # Reading data Mechanic supports several methods of reading data. The following articles discuss usage, and when each technique might \(or might not\) be appropriate: diff --git a/core/shopify/read/liquid-objects.md b/core/shopify/read/liquid-objects.md index 1818f7e..a8b46a8 100644 --- a/core/shopify/read/liquid-objects.md +++ b/core/shopify/read/liquid-objects.md @@ -3,9 +3,9 @@ Mechanic-flavored Liquid comes with a complement of [Liquid objects](../../../platform/liquid/objects/), each of which is tied to a resource in the [Shopify Admin REST API](https://shopify.dev/docs/admin-api/rest). Many objects support access to related objects via lookups (e.g. `{{ shop.customers[customer_id].orders.first }}`); in this way, the REST API can be traversed by resource. {% hint style="danger" %} -**Shopify is deprecating some of the Shopify Admin REST API. The first round of deprecations involve the product and variant endpoints. Read the deprecation notice** [**here**](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing)**.** +**Shopify has deprecated the REST Admin API that these Liquid objects depend on.** The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read more [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing). -Our recommendation is to use [GraphQL](../../actions/shopify.md#graphql) going forward. The [product](../../../platform/liquid/objects/shopify/product.md) and [variant](../../../platform/liquid/objects/shopify/variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. It appears that Shopify will gradually phase out the REST API over time. +Use [GraphQL](../../actions/shopify.md#graphql) going forward. The [product](../../../platform/liquid/objects/shopify/product.md) and [variant](../../../platform/liquid/objects/shopify/variant.md) objects no longer work. The remaining REST objects will follow as Shopify continues the migration. All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed: {% endhint %} diff --git a/core/tasks/advanced-settings/README.md b/core/tasks/advanced-settings/README.md index f39414f..8319926 100644 --- a/core/tasks/advanced-settings/README.md +++ b/core/tasks/advanced-settings/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Per-task configuration beyond code and options — documentation, JavaScript, and action sequencing. +--- + # Advanced settings Advanced settings are per-task configuration options beyond the task's code and user-facing options. They control how the task is documented, how its code is executed, and how its actions are performed. diff --git a/core/tasks/code/README.md b/core/tasks/code/README.md index 6ca0e98..fd6a6ae 100644 --- a/core/tasks/code/README.md +++ b/core/tasks/code/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Write task code in Mechanic's Liquid environment — render actions, logs, and errors in response to events. +--- + # Code A task's code is a [**Liquid**](../../../platform/liquid/) template. In the same way that a Shopify storefront might use a Liquid template to receive requests and render HTML, a task uses its Liquid code to receive events, and render a series of JSON objects. These JSON objects define [**actions**](action-objects.md), [**logs**](log-objects.md), and [**errors**](error-objects.md). @@ -17,3 +22,11 @@ A task must purposefully consider its [**preview**](../previews/), so as to accu {% hint style="info" %} To find many examples of task code, browse [https://github.com/lightward/mechanic-tasks](https://github.com/lightward/mechanic-tasks). {% endhint %} + +## See also + +* [Liquid basics](../../../platform/liquid/basics/) — syntax, data types, variables, filters, and control flow +* [Mechanic filters](../../../platform/liquid/filters/) — Mechanic-specific filters for data manipulation +* [Mechanic tags](../../../platform/liquid/tags/) — `{% raw %}{% action %}{% endraw %}`, `{% raw %}{% log %}{% endraw %}`, `{% raw %}{% error %}{% endraw %}`, and more +* [Mechanic objects](../../../platform/liquid/objects/) — event, task, options, cache, and action objects available in your code +* [Writing a high-quality task](../../../techniques/writing-a-high-quality-task.md) — patterns and practices for reliable Mechanic tasks diff --git a/core/tasks/import-and-export.md b/core/tasks/import-and-export.md index b28bd30..16b38d3 100644 --- a/core/tasks/import-and-export.md +++ b/core/tasks/import-and-export.md @@ -1,3 +1,8 @@ +--- +description: >- + Share and back up Mechanic tasks as JSON — import individually or in bulk, and contribute to the task library. +--- + # Import and export Mechanic tasks may be imported and exported as JSON, using the "Import" or "Export" button below the task editor. The JSON schema used for representing tasks is identical to that used by the **task library**, making it suitable for [contributing to the task library](../../resources/task-library/contributing.md). diff --git a/core/tasks/options/README.md b/core/tasks/options/README.md index ebb57a2..f3661bc 100644 --- a/core/tasks/options/README.md +++ b/core/tasks/options/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Add user-facing configuration to your Mechanic tasks — input fields, validation flags, and custom option types. +--- + # Options [**Tasks**](../) can accept user configuration via **options**. Options are created automatically: when you reference `options.something` in your task's [**code**](../code/), Mechanic adds an input field for it in the task configuration UI. diff --git a/core/tasks/permissions.md b/core/tasks/permissions.md index 03e3e90..8c355de 100644 --- a/core/tasks/permissions.md +++ b/core/tasks/permissions.md @@ -1,3 +1,8 @@ +--- +description: >- + How Mechanic determines Shopify API access scopes from your task code — automatic detection and explicit declarations. +--- + # Permissions Mechanic determines Shopify API access scopes (like `read_orders` or `write_products`) from your task code. It can infer scopes from several places, including subscriptions, Shopify data access in task code, and actions rendered during preview. When your shop needs additional access, Mechanic will surface that in the app. diff --git a/core/tasks/previews/README.md b/core/tasks/previews/README.md index 2d0ba94..b4deb79 100644 --- a/core/tasks/previews/README.md +++ b/core/tasks/previews/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Test Mechanic tasks safely before they run on real data — preview actions, request Shopify permissions, and define sample events. +--- + # Previews A task uses its **preview** to demonstrate what actions the task intends to generate. Among other purposes (see below), this is also how tasks request the Shopify permissions they require. diff --git a/core/tasks/user-form.md b/core/tasks/user-form.md index 851696c..5bcdd1e 100644 --- a/core/tasks/user-form.md +++ b/core/tasks/user-form.md @@ -1,3 +1,8 @@ +--- +description: >- + Create custom input forms for manually-triggered Mechanic tasks — collect user input and pass it to your task code. +--- + # User Form When a task subscribes to the **mechanic/user/form** event topic a "Run task" button is added to the task. diff --git a/platform/cache/README.md b/platform/cache/README.md index 6b4ddce..6a756ea 100644 --- a/platform/cache/README.md +++ b/platform/cache/README.md @@ -18,4 +18,12 @@ The cache is intended for temporary data storage. As such, each stored value is The cache is not intended for large value storage. As such, each stored value is limited to a maximum of 256kb. -For storing larger values, consider spreading the value across multiple cache keys, or using the [FTP](../../core/actions/ftp.md) action to upload data to another storage service (possibly using a service like [Couchdrop](https://couchdrop.io/) as a intermediary). To read larger values in task code, use the [HTTP](../../core/actions/http.md) action to perform a GET request, then [respond to the action's results](../../techniques/responding-to-action-results.md).\ +For storing larger values, consider spreading the value across multiple cache keys, or using the [FTP](../../core/actions/ftp.md) action to upload data to another storage service (possibly using a service like [Couchdrop](https://couchdrop.io/) as a intermediary). To read larger values in task code, use the [HTTP](../../core/actions/http.md) action to perform a GET request, then [respond to the action's results](../../techniques/responding-to-action-results.md). + +## Common patterns + +The cache is a versatile tool — here are some of the ways it's commonly used: + +* [Debouncing events](../../techniques/debouncing-events.md) — use the cache to skip duplicate events that arrive in rapid succession +* [Batch processing of events](../../techniques/batch-processing-of-events.md) — accumulate data in the cache across multiple events, then process it all at once on a schedule +* [Responding to action results](../../techniques/responding-to-action-results.md) — store state across the multiple task runs in a multi-step workflow diff --git a/platform/email/README.md b/platform/email/README.md index 7b6bc6b..c80339c 100644 --- a/platform/email/README.md +++ b/platform/email/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Send automated emails from Mechanic — templates, custom domains, DMARC, and receiving inbound email. +--- + # Email Mechanic email is powered by [Postmark](https://postmarkapp.com/). diff --git a/platform/events/README.md b/platform/events/README.md index d0ff6a3..bacc79d 100644 --- a/platform/events/README.md +++ b/platform/events/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Mechanic event sources, topics, and filters — Shopify webhooks, scheduled events, custom triggers, and more. +--- + # Events In Mechanic, an [event](../../core/events/) represents something that happened — a new order, a scheduled timer firing, an incoming email, or a custom trigger. Events are the starting point for all automation: every task run begins with an event. diff --git a/platform/graphql/basics/README.md b/platform/graphql/basics/README.md index 972b9f3..08b2bfc 100644 --- a/platform/graphql/basics/README.md +++ b/platform/graphql/basics/README.md @@ -1,3 +1,8 @@ +--- +description: >- + GraphQL fundamentals for Mechanic — queries, mutations, pagination, and the Shopify Admin API. +--- + # Basics GraphQL is a query language used to request data from APIs and it is also a runtime for fulfilling these requests. When working with GraphQL, you'll use [queries](queries.md) and [mutations](mutations.md) to query a GraphQL serve and responses will come back in JSON format. GraphQL is the future of Shopify APIs, and Shopify has said: "You should expect that there absolutely will be more features that will be only on GraphQL in the future." diff --git a/platform/liquid/basics/README.md b/platform/liquid/basics/README.md index 38afe1b..e4ddeab 100644 --- a/platform/liquid/basics/README.md +++ b/platform/liquid/basics/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Learn the fundamentals of Liquid in Mechanic — syntax, data types, variables, filters, operators, and control flow. +--- + # Basics Mechanic uses [**Liquid**](../), a template language created by Shopify. If you have worked with the code behind Shopify themes, you've worked with Liquid. diff --git a/platform/liquid/basics/control-flow/README.md b/platform/liquid/basics/control-flow/README.md index b9c0765..e70a99a 100644 --- a/platform/liquid/basics/control-flow/README.md +++ b/platform/liquid/basics/control-flow/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Control flow in Liquid — conditionals and iteration for directing task logic in Mechanic. +--- + # Control flow In Liquid, **control flow** determines what code is evaluated. By using control flow tags, developers can use logic to activate different parts of code, and skip over other parts. diff --git a/platform/liquid/filters/README.md b/platform/liquid/filters/README.md index ae92854..1d0c49a 100644 --- a/platform/liquid/filters/README.md +++ b/platform/liquid/filters/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Complete reference of Liquid filters available in Mechanic — shopify, parse_json, csv, hmac_sha256, and more. +--- + # Mechanic filters This page defines all of the [**Liquid filters**](../basics/filters.md) that are available in Mechanic Liquid. Mechanic supports many of our own filters, as well as an array of filters drawn from Shopify Liquid. diff --git a/platform/liquid/keyword-literals/README.md b/platform/liquid/keyword-literals/README.md index c523410..552390a 100644 --- a/platform/liquid/keyword-literals/README.md +++ b/platform/liquid/keyword-literals/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Mechanic's keyword literals for Liquid — array, hash, and newline for working with data structures and formatting. +--- + # Keyword literals Mechanic adds several keyword literals to Liquid — special values that can be used directly in expressions without needing to be assigned or constructed. These make it easier to work with common data structures and formatting. diff --git a/platform/liquid/objects/README.md b/platform/liquid/objects/README.md index 0923ff2..13a9a70 100644 --- a/platform/liquid/objects/README.md +++ b/platform/liquid/objects/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Mechanic's Liquid objects — event, task, options, cache, action, and Shopify resource objects available in your task code. +--- + # Mechanic objects Mechanic makes a variety of [**Liquid environment variables**](../../../core/tasks/code/environment-variables.md) available, containing specific Liquid objects. (The `shop` variable, for example, is always available and always contains the [Shop object](shopify/shop.md).) diff --git a/platform/liquid/objects/shopify/README.md b/platform/liquid/objects/shopify/README.md index 62e1ac8..2ef3e17 100644 --- a/platform/liquid/objects/shopify/README.md +++ b/platform/liquid/objects/shopify/README.md @@ -3,10 +3,9 @@ {% hint style="danger" %} **Important Notice** -\ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ -\ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read more [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate). + +Use [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects no longer work. The remaining REST objects will follow as Shopify continues the migration. \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/article.md b/platform/liquid/objects/shopify/article.md index 5a49bf2..9740b60 100644 --- a/platform/liquid/objects/shopify/article.md +++ b/platform/liquid/objects/shopify/article.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/blog.md b/platform/liquid/objects/shopify/blog.md index ecad8cb..fbc10bd 100644 --- a/platform/liquid/objects/shopify/blog.md +++ b/platform/liquid/objects/shopify/blog.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API competely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/collection.md b/platform/liquid/objects/shopify/collection.md index ef4d213..9ec4162 100644 --- a/platform/liquid/objects/shopify/collection.md +++ b/platform/liquid/objects/shopify/collection.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/customer-object.md b/platform/liquid/objects/shopify/customer-object.md index 7af066e..b7096d1 100644 --- a/platform/liquid/objects/shopify/customer-object.md +++ b/platform/liquid/objects/shopify/customer-object.md @@ -3,9 +3,9 @@ {% hint style="danger" %} **Important Notice** -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate). -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed: diff --git a/platform/liquid/objects/shopify/discount-code.md b/platform/liquid/objects/shopify/discount-code.md index 4b6144d..4959e77 100644 --- a/platform/liquid/objects/shopify/discount-code.md +++ b/platform/liquid/objects/shopify/discount-code.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/dispute.md b/platform/liquid/objects/shopify/dispute.md index 23ae132..6160554 100644 --- a/platform/liquid/objects/shopify/dispute.md +++ b/platform/liquid/objects/shopify/dispute.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/draft-order.md b/platform/liquid/objects/shopify/draft-order.md index 373aaa9..a93e103 100644 --- a/platform/liquid/objects/shopify/draft-order.md +++ b/platform/liquid/objects/shopify/draft-order.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/fulfillment-event.md b/platform/liquid/objects/shopify/fulfillment-event.md index b023ac3..024339d 100644 --- a/platform/liquid/objects/shopify/fulfillment-event.md +++ b/platform/liquid/objects/shopify/fulfillment-event.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/fulfillment-order.md b/platform/liquid/objects/shopify/fulfillment-order.md index e6d5bf6..7c00af5 100644 --- a/platform/liquid/objects/shopify/fulfillment-order.md +++ b/platform/liquid/objects/shopify/fulfillment-order.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/fulfillment.md b/platform/liquid/objects/shopify/fulfillment.md index 91d4a6b..a6adf07 100644 --- a/platform/liquid/objects/shopify/fulfillment.md +++ b/platform/liquid/objects/shopify/fulfillment.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/gift-card.md b/platform/liquid/objects/shopify/gift-card.md index 3be7c64..66eb0bc 100644 --- a/platform/liquid/objects/shopify/gift-card.md +++ b/platform/liquid/objects/shopify/gift-card.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/inventory-item.md b/platform/liquid/objects/shopify/inventory-item.md index 0b6fa68..5d74f49 100644 --- a/platform/liquid/objects/shopify/inventory-item.md +++ b/platform/liquid/objects/shopify/inventory-item.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/inventory-level.md b/platform/liquid/objects/shopify/inventory-level.md index 834c517..fc1526c 100644 --- a/platform/liquid/objects/shopify/inventory-level.md +++ b/platform/liquid/objects/shopify/inventory-level.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/line-item.md b/platform/liquid/objects/shopify/line-item.md index 45661d1..70a02b6 100644 --- a/platform/liquid/objects/shopify/line-item.md +++ b/platform/liquid/objects/shopify/line-item.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/location.md b/platform/liquid/objects/shopify/location.md index 98e809c..69fca4e 100644 --- a/platform/liquid/objects/shopify/location.md +++ b/platform/liquid/objects/shopify/location.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/metafields/README.md b/platform/liquid/objects/shopify/metafields/README.md index 4f72dcc..1d42d3b 100644 --- a/platform/liquid/objects/shopify/metafields/README.md +++ b/platform/liquid/objects/shopify/metafields/README.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/metafields/metafield-collection.md b/platform/liquid/objects/shopify/metafields/metafield-collection.md index eef53e8..9057b1e 100644 --- a/platform/liquid/objects/shopify/metafields/metafield-collection.md +++ b/platform/liquid/objects/shopify/metafields/metafield-collection.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/metafields/metafield-object.md b/platform/liquid/objects/shopify/metafields/metafield-object.md index 0a5234e..3e1891c 100644 --- a/platform/liquid/objects/shopify/metafields/metafield-object.md +++ b/platform/liquid/objects/shopify/metafields/metafield-object.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/metafields/metafield-representation-object.md b/platform/liquid/objects/shopify/metafields/metafield-representation-object.md index 7d7bbc4..cc01b3b 100644 --- a/platform/liquid/objects/shopify/metafields/metafield-representation-object.md +++ b/platform/liquid/objects/shopify/metafields/metafield-representation-object.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../../core/actions/shopify.md#graphql) going forward. The [product](../product.md) and [variant](../variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/order-risk.md b/platform/liquid/objects/shopify/order-risk.md index a4b605a..bac412f 100644 --- a/platform/liquid/objects/shopify/order-risk.md +++ b/platform/liquid/objects/shopify/order-risk.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/order.md b/platform/liquid/objects/shopify/order.md index 070cef2..518e4d0 100644 --- a/platform/liquid/objects/shopify/order.md +++ b/platform/liquid/objects/shopify/order.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/price-rule.md b/platform/liquid/objects/shopify/price-rule.md index d39942a..1b49480 100644 --- a/platform/liquid/objects/shopify/price-rule.md +++ b/platform/liquid/objects/shopify/price-rule.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/product-image.md b/platform/liquid/objects/shopify/product-image.md index b22d229..5f7f760 100644 --- a/platform/liquid/objects/shopify/product-image.md +++ b/platform/liquid/objects/shopify/product-image.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/product.md b/platform/liquid/objects/shopify/product.md index 765e175..8d0c4e5 100644 --- a/platform/liquid/objects/shopify/product.md +++ b/platform/liquid/objects/shopify/product.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/refund.md b/platform/liquid/objects/shopify/refund.md index b784f32..b28b8e5 100644 --- a/platform/liquid/objects/shopify/refund.md +++ b/platform/liquid/objects/shopify/refund.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/shipping-zone.md b/platform/liquid/objects/shopify/shipping-zone.md index 5b63f98..b1576a7 100644 --- a/platform/liquid/objects/shopify/shipping-zone.md +++ b/platform/liquid/objects/shopify/shipping-zone.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/shop.md b/platform/liquid/objects/shopify/shop.md index f3ae907..de4c558 100644 --- a/platform/liquid/objects/shopify/shop.md +++ b/platform/liquid/objects/shopify/shop.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/theme-asset.md b/platform/liquid/objects/shopify/theme-asset.md index 0a93fa2..0c5c64a 100644 --- a/platform/liquid/objects/shopify/theme-asset.md +++ b/platform/liquid/objects/shopify/theme-asset.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/theme.md b/platform/liquid/objects/shopify/theme.md index d40deeb..a75d001 100644 --- a/platform/liquid/objects/shopify/theme.md +++ b/platform/liquid/objects/shopify/theme.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/transaction.md b/platform/liquid/objects/shopify/transaction.md index e3a68e1..fc9e634 100644 --- a/platform/liquid/objects/shopify/transaction.md +++ b/platform/liquid/objects/shopify/transaction.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/objects/shopify/variant.md b/platform/liquid/objects/shopify/variant.md index 97f8eb9..d2889d7 100644 --- a/platform/liquid/objects/shopify/variant.md +++ b/platform/liquid/objects/shopify/variant.md @@ -4,9 +4,9 @@ **Important Notice** \ -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ +Shopify has deprecated the REST Admin API that these Mechanic objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate).\ \ -Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use the [GraphQL](../../../../core/actions/shopify.md#graphql) going forward. The [product](product.md) and [variant](variant.md) objects ceased to work on Feb 1, 2025 due to changes made by Shopify. Shopify is phasing out the REST API entirely — read more [here](https://shopify.dev/docs/apps/build/graphql/migrate). \ All of our [library tasks](https://tasks.mechanic.dev/) will be ported to use GraphQL only, which will provide a model for how you can update your custom tasks. You'll be able to update your non-customized library tasks with a click of a button :relaxed:\ diff --git a/platform/liquid/tags/README.md b/platform/liquid/tags/README.md index 745ee63..971f445 100644 --- a/platform/liquid/tags/README.md +++ b/platform/liquid/tags/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Custom Liquid tags in Mechanic — action, log, error, permissions, and more for producing task output. +--- + # Mechanic tags Mechanic extends Liquid with custom tags that go beyond what standard Liquid provides. These tags are how tasks produce output — defining actions, logging data, raising errors, and more. diff --git a/platform/policies/README.md b/platform/policies/README.md index a13382f..cfb1260 100644 --- a/platform/policies/README.md +++ b/platform/policies/README.md @@ -1,3 +1,8 @@ +--- +description: >- + Mechanic's operational policies — data retention, subscription plans, pricing, and privacy practices. +--- + # Policies This section covers Mechanic's operational policies — how data is handled, what plans are available, pricing details, and privacy practices. diff --git a/resources/converting-tasks-from-shopify-rest-to-graphql/README.md b/resources/converting-tasks-from-shopify-rest-to-graphql/README.md index ab86b12..0eb9b10 100644 --- a/resources/converting-tasks-from-shopify-rest-to-graphql/README.md +++ b/resources/converting-tasks-from-shopify-rest-to-graphql/README.md @@ -1,11 +1,16 @@ -# 🏆 Converting tasks from Shopify REST to GraphQL +--- +description: >- + Step-by-step guides for migrating Mechanic tasks from Shopify's deprecated REST API to GraphQL. +--- + +# Converting tasks from Shopify REST to GraphQL {% hint style="danger" %} **Important Notice** -Shopify is deprecating the Shopify Admin REST API which the Mechanic REST objects depend on. The first round of deprecations involve the product and variant endpoints. Read about the deprecation [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Shopify has deprecated the REST Admin API that Mechanic's REST objects depend on. The product and variant endpoints were removed on Feb 1, 2025, and Shopify is phasing out the remaining REST endpoints over time. Read more [here](https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing) and [here](https://shopify.dev/docs/apps/build/graphql/migrate). -Use the [GraphQL](../../core/actions/shopify.md#graphql) going forward. The [product](../../platform/liquid/objects/shopify/product.md) and [variant](../../platform/liquid/objects/shopify/variant.md) objects will cease to work on on Feb 1, 2025 due to the changes being made by Shopify. Shopify will phase out the REST API completely over time, you can read more about this [here](https://shopify.dev/docs/apps/build/graphql/migrate). +Use [GraphQL](../../core/actions/shopify.md#graphql) going forward. The [product](../../platform/liquid/objects/shopify/product.md) and [variant](../../platform/liquid/objects/shopify/variant.md) objects no longer work. The remaining REST objects will follow as Shopify continues the migration. {% endhint %} diff --git a/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-metafield-lookups-from-a-resource.md b/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-metafield-lookups-from-a-resource.md index 1585801..1a31574 100644 --- a/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-metafield-lookups-from-a-resource.md +++ b/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-metafield-lookups-from-a-resource.md @@ -1,6 +1,6 @@ # Conversion: Metafield lookups from a resource -For every Shopify resource object that supports metafields, Mechanic has traditionally provided a way to directly access those metafields from the resource using [dot notation](../../platform/liquid/objects/shopify/metafields/metafield-collection.md). This shortcut will no longer be accessible for product and variant REST resources once they are fully deprecated. +For every Shopify resource object that supports metafields, Mechanic has traditionally provided a way to directly access those metafields from the resource using [dot notation](../../platform/liquid/objects/shopify/metafields/metafield-collection.md). This shortcut is no longer accessible for product and variant REST resources, which were deprecated on Feb 1, 2025. {% code title="REST - product metafield value check" lineNumbers="true" %} diff --git a/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-resource-lookups-in-task-option-fields.md b/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-resource-lookups-in-task-option-fields.md index ebc0933..559a299 100644 --- a/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-resource-lookups-in-task-option-fields.md +++ b/resources/converting-tasks-from-shopify-rest-to-graphql/conversion-resource-lookups-in-task-option-fields.md @@ -1,6 +1,6 @@ # Conversion: Resource lookups in task option fields -An oft utilized feature of Mechanic is the ability to add Liquid tags into task options fields, such as a configurable email body. Additionally, these Liquid tags (currently) support inline resource lookups for data not available in the event webhook. However, for products and variants this will no longer work as of the [Feb 1, 2025 REST deprecation date](../../platform/liquid/objects/shopify/). +An oft utilized feature of Mechanic is the ability to add Liquid tags into task options fields, such as a configurable email body. Additionally, these Liquid tags (currently) support inline resource lookups for data not available in the event webhook. However, for products and variants this no longer works as of the [Feb 1, 2025 REST deprecation](../../platform/liquid/objects/shopify/). {% code title="REST - product resource lookup from line item" %} diff --git a/resources/tutorials/your-first-custom-task.md b/resources/tutorials/your-first-custom-task.md index daed1bc..dcb4f29 100644 --- a/resources/tutorials/your-first-custom-task.md +++ b/resources/tutorials/your-first-custom-task.md @@ -1,3 +1,8 @@ +--- +description: >- + Build your first Mechanic task from scratch — a step-by-step tutorial for auto-tagging high-value Shopify orders. +--- + # Your first custom task This tutorial walks you through building a complete Mechanic task from scratch. By the end, you'll have a working task that automatically tags orders over $100 with a "high-value" tag. diff --git a/resources/video-walkthroughs/README.md b/resources/video-walkthroughs/README.md index 595a91f..fed1d18 100644 --- a/resources/video-walkthroughs/README.md +++ b/resources/video-walkthroughs/README.md @@ -1,2 +1,7 @@ +--- +description: >- + Video tutorials for common Mechanic tasks — auto-tagging, inventory sync, email automation, and more. +--- + # Video walkthroughs diff --git a/techniques/preventing-action-loops.md b/techniques/preventing-action-loops.md index 288b99f..cd58ae3 100644 --- a/techniques/preventing-action-loops.md +++ b/techniques/preventing-action-loops.md @@ -95,3 +95,8 @@ Mechanic has some built-in features to prevent action loops: 1. For tasks responding to `mechanic/actions/perform`, Mechanic will detect identical results to their predecessors and mark the task run as failed. 2. For tasks responding to Shopify update events like `shopify/products/update`, Mechanic will detect repeated, identical task runs and error all action runs generated by the flagged task run. +## Related + +* [Responding to action results](responding-to-action-results.md) — how to safely subscribe to mechanic/actions/perform without creating loops +* [Debouncing events](debouncing-events.md) — another approach to managing high-frequency events that could cause repeated processing +