Mechanic is a development and ecommerce automation platform, for Shopify.

You’re looking at our library: 360 tasks, ready to go. Or write something new, in Liquid. :)

Useful for digital products, shipping insurance, gift cards, or anything else that needs to be fulfilled instantly. This task watches for new orders, and auto-fulfills all line items that don't require shipping.
Runs Occurs whenever an order is created, Occurs whenever an order is updated, with a 30 second delay, and Occurs when a user manually triggers the task. Configuration includes include products with any of these tags, exclude products with any of these tags, only process paid orders, wait until any other shippable items are fulfilled, and fulfill gift cards.
This task re-sorts your collections, beginning with the sort order of your choice (alphabetically, best selling first, etc), and then moving all out-of-stock products to the very end of the collection.
Runs Occurs when a user manually triggers the task. Configuration includes base sort order, collection handles or ids to include, collection handles or ids to exclude, force manual sorting on collections, run hourly, and run daily.
This task will keep your sale tags in sync, without any manual work. Configure the task with a tag to apply (and optionally a tag for products that aren't on sale), and Mechanic will take care of applying and removing tags as appropriate.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, and Occurs when a user manually triggers the task. Configuration includes tag for sale products, tag for all other products, and sale products must have a price lower than the compare at price.
This task monitors inventory updates, and pulls the product from the configured sales channels whenever a product's total inventory meets your "out of stock" threshold. Optionally, it'll send you an email when it does so. You may also choose whether to further refine the products being considered by this task by configuring inclusion or exclusion tags (note: exclusion tags will always take precedence over inclusion tags).
Runs Occurs when a user manually triggers the task and Occurs whenever an inventory level is updated. Configuration includes out of stock inventory quantity, sales channel names, only include products with any of these tags, always exclude products with any of these tags, only include inventory from these location names, and email notification recipient.
Running manually or on a schedule, this task scans all products in your store, and adds a tag to any products that have no images. Optionally, choose to have this task remove that tag from any products that are found to have an image.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes product tag to add, remove product tag if images are found, run every 10 minutes, run hourly, and run daily.
This task watches for incoming orders, and tags them if they contain a product that matches by title or by product tags. Additionally, edited orders will have tags added or removed in line with product additions or removals. Run this task manually to scan your store's order history, tagging older orders that qualify, and untagging those that have been edited and no longer do.
Runs Occurs whenever an order is created, Occurs whenever an order is edited, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes required product title, required product tags, and order tags to apply.
Use this task to maintain a "New Products" collection, specifying either a number of products to include or the number of days to keep each product around. Easy! :)
Runs Occurs when a user manually triggers the task and Occurs every day at midnight (in local time). Configuration includes collection id, number of days to keep a product in this collection, and number of products to keep in this collection.
Use this task to monitor order tags, and notify staff, vendors, or any other interested parties when an order receives a certain tag. Useful for keeping teams across your business up to date as an order progresses.
Runs Occurs whenever an order is updated. Configuration includes tag to watch for, ignore orders that are older than this task, email recipients, email subject, and email body.
Configure this task with search terms that describe certain products, and this task will apply the tags of your choice to every customer who purchases a matching product or product variant. Run this task manually to tag all customers who have a qualifying order already on file.
Runs Occurs whenever an order is paid, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes search query, search for, customer tags to apply, and test mode.
Use this task to tag incoming orders with all the product tags in the order. Optionally, specify a specific list of tags to be copied, and/or a certain tag prefix to watch for. Can be run manually, to scan and tag historical orders.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, Occurs when a bulk operation is completed, and Occurs when a user sends an order to Mechanic. Configuration includes only copy these tags and only copy tags having one of these prefixes.
Improve your customer relationships without complicated your workflow - use this task to send automatic emails whenever your staff adds a certain tag to an order. (Mechanic will add another tag to your order when the email is sent, for visibility.)
Runs Occurs whenever an order is updated. Configuration includes tag to watch for, email subject, email body, ignore orders older than this task, and ignore orders having this tag.
This task checks the payment gateways for new orders immediately upon order creation, and tags the order accordingly.
Runs Occurs whenever an order is created. Configuration includes payment gateway names and tags and run when orders are paid instead of created.
Use this task to get email or Slack notifications when errors occur with any events, tasks, and actions in Mechanic. Use this task out of the box, customize it, or borrow logic for your more advanced error reporting tasks.
Runs Occurs when an event fails, Occurs when a task fails, and Occurs when an action fails. Configuration includes notification methods, email recipients, slack account, and slack channel id .
This task scans for orders that are more than X days or hours old that have a financial status of "pending", and ensures that they are all closed/archived and cancelled. Pending orders that are already closed will be cancelled, and pending orders that are already cancelled will be closed. Optionally, choose to add a tag to such orders, and whether to restock line items.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes only process orders having this tag, ignore orders having this tag, period to wait before checking each order, period to wait is in hours, period to wait is in days, tag to add to the order, cancellation reason to set, restock line items, send cancellation email to customer, and test mode.
This task watches for newly-created orders, and copies any discount codes present to the order's tags.
Runs Occurs whenever an order is created.
Quickly identify and sort orders based on their shipping method, using automatic order tags. This task supports auto-tagging incoming orders, and can be run manually to tag historical orders.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes shipping method titles and tags and allow partial matches for shipping method titles.
This task scans every product in your store, and adds or removes the tags you configure, according to how many days have passed since the product was created. (Or published, if you prefer!)
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes product tags and age threshold in days, match product tags by minimum age, match product tags by maximum age, use product publish times instead of creation times, run daily, and run hourly.
Watches for incoming orders that are the very first order on file for the related customer, and adds the tag of your choice.
Runs Occurs whenever an order is created. Configuration includes order tag to add.
Use this task to automatically sync inventory for a simple product bundle – no theme modifications required. When configured with unique SKUs for the bundle and its components, and with quantities needed from each component for each bundle unit, this task keeps the bundle inventory set to the greatest possible value, given the quantities of its components. It also appropriately subtracts from component inventory whenever the bundle is ordered, and appropriately raises component inventory when a bundle order is refunded and restocked.
Runs Occurs whenever an order is created, Occurs whenever a new refund is created without errors on an order, independent from the movement of money, Occurs whenever an inventory level is updated, and Occurs when a user manually triggers the task. Configuration includes bundle product sku, component product skus and quantities per bundle, and inventory buffer quantity.
Automatically send out an email to your customers when a tag is added to their account. Useful for sending approval emails, welcome emails if the customer was created with a certain tag, or any other emails related to an update to the customer's status. The most common use of this task is to send out emails to customers when their accounts are approved, but you can use this task to email customers any kind of alert you like, triggered by a simple tag. For example, some themes include an email subscription form that creates a customer record, pre-tagged with "email subscribe", or something to that effect.
Runs Occurs whenever a customer is created, Occurs whenever a customer is updated, and Occurs when a user manually triggers the task. Configuration includes tag to watch for, ignore tag case, autotag customers after emailing, email subject, and email body.
Use this task to keep you and your team updated when products go out of stock - and, optionally, when they go back in stock. Filter with a simple product search to only track products you care about. Choose a custom stock threshold to get a heads up before the stock level reaches zero.
Runs Occurs whenever an inventory level is updated and Occurs when a user manually triggers the task. Configuration includes out of stock inventory quantity, only monitor products matching this search query, send email for out of stock products, send email for back in stock products, and stock update email recipients.
This task exists to fill the gap between Shopify's admin product search, and product metafields. Use this task to copy metafield values to product tags, allowing you to filter products by tags based on those metafields.
Runs Occurs when a user manually triggers the task. Configuration includes metafield namespace, metafield keys and tag prefixes, monitor new and updated products, remove outdated prefixed tags, and test mode.
This task monitors inventory updates, and publishes the product to the configured sales channels whenever a product's total inventory meets your "back in stock" threshold. Optionally, it'll send you an email when it does so. You may also choose whether to further refine the products being considered by this task by configuring inclusion or exclusion tags (note: exclusion tags will always take precedence over inclusion tags).
Runs Occurs whenever an inventory level is updated and Occurs when a user manually triggers the task. Configuration includes back in stock inventory quantity, sales channel names, only include products with any of these tags, always exclude products with any of these tags, only include inventory from these location names, and email notification recipient.
This task monitors all variants having a SKU that you configure, and ensures that changes to the available inventory quantity are reflected across all variants sharing that SKU.
Runs Occurs when a user manually triggers the task and Occurs every 10 minutes. Configuration includes product skus to monitor.
Use this task to apply certain tags to newly-created orders, based on what tags are on the associated customer. Configure this task with one-to-one mappings of customer tags to look for, connected to order tags to add.
Runs Occurs whenever an order is created. Configuration includes customer tags to look for and order tags to add.
Use this task to automatically select a specific product template for each of your products, based on how each product is tagged. Useful for a set-it-and-forget-it setup. :)
Runs Occurs when a user manually triggers the task, Occurs when a bulk operation is completed, Occurs whenever a product is created, and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes product tags and template suffixes.
Automatically prompt customers to activate their customer accounts, after placing an order in your store, by triggering a customizable Shopify-powered email. Useful if your online store unlocks special offers, functionality, or content after making a purchase. Optionally, only send invitations if the customer has a certain tag and/or has ordered a product with a specific tag.
Runs Occurs whenever an order is created. Configuration includes only invite if the customer has not yet been invited, only invite if the customer has this tag, only invite if the order contains a product with this tag, custom invitation email subject, custom invitation email message, and invitation email bcc.
Use this task to automatically tag orders based on what collection(s) the customer has ordered from. Useful for broadly classifying orders according to their contents.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes collections and tags.
Quickly send a thank-you email (or any other sort of follow-up email) to your customers, as soon as their order is paid. (Optionally, require one or more order tags to be present, in order for the email to be sent.) And it's super easy to add a delay – set the task to subscribe "shopify/orders/paid+2.days" or "shopify/orders/paid+1.week" instead to create a thoughtful just-checking-back-in-with-you message. :)
Runs Occurs whenever an order is paid. Configuration includes required order tags at the time of payment, email subject, and email body.
This task runs whenever a product is updated (which includes product creation), and it will add the configured "tags to add" to the product when the corresponding "tags to watch for" are present.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes tags to watch for and tags to add, remove tags to add when the corresponding tag to watch for is removed, and manual bulk mode.
It's critical to stay on top of any orders that aren't properly fulfilled – and your customers care, too! Use this task to auto-tag orders, to email yourself a reminder, and optionally to send customers a little reassurance message, if an order hasn't been fulfilled a configurable number of days after payment.
Runs Occurs whenever an order is paid, with a 2 day delay. Configuration includes include partially fulfilled orders, tag to add, staff notification recipient, send the customer an email, customer email subject, customer email body, and days to wait before followup.
This task monitors new and updated products, applying the tag(s) of your choice to them based on their individual product type. Run this task manually to tag all of your products at once.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, and Occurs when a user manually triggers the task. Configuration includes product types and tags and remove product tags in this list when they do not apply.
Use this task to easily make your inventory levels available in your online storefront theme. This task monitors for changes to inventory, and copies inventory availability figures to metafields on the related variant.
Runs Occurs whenever an inventory level is connected, Occurs whenever an inventory level is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes metafield namespace and location ids and metafield keys.
This task re-sorts your collections by the product property, product metafield, or variant property that you choose. Use the "Product property" or "First variant property" options to control what attribute the task looks up. For example, using publishedAt in the "Product property" field will result in sorting by the date and time the product was published, while using sku in the "First variant property" field will result in sorting by the sku of the first variant of each product in the collection. Alternatively, enter a product metafield as "namespace.key" (e.g. store.priority), and the task will attempt to sort by the value of that metafield.
Runs Occurs when a user manually triggers the task, Occurs whenever user/collection_sort/process is triggered, and Occurs whenever user/collection_sort/complete is triggered. Configuration includes product property, product metafield, first variant property, only sort these collections, reverse sort, sort naturally, run hourly, and run daily.
This task scans your entire product list, looking for duplicate SKUs using exact matching, and returning the list of duplicate SKUs (and the associated product variant IDs) if any are found.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes exclude products that do not track inventory.
Use this task to generate and email a CSV of orders, including one row per line item. Filter with a search query or by tags, and auto-tag orders as they're exported. Run the export on demand, and/or nightly. This task is also useful as a template for further development.
Runs Occurs when a user manually triggers the task. Configuration includes search query for orders, ignore orders with this tag, add this tag after export, export email recipient, export email subject, export email body, export csv filename, and run export nightly.
This task watches for order tags, and adds a corresponding tag to the customer whenever a known order tag is found.
Runs Occurs whenever an order is updated. Configuration includes order tags and customer tags.
This task watches for newly-paid orders (or newly-fulfilled orders, if you choose), and adds or moves the purchased products to the top of the collection of your choice. Optionally, ignore products that are sold out. Useful for "trending products" functionality. :)
Runs Occurs whenever an order is paid. Configuration includes collection maximum size, collection id, ignore products that are sold out, and wait until order is fulfilled.
This task scans your active products, in bulk, and tags them according to whether or not they're in stock. Optionally, configure this task to monitor products for live auto-tagging.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes in stock tag, out of stock tag, and monitor products for inventory updates.
This task automatically tags incoming orders with the UTM campaign, content, medium, source, and/or term associated with the customer's visit. Run this task manually to tag your existing orders.
Runs Occurs whenever an order is created, with a 2 minute delay, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes tag with utm campaign, tag with utm content, tag with utm medium, tag with utm source, and tag with utm term.
This task monitors order tags, and when a certain tag is added to an order, it auto-fulfills all unfulfilled items in the order. Optionally, you can choose to notify customers when their order is fulfilled by this task.
Runs Occurs whenever an order is updated. Configuration includes order tag to watch for, ignore if this order tag is found, and notify customer on fulfillment.
Use this task to automatically add products, as they're tagged, to a specific delivery profile. Untag products to remove them from the configured profile.
Runs Occurs whenever a product is created and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes delivery profile id and required product tag.
If you prefer to categorize your products using manual collections, but you still need your tags to match up, use this task to monitor your manual collection and automatically tag the products it contains.
Runs Occurs when a user manually triggers the task and Occurs whenever a collection is updated, including whenever products are added or removed from the collection. Configuration includes collection tag and collection id.
When products are created, this task will auto-create smart collections by product type and/or vendor, if such collections don't already exist. Additionally, configuring one or more exact sales channel names will enable publishing of any newly created collections by this task to those sales channels.
Runs Occurs whenever a product is created and Occurs when a user manually triggers the task. Configuration includes create collections by product type, create collections by vendor, names of sales channels to publish collections to, and run daily.
Does exactly as it says: this task will publish all active products to the sales channel(s) of your choice, on demand. Optionally, filter products by a search query, or choose to have this task run hourly or daily.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes sales channel names, only publish products matching this query, test mode, run hourly, and run daily.
Use this task to notify staff (or suppliers, or anyone!) of incoming orders. Optionally, choose to only be notified when orders are paid, or only for orders that contain at least one product with a certain tag.
Runs Occurs whenever an order is created. Configuration includes only for orders including this product tag, email recipients, email subject, email body, and only for paid orders.
This task is a simple demonstration of pulling product titles and images into a PDF, resulting in a simple catalog of the products available in your store. Use it as a starting point for building something more complex.
Runs Occurs when a user manually triggers the task.
Automatically generate an invoice PDF, to be emailed to the address on file for the order, if the order has not yet been paid. Useful for working with billing departments, or with anyone else who needs an order summary auto-emailed. :)
Runs Occurs whenever an order is created. Configuration includes days to wait before emailing, email subject, email body, pdf attachment filename, and pdf html template.
Based on an out-of-stock threshold you define, this task sends you an email summary (with CSV attachment) of all variants that are out of stock in any location. Run this task manually to receive the report on demand.
Runs Occurs when a user manually triggers the task and Occurs every day at midnight (in local time). Configuration includes out of stock quantity, report recipient email, and report subject.
Use this task to copy each product's vendor to the product's tag. Optionally, you can apply a prefix to all vendor tags (e.g. "vendor-"). Run this task manually to scan every product in your store. Otherwise, this task will run for specific products, whenever a product is created or updated.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, and Occurs when a user manually triggers the task. Configuration includes apply this prefix to vendor tags.
Use this task to easily keep an eye on which products are in stock, or out of stock, as established by individual locations. Configure tag prefixes and suffixes to arrive at product tags resembling "location-123456890-instock" or "oos-123456890". Configure this task to run hourly or daily, to keep these tags in sync.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes tag prefix when in stock, tag suffix when in stock, tag prefix when out of stock, tag suffix when out of stock, run daily, and run hourly.
This task tags every new customer, with the same configurable tag. :)
Runs Occurs whenever a customer is created. Configuration includes tag.
Use this task to copy prefixed tags to metafields, useful for Online Store 2.0 filtering. When run manually, it will scan for all of the object type you have configured in the task, and add/update the configured metafield on each with the resulting tag value when the tag prefix is matched.
Runs Occurs when a user manually triggers the task. Configuration includes shopify object type, metafield namespace, metafield key, metafield type, and tag prefix.
Use this task to receive an immediate email alert, whenever a variant's total inventory hits 0, when added up across all locations. You can limit alerts to a specific collection or publication (e.g. Online Store or Point of Sale).
Runs Occurs whenever an inventory level is updated and Occurs when a user manually triggers the task. Configuration includes must belong to collection id, must be published to publication id, email subject, email body, and email recipient.
This task sends recurring unpaid order reminders to customers, emailing them on a configurable schedule, until the order is no longer "pending" or until the order is cancelled.
Runs Occurs every hour. Configuration includes include partially paid orders, limit to orders matching this query, ignore customers having this tag, initial delay period, interval period between emails, periods given are in days, periods given are in hours, email subject, email body, and test mode.
Use this task to automatically make add new products to the sales channels of your choice, making each product available on each channel immediately after the product is created.
Runs Occurs whenever a product is created. Configuration includes sales channel names.
This task watches for certain product tags, and removes the product from the selected sales channel(s) when those tags are found.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes product tags to watch for, require product to have all given tags before unpublishing, and sales channel names.
Super basic, super useful. :) Get an email alert whenever a customer account is created.
Runs Occurs whenever a customer is created. Configuration includes to, subject, and body.
Use this task to add tags to your products, based on their options, for easy filtering. A shirt might be tagged with "Color-Blue" and "Size-XL", for example. Optionally, choose to ignore options that only appear on out-of-stock variants, or choose to apply all tags in lowercase.
Runs Occurs when a user manually triggers the task, Occurs when a bulk operation is completed, Occurs whenever a product is created, and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes product options to consider, option name and value separator, use lowercase tags, ignore variants that are out of stock, run for all products daily, run for individual products when they are created or updated, and run for individual products when their inventory changes.
Use this task to tag orders as they come in, based on which sales channel created them. Run this task manually to backfill tags for all orders.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes sales channel names and tags.
Shopify's product collection filters allow you to filter by the tags the product contains – but not the tags a product does not contain. Use this task to sync an "inverse" tag to all products who do not have a particular tag, allowing you to create collections in Shopify that use the inverse tag.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes product tag to watch and product tag to use when missing.
Out of the box, this task scans the last week's worth of paid orders, and auto-tags products that meet the sales threshold of your choice, removing the tag from products that no longer qualify. This scan can be run on demand (with the "Run task" button), and will otherwise run nightly.
Runs Occurs when a user manually triggers the task, Occurs every day at midnight (in local time), and Occurs when a bulk operation is completed. Configuration includes tally by line item quantity, tally by line item subtotals, tally by number of orders, minimum tally threshold per product, product tag to apply, and order query.
Use this task to help you close in on the last few products that are missing cost values. Trigger this task manually to process your entire catalog, or let this task update tags as needed for products you create or update.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes tag for cost missing.
Use this task as a starting point, for allowing visitors to submit their carts to be transformed into draft orders, associated with their customer account. Installing and customizing this task requires some level of comfort with Liquid, HTML, and JavaScript.
Runs . Configuration includes shared secret, mechanic webhook event topic, and mechanic webhook url.
Use this this task to monitor for the addition of a specific product tag, and to schedule the product to be untagged a configurable number of days later. Useful for temporarily adding a product to a collection, or qualifying the product for some other temporary functionality.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated and Occurs whenever user/task/untag_product is triggered. Configuration includes tag to monitor and days to wait before untagging.
Follow up with your customers automatically, and establish the purchase -> earn-reviews -> attract-customers cycle. This task comes prefilled with a friendly, customizable email that gives the customer direct links to their purchases on your website, where they can leave a review using your existing review system.
Runs Occurs whenever an order is fulfilled, with a 7 day delay. Configuration includes days to wait before emailing, only send to customers who have accepted marketing, customer tag to add after sending, ignore customers having this tag, ignore orders having this tag, email subject, and email body.
Use this this task to monitor for the addition of a specific customer tag, and to schedule the customer to be untagged a configurable number of days later. Useful for granting temporary access to discounts, or other resources.
Runs Occurs whenever a customer is updated and Occurs whenever user/task/untag_customer is triggered. Configuration includes tag to monitor and days to wait before untagging.
Use this task to tag customers by tier, based on how many orders they've placed or by the sum of all their order totals (i.e. total spend). Optionally, configure a customer segment query, limiting the set of customers that are processed. You may also configure an order query, specifying for things like a rolling time period, or fulfillment status. This task is useful for rewarding customers who establish or maintain a specific spend level.
Runs Occurs when a user manually triggers the task. Configuration includes customer tags and order minimums, only keep the customer tag for the highest order minimum, tag customers by, only process customers matching this segment query, only count orders matching this query, run hourly, and run daily.
Monitoring for brand-new orders, this task tags each order with the fulfillment locations that Shopify automatically assigns at the moment of order creation. (Note: It's not currently possible to adjust tags when assigned fulfillment locations change.)
Runs Occurs whenever an order is created.
This task removes the matched tags from all products in your shop. Optionally, choose to remove partial tag matches as well (e.g. configured tag: "sale", matched tags: "sale", "sale 10", "on sale", etc.).
Runs Occurs when a user manually triggers the task. Configuration includes tags list, remove partial tag matches, and test mode.
Use this task to tag products when they reach the out of stock inventory level you configure. Optionally, fill in the email alert recipient to send an alert when a product is initally tagged for being out of stock.
Runs Occurs whenever an inventory level is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes out of stock inventory level, product tag, and email alert recipient.
This task runs automatically for individual customers, as they are created and updated. It will tag customers when they have an enabled account (i.e. have a registered email address and active password), and it will untag customers whose accounts are disabled.
Runs Occurs whenever a customer is created, Occurs whenever a customer is updated, and Occurs when a user manually triggers the task. Configuration includes customer tag to apply and test mode.
This task re-sorts your collections, beginning with the sort order of your choice (alphabetically, best selling first, etc), and then by total inventory in descending order. Products whose inventory is not tracked (i.e. limitless inventory) will be moved to the top and out-of-stock products (inventory <= 0) will be moved to the bottom. Optionally, choose to sort by the sellable online quantity (i.e. locations enabled for online order fulfillment) instead of the total inventory for a product across all locations.
Runs Occurs when a user manually triggers the task. Configuration includes base sort order, collection handles or ids to include, collection handles or ids to exclude, force manual sorting on collections, use sellable online quantity instead of total inventory, run hourly, and run daily.
This task automatically adds the tag of your choice to incoming orders, based on the country in the order's shipping address.
Runs Occurs whenever an order is created. Configuration includes tags to apply and country codes.
Send an email to the customer with specific information regarding a product they just purchased. Useful for digital products, or anytime you'd like to communicate something extra about a product you offer. (Note: this does not replace the Shopify order confirmation email!)
Runs Occurs whenever an order is created. Configuration includes email subject, email body, product sku, and days to wait before emailing.
This task watches for new orders, and checks each line item for that variant's total inventory quantity. If any are found with an inventory level of 0 or less, the task will add the tag of your choice to the order, and optionally will add a tag to the customer and to each product related to an out-of-stock line item.
Runs Occurs whenever an order is created. Configuration includes apply this order tag, ignore variants marked for oversell, apply this customer tag, and apply this product tag for each out of stock line item.
Upon the fulfillment of an authorized or partially paid order, this task attempts to capture all open authorized payments for that order. (Multiple authorizations can exist on edited orders or with post-purchase upsells.)
Runs Occurs whenever an order is fulfilled.
This task demonstrates Mechanic's ability to compile a CSV export, and send it as an email attachment. In this example, we bundle up a simple export of product titles and IDs, and email it as a CSV attachment.
Runs Occurs when a user manually triggers the task. Configuration includes email recipient.
Immediately upon order creation, add one or more tags to the order. Simple as that. :)
Runs Occurs whenever an order is created. Configuration includes order tags to add.
Use this task to set a default value on a single metafield across all of your products or variants, excluding any where this metafield already has a value set.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes metafield namespace and key, metafield type, metafield default value, set product metafields, and set variant metafields.
Use this task to easily identify customers who used certain discount codes. This task runs automatically on incoming orders, and can be run manually to tag customers based on historical orders. Optionally, choose to remove tags, instead of adding them.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes discount codes and tags, untag customers instead of tagging them, and allow partial matches when checking for discount codes.
This task wait for a configurable number of days (or hours!) after an order placed, and – if the order is still unpaid – emails the customer, and optionally adds a tag to the order. This task only sends one email – it does not send repeating reminders.
Runs Occurs whenever an order is created, with a 7 day delay. Configuration includes email subject, email body, tag to add to the order, number of days to wait, and use hours instead of days.
Use this task to apply the same categorizations you use for your customers. Useful for pre-approving customers, and then quickly sorting your orders based on that pre-approval. Optionally, configure this task to only copy certain tags from customers to their orders.
Runs Occurs whenever an order is created. Configuration includes only copy these tags.
Easily segment your orders by shipment status. Tagging your orders as "Delivered", or "Out for delivery", or "Attempted delivery", or any other status, allows you to stay on top of your order flow. And, adding these tags makes it easier to wire up additional automation, keeping the connection live between your customers and their orders.
Runs Occurs whenever a fulfillment is created, Occurs whenever a fulfillment is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes shipping statuses and tags and limit to orders matching this query for manual runs.
This task cancels orders as soon as Shopify (or another risk-analysis app) determines it to be high risk. Optionally, this task can also auto-tag the order, email the customer, restock the inventory, and/or refund payment.
Runs Occurs whenever an order is updated. Configuration includes cancellation reason to set, ignore unpaid orders, refund payment for cancelled orders, restock inventory for cancelled orders, email customer when cancelling, staff note for timeline, and add this order tag when cancelling.
This task keeps an eye on customers as you create or import them in Shopify, and automatically sends account invitations to any customers that have an email address.
Runs Occurs whenever a customer is created, with a 1 minute delay. Configuration includes invitation email subject and invitation email body.
Do you ship custom items, or do you have a lengthy turnaround time on your orders? Use this task to automatically re-assure customers that their order is in the queue, to be shipped as soon as possible. By default, this task sends an email 10 days (or a number you configure) after the order is paid, as long as the order remains fully paid, unfulfilled, and un-cancelled. Optionally, configure tags to add to the order and/or customer, to be added when the email is sent, and choose whether to only send reminders on weekdays.
Runs Occurs whenever an order is paid and Occurs whenever user/order/customer_reminder is triggered. Configuration includes number of days to wait, only send reminders on weekdays, email subject, email body, tag to add to order, and tag to add to customer.
This task checks for incoming orders, watching for orders that have a specific cart attribute filled in. When present, the task then copies that attribute over to the order's tags.
Runs Occurs whenever an order is created. Configuration includes cart attribute to monitor.
Follow up with your customers – keep those relationships alive, and improve your returning customer rate, by emailing your customers after a few months of no order activity. By default, this task sends an email after 6 months of no order activity, and another 6 months after that.
Runs Occurs whenever an order is created, with a 6 month delay and Occurs whenever an order is created, with a 12 month delay. Configuration includes subject and body.
Useful for multiple price points, or for offering customizations of the same item, this task lets you offer multiple variant listings for what is ultimately the same stock. A purchase of a particular variant results in the inventory for all other variants, for the same product, being lowered by the amount ordered.
Runs Occurs when a user manually triggers the task, Occurs every 10 minutes, and Occurs whenever user/sync_variant_inventory/set_cache is triggered. Configuration includes product tags to monitor, product types to monitor, and only sync active products.
Use this task to send out account invitations to all the customers you already have on file, with the push of a button. Optionally, filter by customer tag.
Runs Occurs when a user manually triggers the task. Configuration includes only invite customers with this tag, custom subject, and custom message.
This task keeps customers tagged with the SKUs of the products they've purchased, optionally ignoring product purchases that have been refunded. Add a tag prefix to make SKU tags easy to distinguish from your other customer tags.
Runs Occurs whenever an order is paid, Occurs whenever a new refund is created without errors on an order, independent from the movement of money, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes tag prefix, ignore refunded purchases, and test mode.
Use this task to tag incoming orders with all of the line item properties found on the order. Optionally, configure a list of property names to be included, or a list of property names to be excluded. This task can also be run manually to scan and tag historical orders.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes property name and value separator, include only these property names, and exclude these property names.
This task is part of the Mechanic tour! Feel free to delete this task once you are done with the tour.
Runs Occurs when a user manually triggers the task. Configuration includes what is your first name, what is your last name, and what is your favorite color.
This advanced task allows you to schedule price change events for your store, useful for seasonal and flash sales. To use this task, configure a price change event using the task options, save the task and run it manually, and then enter a keyword of schedule in the dialog that appears. An email summary with the price change event ID will be sent upon successful scheduling.
Runs Occurs when a user manually triggers the task with text, Occurs whenever user/price_changes/start is triggered, Occurs whenever user/price_changes/end is triggered, and Occurs whenever user/price_changes/reset is triggered. Configuration includes notification email recipients, event start, event end, set compare at prices to original price during event, collection handles and discounts, skus to include, sku discount, exclude products tagged with, skus to exclude, and do not restore prices on reset.
Use this task to keep track of who created what draft order. This task watches for new draft orders, and tags each one with the name of the store staff member who created it. This task can also be run manually, to scan and tag all draft orders already in your store.
Runs Occurs whenever a draft order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes tag prefix.
Use this task to automatically categorize orders based on the cart attributes configured before checkout. Useful if you allow customers to supply extra information about their order, or if your cart has some hidden coding that adds cart attributes programatically.
Runs Occurs whenever an order is created. Configuration includes cart attribute to monitor and cart attribute values and order tags to add.
Does exactly as it says. :)
Runs Occurs whenever a customer is updated. Configuration includes customer tag to watch for, customer tag to remove, and ignore tag case.
This task runs when products are updated, checking if they have a description, and tagging them if not. Once a description has been added, then the tag will be removed.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated and Occurs when a user manually triggers the task. Configuration includes tag to apply.
Running when a customer is updated, this task will fill empty customer names and/or phones on accounts by pulling the relevant data from any customer addresses on file. Optionally, the task may be run in manual mode to scan and update all customers.
Runs Occurs whenever a customer is updated. Configuration includes customer data to update and enable manual runs to scan all customers.
Tracking numbers aren't generally searchable within Shopify. Use this task to fix that, by copying all fulfillment tracking numbers over to the order itself, as (searchable!) order tags.
Runs Occurs whenever a fulfillment is created, Occurs whenever a fulfillment is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed.
This task demonstrates Shopify's ability to edit orders through the admin API. It's intended to be a starting place for developing more specific functionality. Out of the box, this task automatically adds a product to orders that (optionally) meet an order minimum.
Runs Occurs whenever an order is created and Occurs when a Mechanic action is performed. Configuration includes minimum order total, variant id to add, quantity to add, notify customer, and staff note.
Save time by letting this task keep your SKUs up to date, generating them based on your product handle, and the initials of each variant option. Optionally, choose to have the task skip updating variants that already have SKUs. Useful for large catalogs, or for anyone who has a consistent SKU format.
Runs Occurs whenever a product is created and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes skip variants that already have skus and product options to keep unabbreviated.
Does exactly as it says. :)
Runs Occurs whenever an order is updated. Configuration includes order tag to watch for, order tag to remove, and ignore tag case.
This task prompts you for a list of email addresses and tags, one pair per line, in the format "customer@example.com:tag". The task adds each tag to its related customer. Developers: this task is an example of working in batches with GraphQL – useful when working with bulk data.
Runs Occurs when a user manually triggers the task with text.
This task watches for newly-paid orders, and if the configured product is purchased, sends the customer a discount code that's just for them. Optionally, configure the discounts to only apply to a certain collection of products, and to only last for a certain number of days.
Runs Occurs whenever an order is paid and Occurs when a Mechanic action is performed. Configuration includes required product, discount collection, discount code prefix, discount fixed amount, discount percentage, discount applies to each line item individually, discount lifetime in days, discount can be used by anyone, email subject, and email body.
When orders come in, this task will copy tags from the order's products to the customer. Useful for automatically segmenting your customers based on attributes of their purchases. To keep things tidy, configure this task to only copy certain product tags.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes limit to customers matching this query for manual runs and only copy these tags.
This task monitors checkouts in your store, and kicks off an email a configurable number of hours after a checkout is created - if the checkout wasn't completed, and if the customer provided their email address.
Runs Occurs whenever user/checkouts/abandoned is triggered, with a 24 hour delay, Occurs whenever a checkout is created, Occurs whenever a checkout is updated, and Occurs whenever an order is created. Configuration includes email subject, custom message, action button text, cart items header text, primary brand color as hex rgb, and hours to wait before sending email.
This task watches for inventory updates. When a product's total inventory becomes 0 or less, the current time will be recorded for that product. Then, on an hourly basis, this task will unpublish any products with a recorded out-of-stock time of at least x days ago.
Runs Occurs whenever an inventory level is updated, Occurs every hour, and Occurs when a user manually triggers the task. Configuration includes number of days to wait before unpublishing, sales channel names, only include products matching this search query, and test mode.
Super simple. Scans all inventory levels in your store, on demand, and brings the negative ones back up to zero. Optionally, configure this task to run nightly.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes run daily at midnight.
This task checks to see if a product's variants have been discounted (by having a price set below the compare at price), and for each variant that meets one ore more configured discount percentage thresholds, it will save the matched filters in a variant metafield for use with Online Store 2.0 filtering.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated and Occurs when a user manually triggers the task. Configuration includes metafield namespace and key and discount filters and percentage thresholds.
This task scans your product catalog nightly or when you hit the "Run task" button, checking for the presence of a "preorder" tag, or a tag that starts with "preorder_" (like "preorder_summer"). If this tag is found, the task updates the product to allow customers to purchase the product after it's out of stock. If no preorder tag is found, the task makes sure customers cannot purchase the product if it's out of stock.
Runs Occurs every day at midnight (in local time), Occurs when a bulk operation is completed, and Occurs when a user manually triggers the task. Configuration includes run on product create and update instead of daily.
Have your traffic sources refer customers using ?ref=referral-code-here URLs (using the query parameter of your choice), then use this task to automatically tag each customer's order according to the referral value they arrived with. Optionally, tag the customer as well.
Runs Occurs whenever an order is created. Configuration includes query parameter name, cart attribute name, tag customer with parameter value, and only tag the customer for their first order.
Use this task to receive an email alert whenever a single customer exceeds a configurable order count, over the last configurable number of hours.
Runs Occurs whenever an order is created. Configuration includes order count threshold, number of hours to look back, email recipient, email subject, and email body.
This task demonstrates how a product sales report can be generated as PDF and emailed to one or more recipients. It also shows how charts can be embedded in the PDF report using a 3rd party library like ChartJS.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes report on sales from today, report on sales from yesterday, report on sales in past week, report on sales in past month, report on sales in past quarter, report on sales in past year, group by product type, group by vendor, email report recipients, and run this task daily.
This task manages tagging for products, according to whether or not they're published for the sales channel of your choice. Choose a tag to use when the product is published, and/or a tag for when the product is unpublished.
Runs Occurs when a user manually triggers the task. Configuration includes tag to add when published, tag to add when unpublished, sales channel name, run every 10 minutes, run hourly, and run daily.
This task, paired with the linked instructions, creates a feed of product inventory (optionally filtering by product type).
Runs Occurs when a user manually triggers the task, Occurs every day at midnight (in local time), and Occurs every day at midnight (in local time), with a 12 hour delay. Configuration includes filter by product type.
Does exactly as it says. :) Optionally, use combinations of tags to require, and/or combinations of tags to add.
Runs Occurs whenever a customer is created and Occurs whenever a customer is updated. Configuration includes tags to watch for and tags to add and remove tag to add when the corresponding tag to watch for is removed.
Use this task to schedule adding and/or removing tags for specific products, with support for scheduling by date, or by date and hour.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes dates and tags to add, dates and tags to remove, product ids, product tag to monitor, use hour specificity, and test mode.
Use this task to tag orders, as they are created, if every single line item is related to a variant that's in stock.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes order tag to add, ignore line items not fulfilled manually, test mode, run every 10 minutes, and run hourly.
Use this task to notify vendors when items of theirs have been purchased, by providing this task with a list of vendor names, and the related email addresses.
Runs Occurs whenever an order is created and Occurs whenever user/orders/send_vendor_email is triggered. Configuration includes vendors and email addresses, email subject, and email body.
Keep your draft order list tidy - use this task to automatically delete orders that are older than a configurable number of days.
Runs Occurs when a user manually triggers the task. Configuration includes days to wait before deleting a draft order, test mode, and run daily.
This task generates a CSV spreadsheet, listing orders that are unpaid, partially paid, or pending payment. The resulting report is emailed to the recipient of your choice. Optionally, choose to have this report generated hourly, or daily.
Runs Occurs when a user manually triggers the task. Configuration includes include closed orders, recipient email address, email subject, email body, csv attachment filename, run hourly, and run daily.
Stay on top of chargebacks and inquiries! Nightly or on-demand, this task will scan the last 60 days of your order records, and apply the tags of your choice to orders with chargeback or inquiry activity, based on what that activity looks like.
Runs Occurs when a user manually triggers the task and Occurs every day at midnight (in local time). Configuration includes tag for any, tag for accepted, tag for charge refunded, tag for lost, tag for needs response, tag for under review, and tag for won.
Using Shopify's multi-locations feature, and importing products in bulk? Use this task to automatically connect each new product to every location for your store.
Runs Occurs whenever a product is created.
Some themes (like Mogo!) support browsing products by price range. Under the hood, this functionality is powered by tags that look like "rprice-1-100". This task watches for new and updated products, making sure that the product range tags stay in sync with prices available for each product.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes tag prefix, range maximum, range minimum, range increment, use only the single smallest range that applies to each variant, and use every range that applies to each variant.
Save time jumping between screens, by making sure that the order record has everything you need. Useful for shops that keep important fulfillment information in the customer notes. This task can be run manually to back-fill notes for open orders.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task.
Use this task to quickly (and permanently) clear out your product list. Optionally, filter by a specific query, so as to only delete specific products from your store. Supports a test mode, allowing you to see exactly what products you can expect Mechanic to delete.
Runs Occurs when a user manually triggers the task. Configuration includes query, test mode, and live mode.
Does exactly as it says. :)
Runs Occurs whenever an order is updated. Configuration includes tags to watch for and tags to add and remove tag to add when the corresponding tag to watch for is removed.
This task watches for new orders, and tags each order with all line item SKUs found in that order.
Runs Occurs whenever an order is created.
This task watches for updates to customers, and sends invites for any customer who has the tag you choose, who hasn't previously been invited. If you'd like to run this task in bulk, you can find that version of the task here.
Runs Occurs whenever a customer is created and Occurs whenever a customer is updated. Configuration includes tag to watch for, ignore tag case, invitation email subject, and invitation email body.
This task watches for order cancellations, and adds or removes tags according to your preference. Run this task manually to update tags for existing cancelled orders.
Runs Occurs whenever an order is updated and Occurs when a user manually triggers the task. Configuration includes tags to add and tags to remove.
Use this task to auto-tag customers whose marketing preferences have been updated, adding a tag for those that do accept marketing and removing it from customers who do not. Optionally, choose whether to limit tags to customers who have single or confirmed opt-in levels. Run this task manually to scan all customers at once.
Runs Occurs whenever a customer is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes customer tag to add, only tag confirmed opt ins, and tag both single and confirmed opt ins.
This task monitors order tags, and sends out an email that you configure whenever a certain tag is added. Supports email templates, and sending to custom recipients.
Runs Occurs whenever an order is updated. Configuration includes email trigger tag, email sent tag, email subject, and email body html.
This task runs when an order is created and captures any authorized transactions, based on the configured risk levels. Optionally choose to filter orders for capture by a tag.
Runs Occurs whenever an order is created, with a 0 minute delay. Configuration includes minutes to wait before capturing, filter orders by this tag, capture orders with a high risk level, capture orders with a medium risk level, and capture orders with a low risk level.
This task watches for product and inventory item updates, and sends an email to the configured recipients for each variant that's found to have a unit cost that's greater than the variant's for-sale price.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated and Occurs whenever an inventory item is updated, with a 15 second delay. Configuration includes recipient emails.
This task will allow you to schedule any number of themes to be published at future dates and times. When the task runs at its normally scheduled 10 minute interval, it will find the entry with the most recent configured date in the past, and if that theme is not currently published, then the task will publish it.
Runs Occurs every 10 minutes and Occurs when a user manually triggers the task. Configuration includes theme ids and publish dates.
This task monitors newly-created orders, and appends an order note if that order was created with a certain tag.
Runs Occurs whenever an order is created. Configuration includes required order tag and order note to add.
This task script demonstrates using the "http" action to retrieve external data, using a GET request. It also demonstrates saving the retrieved data to the Mechanic cache, where it can be used for future task runs.
Runs Occurs when a user manually triggers the task and Occurs when a Mechanic action is performed. Configuration includes save data to cache.
Use this task to automatically add product bundle components to qualifying paid orders, by configuring the task with a bundle parent SKU, unique SKUs for the bundle components, and with quantities needed from each component for each bundle parent unit. The bundle components will be added to the order at a 100% discount, and the order's subtotal will be unaffected.
Runs Occurs when a user sends an order to Mechanic and Occurs when a Mechanic action is performed. Configuration includes bundle parent sku, component skus and quantities per bundle, discount message to display on each added component, staff note for the order edit, alert email recipients, and manual mode.
This task runs daily to maintain tags for any customers that have a certain spending threshold within a rolling period of order history. Useful for rewarding customers who keep a consistent spend total. Select to have the rolling spend calculated using either "Total sales" (net sales + additional fess + duties + shipping charges + taxes) or only "Net sales" (gross sales - discounts - returns).
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes sales calculation to use, minimum total spent, customer tag to apply, days of order history to consider, only monitor customers having this tag, run hourly instead of daily, and test mode.
Useful for flagging orders for manual follow-up, for stores that see fraudulent activity in which billing and shipping address are not the same.
Runs Occurs whenever an order is created. Configuration includes order tag to add.
Use this task to rapidly update your order list, by entering a set of order names (e.g. "#12345", often called order numbers) and the tags to apply to those orders.
Runs Occurs when a user manually triggers the task with text.
Just as it says. :) Archives orders immediately upon fulfillment, or after a configurable number of days.
Runs Occurs whenever an order is fulfilled. Configuration includes days to wait after fulfillment before archiving.
Use this task to automatically set product inventory to 0, and the product's inventory policy to deny out-of-stock purchases, after a date/time that you specify in a product metafield.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes product metafield, run hourly, and run daily.
Shopify allows orders to have custom attributes associated with them – and these attributes can be edited from within Shopify. Use this task to configure default attributes to be added to all new orders, providing an attribute name and (optionally) a value. Feel free to leave the value blank if you know you'll want to add your own values later, within Shopify.
Runs Occurs whenever an order is created. Configuration includes default order attributes to add.
This task runs when customers are created, and it applies a tag if they have one of the configured email domains.
Runs Occurs whenever a customer is created and Occurs when a user manually triggers the task. Configuration includes customer email domains and customer tag to apply.
Use customer tags to assign staff email addresses to specific customers. When a new order arrives from a customer who has an assignment tag, this task will email the related staff member.
Runs Occurs whenever an order is created. Configuration includes customer tags and assigned email recipients, email subject, and email body.
This task monitors newly-created orders, and appends an order note if the customer has a certain tag. Useful for identifying orders for a particular customer group, and adding fulfillment notes as appropriate.
Runs Occurs whenever an order is created. Configuration includes required customer tag and order note to add.
Use this task to tag incoming customers with the current date/time, using the format of your choice, and optionally a prefix and suffix. If you like, enable "Wait until the customer is enabled" to apply the tag when the customer's online account is activated, rather than when the customer is first created.
Runs Occurs whenever a customer is created and Occurs whenever a customer is created. Configuration includes tag date format, tag prefix, tag suffix, and wait until the customer is enabled.
Quickly route order notifications to whichever teams need be alerted for a given order. Use product tags to mark products according to which team needs the alert, and add multiple copies of this task to alert different teams for different tags.
Runs Occurs whenever an order is created. Configuration includes required product tag, team email, email subject, and email body.
Use this task to automatically tag incoming orders with the vendor of each product in the order.
Runs Occurs whenever an order is created and Occurs when a user sends an order to Mechanic.
Use this task to send a follow-up email, 24 hours after you send out an email invoice for a draft order. Optionally, set this task to continue sending follow-up messages, every day after that.
Runs Occurs whenever user/draft_orders/followup is triggered, with a 24 hour delay and Occurs whenever a draft order is updated. Configuration includes send daily emails, email subject, and email body.
This task populates variant metafields with your desired variant options for use by Online Store 2.0 filtering, taking into account whether or not a variant has inventory available for sale online. It runs when inventory levels are updated, and may also be run manually to scan all variants in your shop.
Runs Occurs whenever an inventory level is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes metafield namespace and option names and metafield keys.
This task monitors for newly-created orders, and auto-tags any that were originally based on a Shopify draft order, using the tag of your choice.
Runs Occurs whenever an order is created. Configuration includes tag to add.
This task monitors changes to inventory level, records the time at which a product's total inventory passes your configured threshold, and then maintains a set of tags indicating how recently the product returned to "back in stock" status.
Runs Occurs whenever an inventory level is updated, Occurs every day at midnight (in local time), Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes back in stock inventory level, product tags and maximum age in days, include new products, run hourly, run daily, and force usage of creation date on manual runs.
With no configuration, this task will delete all product or variant metafields. Configure it with a metafield namespace to only delete metafields with that namespace, or add both a namespace and key to get even more specific. Run this task with the test mode option enabled, the first time, to make sure you're deleting the right material.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes delete product metafields, delete variant metafields, metafield namespace, metafield key, and test mode.
When an order is fulfilled, this task will scan the tracking information for each fulfillment. The name of each tracking company on file – i.e. the fulfillment carrier – will then be added to the order as a tag.
Runs Occurs whenever an order is fulfilled.
Use this task to monitor for orders that meet a certain quantity threshold, per line item or totaled up, optionally only looking at certain SKUs. Optionally, send yourself an email notification when such an order comes in.
Runs Occurs whenever an order is paid. Configuration includes minimum quantity threshold, evaluate threshold per line item, only monitor these skus, order tag to apply, and email notification recipient.
This task formats the publish date of a product (according to the format you choose), adds a prefix (also of your choosing), and applies it as a tag to the product. Run this task manually to scan your entire catalog of active products, or wait for the task to run automatically when products are created or updated.
Runs Occurs when a user manually triggers the task, Occurs whenever a product is created, and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes date format and tag prefix.
Configure this task with a customer tag, and Mechanic will take care of applying it to your customers as soon as their order payment goes through. Easy as that. :)
Runs Occurs whenever an order is paid. Configuration includes customer tag.
Immediately upon the creation of a draft order, add one or more tags. Simple as that. :)
Runs Occurs whenever a draft order is created. Configuration includes draft order tags to add.
Run this task to scan all of your customers and their order histories, copying order and/or product tags to the relevant customer. Optionally, configure a specific set of tags to look for, when scanning. Optionally, choose to remove those tags if a qualifying source can't be found.
Runs Occurs when a user manually triggers the task. Configuration includes include order tags, include product tags, only include customers matching this query, only include orders matching this query, only copy these tags, remove those tags if a qualifying source cannot be found, and run daily.
This task will run daily to query all customers in your shop who have placed an order, tagging each with whichever configured tag is paired with the closest "days since last order" threshold. This is great way to keep tabs on who is active in your store, and who you might need to reconnect with.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes customer tags and days since last order and create customer segments by tag.
This task runs when products are created or updated and manages publishing to the configured sales channels, according to whether or not the product has a certain tag. Products with the tag will be published on ALL of the configured sales channels; and those without the product tag will be unpublished from them.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes sales channel names and product tag.
Use this task to send a quick welcome email to customers, when they sign up or are otherwise created in your shop. Optionally, filter by customer tag to only send welcome emails to certain customers.
Runs Occurs whenever a customer is created. Configuration includes required customer tag, email subject, and email body.
This task applies the tag of your choice to orders, based on the highest risk level for each order. Run this task manually to tag all open orders in your shop, according to their respective risk levels.
Runs Occurs whenever an order is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes risk levels and tags.
Just as it says. Useful for collections that can't be configured for automatic products, but still should have some products pulled in automatically.
Runs Occurs whenever a product is created and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes product tags and collection ids.
Use this task to perform an extra verification step for your newly-created customers, in which a verification code is emailed to them, along with a link to a form on your online storefront where they can enter the code for verification. Once verified, the customer will be tagged, and sent a confirmation email.
Runs Occurs whenever a customer is created and Occurs whenever user/customers/verify_webhook is triggered. Configuration includes tag to add after verifying, verification email subject, verification email body, verification confirmed email subject, verification confirmed email body, and verification webhook event topic.
Get an alert email sent to you when your tracking service reports a fulfillment failure. This email contains a link to the order details, so you can jump in and resolve the issue for the customer without losing any time.
Runs Occurs whenever a fulfillment event is created. Configuration includes email recipient.
This task will scan your entire catalog to maintain products in collections based on metafield values. Configure the task with a metafield namespace and key (separated by a period, e.g. "custom.color"), and a list of metafield string values paired with collection IDs. If the value of a product's metafield matches any of the configured ones, then the product will be added to that collection. Conversely, products in a configured collection which do not match a metafield value will be removed.
Runs Occurs when a bulk operation is completed, Occurs every day at midnight (in local time), and Occurs when a user manually triggers the task. Configuration includes metafield namespace and key and metafield values and collection ids.
This task scans all orders, regardless of status, and counts up the lifetime quantity purchased for each SKU, listing each SKU with its quantity and all related order names. This task demonstrates Shopify's bulk operations API.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed.
When an inventory level is updated, this task will adjust the "available" inventory for all other locations of the same variant to be the same quantity. Optionally, configure this task to filter for specific product types. Leaving this option blank means the task will monitor and update inventory for all products in the shop.
Runs Occurs whenever an inventory level is updated. Configuration includes filter by these product types.
This is the companion task for the Triggering tasks from a contact form tutorial.
Runs Occurs whenever user/webhook/form is triggered. Configuration includes recipient email address, email subject, email body, csv attachment filename, and mechanic webhook url.
Use this task when the pricing for your products can be automatically calculated by multiplying with compare-at prices.
Runs Occurs when a user manually triggers the task. Configuration includes multiplier when calculating price, product tag to monitor, only process active products, run automatically for product updates, run daily, and test mode.
Order Tracking with Google Sheets (Demonstration)
Runs Occurs when a user manually triggers the task, Occurs whenever an order is created, and Occurs when a Mechanic action is performed. Configuration includes google account, spreadsheet title, spreadsheet id, email address for export, file format for export, create sheet mode, and export sheet mode.
On a configurable schedule, this task generates a Shopify-friendly CSV of your inventory, and uploads it to the SFTP destination of your choice, and/or sends it via email. This is a convenient way to keep regular backups of your entire product inventory: simply import a CSV to restore your inventory to that point in time. (Learn more about CSV imports and exports of Shopify inventory.)
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes only export products matching this query, run every x hours, sftp host, sftp port, sftp user, sftp password, sftp upload directory, and send email export to this address.
Use this task to auto-tag customers when their historical purchase total falls within a certain range. For example, by configuring this task to evaluate purchase thresholds by number of orders, and by setting the minimum to "1" and the maximum to "12", this task will auto-tag customers who've made at least 1 purchase, and will remove the tag when the 13th purchase is made.
Runs Occurs whenever an order is created and Occurs whenever an order is cancelled. Configuration includes purchase minimum, purchase maximum, evaluate purchase thresholds by number of orders, evaluate purchase thresholds by adding line item quantities, evaluate purchase thresholds by adding line item subtotals, only count paid orders, only count this product id, and customer tag to apply.
Using Judge.me for reviews? Use this task to keep a counter for each customer's reviews, stored as a metafield on the customer record. And, auto-tag customers as they reach different levels of review counts - useful for granting discounts or special access to repeat reviewers.
Runs Occurs when a Judge.me review is created. Configuration includes metafield namespace, metafield key, and tags to apply for review counts.
Use this task to keep track of who created what order. This task watches for new orders, that are created by store staff members, auto-tagging each new order with the name of the user who created it. Run this task manually to scan and tag all existing orders in your store.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes tag prefix and include pos orders.
After waiting 7 days (or another timespan of your choice), this task attempts to capture all open authorized payments for an order. (Multiple authorizations can exist on edited orders or with post-purchase upsells.)
Runs Occurs whenever an order is created, with a 7 day delay. Configuration includes days to wait before capturing.
This task demonstrates how to use the four Mechanic Shopify Flow triggers: General, Customer, Product, and Order.
Runs Occurs when a user manually triggers the task, Occurs whenever user/flow/customer is triggered, Occurs whenever user/flow/order is triggered, Occurs whenever user/flow/product is triggered, and Occurs whenever user/flow/general is triggered. Configuration includes customer id, order id, product id, and send general trigger.
When an order is cancelled, this task waits 48 hours, and then permanently deletes the order. Simple as that! (Please note: if you only want to archive the cancelled order, not delete it, try a different task!)
Runs Occurs whenever an order is updated and Occurs whenever user/orders/delete_cancelled is triggered, with a 48 hour delay.
Use this task to easily set the shipment status on your fulfilled orders. Just add a tag, and new fulfillment events will be created, using the corresponding shipment status. Optionally, you may have the task attempt to fulfill the order first and may choose whether to send shipment status notifications to the customer.
Runs Occurs whenever an order is updated. Configuration includes shipment tags and status, attempt to fulfill the order before setting shipment status, and send shipment notifications to customer.
Use this task to quickly designate certain orders to be automatically marked as paid. Runs for orders as they're created and updated, and can also be run manually, to scan all orders in your store at once.
Runs Occurs whenever an order is created, Occurs whenever an order is updated, and Occurs when a user manually triggers the task. Configuration includes required order tag and test mode.
Running daily or manually, this task scans all customers who have placed orders and tags them based on the date of their last order. Choose between tagging customers whose orders are before x days ago, or after x days ago.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes days since last order, tag customers when last order is after, tag customers when last order is before, customer tag to apply, and run daily.
Use this task to automatically tag customers when they purchase specific a membership product, and then untag them after a certain amount of time has passed! (Optionally, this task can also automatically untag the customer if/when their membership order is cancelled.)
Runs Occurs whenever an order is paid and Occurs whenever user/memberships/expire is triggered. Configuration includes membership product title, membership tag, days to wait before untagging, and remove tag immediately for cancelled orders.
This task runs when inventory level changes occur at a configured location in the task, and it will check the stock status across all of that product's variants at each configured location. If the variants are all out of stock at a location, the task will unpublish the product from each catalog associated with each configured market for that location, thus denying the product from online sale in those markets. On the flipside, the task will publish a product to the related market catalogs if any of its variants are in stock at any of the configured locations for a market.
Runs Occurs whenever an inventory level is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes locations and market names, ignore products with any of these tags, ignore variants that do not track inventory, and ignore variants that are configured for overselling.
This task script demonstrates using the "http" action to retrieve data from a shared Google sheet, using a GET request. It also includes a basic alert email that will be sent to the configured recipients if Mechanic is unable to access the shared sheet as a CSV.
Runs Occurs when a user manually triggers the task and Occurs when a Mechanic action is performed. Configuration includes gsheet url and alert email recipients.
Add a tag, have the order automatically archived/closed. Simple. :)
Runs Occurs whenever an order is created, Occurs whenever an order is updated, and Occurs when a user manually triggers the task. Configuration includes required tag and allow manual unarchiving of orders.
This task automatically tags orders based on the city in the shipping address. Within this key you define the city and the tag on the order.
Runs Occurs whenever an order is created. Configuration includes city and tag to apply.
This task monitors incoming orders, and tags them with information about the customer's web browser.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes include browser version.
This task resets your inventory levels at the default location in your shop, every night, for all products within a given collection.
Runs Occurs every day at midnight (in local time). Configuration includes inventory level to apply and collection.
This task monitors for newly-created draft orders, and converts each one into a completed order. Nothing more, nothing less. :)
Runs Occurs whenever a draft order is created. Configuration includes mark new orders as fully paid.
This task sends an email notification, immediately after an order is paid - if a product in the order has a title matching the product title you configure. Optionally, configure this task with a delay, in days, to wait before sending the email. (The task will not send any emails for orders that have since been cancelled.)
Runs Occurs whenever an order is paid. Configuration includes product title, email address, email subject, email body, reply to email address, and number of days to wait before emailing.
On a configurable schedule, this task generates a Shopify-friendly CSV of all your products, and uploads it to the SFTP destination of your choice. This is a convenient way to keep regular backups of your entire product catalog: simply import a CSV to restore your products to that point in time. (Learn more about CSV imports and exports of Shopify products.)
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes only export products matching this query, run every x hours, sftp host, sftp port, sftp user, sftp password, and sftp upload directory.
Use this task with services that add tracking numbers to fulfillments after fulfillments are created, to ensure that customers are notified when their tracking number is available.
Runs Occurs whenever a fulfillment is created and Occurs whenever a fulfillment is updated. Configuration includes email subject and email body.
This task watches for new and updated products, copying variant barcodes over to the variants' inventory item SKUs. This occurs whenever a barcode is found, and the related SKU does not already have that value.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed.
This task will watch for new order fulfillments, waiting a configurable number of days after each one. When the waiting period is over, if the fulfillment's status matches an item in the list, this task will send an event to Klaviyo, allowing you to use Klaviyo to contact the customer appropriately.
Runs Occurs whenever an order is fulfilled, with a 5 day delay. Configuration includes qualifying fulfillment statuses, klaviyo api token, klaviyo event name, days to wait before checking, and test mode.
Use this task to sell a single product in different pack sizes, keeping available inventory levels synchronized appropriately, storing the "main" inventory level in a product tag (e.g. "inventory:50").
Runs Occurs whenever an order is created, Occurs whenever a product is created, and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes product inventory tag prefix, variant pack size option name, variant pack size metafield namespace dot key, and run when orders are paid instead of when they are created.
Do you wish Shopify Flow workflows could run on historical data? Now they can! :D
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes start date, end date, and flag value.
Use this task to send yourself a quick tally of everything currently waiting in your order list. Super simple: just a list of products, and how many of each were ordered.
Runs Occurs every Monday at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes only include open orders, only include fully paid orders, only include fully unfulfilled orders, count quantities by variant instead of by product, email recipient, email subject, day of week to send email, and allow sending manually.
Does exactly as it says. :)
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes product tag to watch for, product tag to remove, and ignore tag case.
Use this task to auto-reserve all of the line items for a set amount of time on qualifying new or updated draft orders. A common use case is when you have an app or service that is creating draft orders on your behalf and you want to make sure that the inventory for those orders is set aside if possible.
Runs Occurs whenever a draft order is created and Occurs whenever a draft order is updated, with a 10 second delay. Configuration includes amount of days to reserve, include draft orders with any of these tags, and exclude draft orders with any of these tags.
This task automatically removes specific order tag(s) when orders are paid.
Runs Occurs whenever an order is paid. Configuration includes order tags to remove.
This task works by setting your inventory to zero when the order limit is reached. (Specifically, this means setting inventory levels to 0 for all items that have a greater-than-zero inventory level.) When the limit is reached, your inventory will be dropped to zero. If your store is configured to stop selling out-of-stock products, your customers will be prevented from making additional purchases.
Runs Occurs whenever an order is created and Occurs every day at midnight (in local time). Configuration includes maximum daily orders, only count orders matching this query, only clear inventory for products with this tag, restore inventory levels the next day, and restore inventory levels on demand.
Use this task to automatically maintain minimum inventory levels. Optionally, filter by variant or product ID, or by variant option, or by product type, choosing whether to blacklist or whitelist your filter selections.
Runs Occurs whenever an inventory level is updated. Configuration includes minimum inventory level, location id, whitelist filter mode, blacklist filter mode, filter for these variant ids, filter for these variant options, filter for these product types, and filter for these product ids.
Useful for selling, say, a limited print with different framing options, this task makes sure that a product's inventory levels, for each variant and location, are all kept in sync.
Runs Occurs whenever an inventory level is updated. Configuration includes filter by these location names and filter by these product types.
This task tags customers with the name of each vendor in their order, as soon as the order is created. Useful for keeping track of which vendors a customer is interested in. :)
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed.
Use this task to keep an eye on the contents of a customer's note. When the text you want to watch for is added (e.g. "Authorization number:", or "VAT Registration Number:", or anything else!), Mechanic will add the tag of your choice to the customer, and optionally send you a notification email.
Runs Occurs whenever a customer is created and Occurs whenever a customer is updated. Configuration includes text to watch for in the customer note, require a case sensitive match, customer tag to apply, and staff notification email recipient.
Use this task to receive immediate email notifications whenever inventory/stock levels are adjusted, whether manually or as a result of a transfer or customer order.
Runs Occurs whenever an inventory level is updated and Occurs whenever an inventory level is connected. Configuration includes email recipient, email subject, and email body.
This task monitors customer tags, applying tax-exempt status when a certain tag is detected, and removing it (and the tag) after a certain amount of time. Useful when you need to regularly re-approve customers for tax exemption.
Runs Occurs whenever a customer is updated and Occurs whenever user/customers/expire_tax_exempt is triggered. Configuration includes tax exempt tag and days before removing tax exempt status.
This task searches for draft orders having the configured tag, and duplicates each one (minus the tag used for searching). Optionally, this task can automatically send an invoice to the customer on file, after the new draft order is created. Or, this task can auto-complete the draft order, which will mark it as paid unless the original draft order being duplicated has NET or EVENT payment terms.
Runs Occurs when a user manually triggers the task and Occurs every day at midnight (in local time). Configuration includes draft order tag, cycle start date, number of days in cycle, complete the order after creating, send email invoice after creating, email invoice subject, email invoice bcc, and email invoice custom message.
Activating this task will automatically keep the order tags up to date with the customer's tags.
Runs Occurs whenever a customer is updated.
This task scans all customers and their orders, and copies any new timeline comments to the customer's note. Any existing content in the customer note will be preserved; each new comment will be added to the end of the note (or, optionally, to the beginning). Any edited timeline comments will be added as new note lines during the next scan.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes add new comments to the beginning, do not add removed comments back in, comment date format, automatically trim notes after a one day warning, send errors to slack, slack incoming webhook url, run hourly, and run daily.
This task watches for newly-paid orders, and tags any that include a customer tip, using the tag of your choice. :)
Runs Occurs whenever an order is paid. Configuration includes tag for orders that have a tip.
This task watches for cancellations of orders that have either a single-use discount code, or a discount code that can only be used once per customer. When such an order is found, this task creates a new copy of the discount exclusively for the related customer, using a new discount code, and emails it to the customer.
Runs Occurs whenever an order is cancelled. Configuration includes ignore discount codes containing this text, email subject, email body, and email bcc.
Purely for demonstration purposes, this task illustrates how one might set up a script to send Slack messages. As written, this task requires a Slack incoming webhook URL - learn how to generate this. Then, learn more about sending to Slack with Mechanic.
Runs Occurs when a user manually triggers the task. Configuration includes slack incoming webhook url.
This task appends order notes to the related customer's note, whenever the order note changes.
Runs Occurs whenever an order is updated. Configuration includes note prefix.
Use this task to easily keep track of orders placed by customers that already have at least one unpaid order. When new orders are created and the customer has any existing authorized, partially paid, or pending payment orders, then the new order will get the configured tag.
Runs Occurs whenever an order is created. Configuration includes order tag to apply and exclude company purchases.
When a new order is created, this task will tag all open orders for the customer which match the new order's shipping address, giving you the potential to combine shipments.
Runs Occurs whenever an order is created. Configuration includes tag to apply.
Use this task to regularly scan for repeat orders from a single IP address, by tagging any orders from an IP address that's placed more than a configurable threshold of orders in the last x days of order history.
Runs Occurs when a user manually triggers the task. Configuration includes days of order history to scan, threshold order count per ip address, order tag to apply, run every 10 minutes, run hourly, and run daily.
Get an email alert whenever a product is created, updated, or deleted. This makes it easy to keep tabs on updates to your catalog – useful if you need a precise audit trail.
Runs Occurs whenever a product is created, Occurs whenever a product is deleted, and Occurs whenever a product is updated, ordered, or variants are added, removed or updated. Configuration includes recipient email.
This task demonstrates how to move line items from their assigned fulfillment location to another. Configure it with the SKUs that should be moved and the name of location they should be moved to. Then, when new orders are created, if any of the configured SKUs appear on a line item that is assigned to any other location besides the configured one, the task will move it.
Runs Occurs whenever an order is created and Occurs when a user sends an order to Mechanic. Configuration includes skus to move and move to location name.
Use this task to tag customers, as their orders come in, based on which sales channel they used for their purchase. Run this task manually to backfill tags for customers based on their historical orders. Use test mode to see what this task would do, if test mode wasn't enabled.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes sales channel names and tags and test mode.
This task will remove order attributes from newly created or paid orders after a configurable amount of minutes. This can be helpful when order attributes are set by apps or other processes that are not necessary to keep on the order after initial processing.
Runs Occurs whenever an order is created, with a 15 minute delay. Configuration includes minutes to wait before removing order attributes, order attributes to remove, remove all order attributes, and only run for paid orders.
This task monitors for new and updated orders, adding a tag if a certain other tag is found missing. If and when the order does receive that certain other tag, the task's tag will be removed.
Runs Occurs whenever an order is updated. Configuration includes order tag to watch for and order tag to add.
Are you using Locksmith for access control on your online store? Use this task to tag customers with the passcode keys they've used.
Runs Occurs when Locksmith sends a session ping. Configuration includes echo all locksmith session pings.
Do you sell tickets to recurring events? Do you use a new product variant for each one? Use this task to regularly scan your catalog for product variants that have a date metafield, and to delete variants when their date has passed.
Runs Occurs when a user manually triggers the task, Occurs every day at midnight (in local time), and Occurs when a bulk operation is completed. Configuration includes date metafield namespace and date metafield key.
This task will monitor incoming orders for any products that are included in the collection you choose. Learn where to find the collection ID.
Runs Occurs whenever an order is paid. Configuration includes required collection id, email address, email subject, and email body.
This task monitors for new refunds. When a new refund changes an order's status to fully refunded, this task will cancel all fulfillments for that order. This task supports running manually, to cancel all fulfillments for refunded orders, across your store's order history.
Runs Occurs when a user manually triggers the task and Occurs whenever a new refund is created without errors on an order, independent from the movement of money. Configuration includes cancel pending fulfillments, cancel open fulfillments, and cancel successful fulfillments.
This task generates a brand new discount code (copying configuration from another code, of your choice), and emails it to the customer, after waiting a configurable number of days after order fulfillment.
Runs Occurs whenever an order is fulfilled, with a 14 day delay. Configuration includes days to wait after order fulfillment, source discount code for cloning, override source with this discount validitity period in days, new discount code prefix, email subject, email body, and email bcc.
This task watches new and updated orders, and updates their tags according to their financial status.
Runs Occurs whenever an order is updated. Configuration includes financial statuses and tags and remove outdated financial status tags.
Keep track of which products in your shop have incoming inventory with this task! Running when inventory levels are updated, this task will tag the product with the tag of your choice if any of that product's variants at any of your locations has an incoming transfer. Conversely, the tag will be removed when there are no pending transfers.
Runs Occurs whenever an inventory level is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes product tag to apply and run on a schedule.
When new orders are created, this task will check to see if any of the configured metafields are set on the customer who placed the order, and if so then it will add order tags based on the metafield values.
Runs Occurs whenever an order is created and Occurs when a user sends an order to Mechanic. Configuration includes metafields and tag prefixes and truncate long tags.
When a new order is created from a draft order, this task will automatically add the draft order ID and/or name to the custom attributes of the new order.
Runs Occurs whenever an order is created. Configuration includes order attribute name for storing the draft order id and order attribute name for storing the draft order name.
Useful for stores that are subjected to bot abuse, this task watches for newly-created customers, and deletes any that don't come with an associated order. Optionally, choose to ignore any customers that are created with a certain tag – helpful if you create customers yourself, via the Shopify admin.
Runs Occurs whenever a customer is created. Configuration includes ignore customers having this tag.
When a customer update occurs, if the customer has a phone number on file, this task will look for unshipped or partially shipped orders that don't yet have a phone number on file, and will add the customer's phone number to those orders.
Runs Occurs whenever a customer is updated.
This task monitors for incoming mail, sent directly to your Mechanic account, and forwards all of it (including attachments) to the address of your choice. (Note that only emails less than 10MB in total size will be sent.)
Runs Occurs when your Mechanic account receives an email. Configuration includes email recipient.
This task demonstrates how to write to a Shopify metafield, belonging to a specific resource - in this case, a customer.
Runs Occurs when a user manually triggers the task. Configuration includes customer id, customer metafield, metafield value, and mutation choice.
Useful for quickly preparing labels, or planning a drop-off route.
Runs Occurs when a user manually triggers the task. Configuration includes orders search query, include name in formatted address, include company in formatted address, and csv email recipient.
This task watches for newly-paid orders, and adds a configurable tag to each one.
Runs Occurs whenever an order is paid. Configuration includes order tag to apply.
Monitoring for brand-new orders, this task add a note to each order with the fulfillment locations that Shopify automatically assigns at the moment of order creation.
Runs Occurs whenever an order is created.
This task demonstrates how one might use the Files action to generate a file, using the fileCreate GraphQL mutation to transfer the resulting file to Shopify for storage.
Runs Occurs when a user manually triggers the task and Occurs when a Mechanic action is performed.
This task watches incoming orders, and tags each order with a certain value from the customer's note, as identified by a configurable prefix. For example, if your customers have notes resembling "Username: xyz", configure this task with the prefix "Username: " to have it tag incoming orders as "xyz". Useful with apps like inkFrog, which add eBay usernames to customer notes, using a prefix.
Runs Occurs whenever an order is created. Configuration includes tag prefix in customer note.
A utility task, this one is useful for those one-off moments when your inventory needs a clean slate. Run this task manually to reset all of your inventory, across your entire store and for all locations, to the single level of your choice. No exceptions, no filters.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes reset all inventory items to this level.
This task will maintain a variant list metafield of in stock location names. Running on a schedule, it will check recently updated variants to see which are in stock at each location. Variants with positive "available" inventory at a location, or are configured for overselling, are considered to be in stock, as are variants that are sold from a location but not tracked.
Runs Occurs every hour and Occurs when a user manually triggers the task. Configuration includes variant metafield, include location names, exclude location names, run every 10 minutes, run hourly, and run daily.
Use this task to tag incoming orders that contain subscription products. This task can also be run manually to scan and tag historical orders.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes tag to apply.
This task offers an introduction to using Liquid to dynamically update your orders. This task comes with example Liquid code, showing you how to tag an order as "even" or "odd", based on whether the order number is even or odd; replace this Liquid with whatever suits your purposes. :)
Runs Occurs whenever an order is created. Configuration includes order tag value.
Need to reach customers who made a specific purchase? This task scans your order history, looking for orders that match the conditions you specify. For each qualifying order, the task sends an email to the customer, optionally linking to the product(s) ordered.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes search query for orders, product ids to look for, variant ids to look for, email subject, email body, add this tag to matching orders, test mode, and i certify that messages sent here are related to customer activity.
Need to print price tags whenever a SKU is added? Or make a note of a new variant price? Use this task to tag products that need your attention, whenever a specific variant attribute changes.
Runs Occurs whenever a product is created, Occurs whenever a product is updated, ordered, or variants are added, removed or updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes variant attribute to watch for changes, tag product with the titles of each variant that has changed, product tag to add, and ignore products with any of these tags.
Use this task to easily keep track of who's responsible for which orders. Works for draft orders, too!
Runs Occurs whenever an order is created and Occurs whenever a draft order is created. Configuration includes tag orders, tag draft orders, and staff names and tags.
Use this task to immediately bump orders, from certain customers, to "paid". Useful if you have a standing payment arrangement for certain customers. Optionally, auto-remove this tag from customers after auto-paying their order. Useful for using customer tags as one-time triggers for auto-payment.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes required customer tag and remove tag from customer after processing their order.
Use this task to send email notifications whenever discounts are created in your shop. Optionally, you may choose to monitor when specific apps create discounts.
Runs Occurs whenever a discount is created. Configuration includes email recipients and app names to monitor.
With no configuration, this task will delete all customer metafields in bulk. Configure it with a metafield namespace to only delete metafields with that namespace, or add both a namespace and key to get even more specific. Run this task with the test mode option enabled, the first time, to make sure you're deleting the right material.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes metafield namespace, metafield key, and test mode.
Some apps are responsible for placing orders. Use this task to tag orders, both incoming and historical, based on which app was responsible for placing them.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes app titles and order tags and test mode.
This task watches for incoming orders for the United Kingdom, and reformats any address postcodes that are not in the standard formats "XX XXX", "XXX XXX", and "XXXX XXX".
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes standardize billing postcodes, standardize shipping postcodes, and only scan open orders when running manually.
Use this task to automatically add variants to the configured delivery profile on product update, if any of the variants have a metafield value matching the configured value. Conversely, variants with a non-existant or mismatched metafield value that are in the configured delivery profile will be removed.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated and Occurs when a user manually triggers the task. Configuration includes metafield namespace and key, metafield value to match, and delivery profile id.
This task runs across all active products on your store and syncs a list type product reference metafield to contain all products with a matching common single metafield value (the 'group by' meatfield).
Runs Occurs every day at midnight (in local time), Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes group by metafield namespace, group by metafield key, product list metafield namespace, product list metafield key, remove out of stock products, and include current product.
When an order is created, this task adds the location name of the purchase to the customer's tags. Useful for stores with multiple Shopify-powered POS locations.
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes tag for online orders.
Shopify's customer group filters allow you to filter by the tags the customer contains – but not the tags a customer does not contain. Use this task to sync an "inverse" tag to all customers who do not have a particular tag, allowing you to filter customers in Shopify by that inverse tag.
Runs Occurs whenever a customer is created, Occurs whenever a customer is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes customer tag to watch and customer tag to use when missing.
This task demonstrates how a report can be requested from Report Toaster as a PDF. Once delivered, it is emailed to one or more recipients and/or sent to a Slack channel.
Runs Occurs when a user manually triggers the task and Occurs when a Report Toaster report is created. Configuration includes report id, email report recipients, slack incoming webhook url, message body, and run this task daily.
Use this task to generate discounts for future purchases. When a customer buys a "voucher" product, they will be emailed a single-use discount code for either a fixed amount of money or percentage off a purchase on a corresponding "entitled" product".
Runs Occurs whenever an order is paid and Occurs when a Mechanic action is performed. Configuration includes voucher product ids and entitled product ids, discount code prefix, discount fixed amount, discount percentage, email subject, and email body.
This task allows you to send an email to someone when a certain variant is purchased. Requires the variant ID.
Runs Occurs whenever an order is paid. Configuration includes email address, email subject, email body, reply to email address, and variant id.
Use this task to email donation receipts to donors as PDF attachments, with an option to cc the shop email. It runs on new, paid orders, or optionally on order creation. The task will sum the donation amount from all line items that have any of the configured donation product tags or titles.
Runs Occurs whenever an order is paid and Occurs when a user sends an order to Mechanic. Configuration includes tax id, run on order creation instead of paid, identify donation products with any of these tags, identify donation products with any of these titles, send cc to shop email, email subject, email body, donation receipt filename, and donation reciept html template.
Use this task to request or schedule an email digest of customers, having a certain tag, who haven't placed an order in a certain number of days.
Runs Occurs when a user manually triggers the task. Configuration includes required customer tag, include customers who have not placed an order in this many days, email subject prefix, email recipient, send email anyway if no customers are found, send email daily, and send email every monday.
This task allows you to receive an email alert for any event topic supported by Mechanic. Configure the task with a list of email addresses to notify, an email subject, and one or more event topics, each paired with an email body that supports liquid output tags for the main object of each event (e.g. shopify/products/create can use attributes like {{ product.id }} or {{ product.title }})
Runs Occurs whenever a product is created and Occurs whenever a customer is created. Configuration includes emails to notify, general email subject, append event topic to email subject, and event topics and email bodies.
This task makes it easy for you to automatically mark new orders as 'Ready For Pickup' as soon as they come in. Ideal for stores that always have products in stock and want to speed up the pickup process.
Runs Occurs whenever an order is created. Configuration includes pickup locations.
Use this task to automatically remove a certain customer tag whenever a particular product is refunded, for that customer.
Runs Occurs whenever a new refund is created without errors on an order, independent from the movement of money. Configuration includes product ids and customer tag to remove.
Use this task to make repeat business easy by automatically emailing your customers X days after their purchase, with a one-click reorder link that will send them straight to checkout with their entire cart pre-filled.
Runs Occurs whenever an order is paid and Occurs every hour. Configuration includes days to wait, email subject, email body, pending tag, sent tag, and order referral code.
This demonstration task responds to product updates, by firing a custom event whenever it finds that any of the configured product and variant attributes have changed from a cached snapshot. This is useful for creating custom tasks without having to continually build the scaffolding of a specific attribute monitor in each of them.
Runs Occurs whenever a product is updated, ordered, or variants are added, removed or updated, Occurs when a user manually triggers the task, and Occurs whenever a product is created. Configuration includes custom event topic, product attributes to monitor, and variant attributes to monitor.
Configure this tag with a mapping of country codes to tracking companies and URL templates, and/or default companies and URL templates. When an order is tagged, this task will apply the appropriate values to each fulfillment that has a tracking number.
Runs Occurs whenever an order is updated. Configuration includes order tag to watch for, country codes and tracking url templates, default tracking url template, overwrite existing tracking urls, country codes and tracking companies, default tracking company, and notify customers.
This task scans the last x days of orders, and unpublishes any products that haven't met your specified sales threshold during that time period. By default, this task adds up the line item subtotals for each product (quantity times price), but it can also count by total quantity sold. This task only looks at products that were published before the time period being examined.
Runs Occurs when a user manually triggers the task and Occurs when a bulk operation is completed. Configuration includes sales channel name, number of days back to look, minimum sales threshold for staying published, use total quantity instead of line item subtotals, test mode, and run daily.
This task keeps track of how many lifetime refunded orders a customer has in your shop, and if that count hits a certain threshold, then it will apply a tag to the customer. This is useful for keeping tabs on serial returners.
Runs Occurs whenever a new refund is created without errors on an order, independent from the movement of money, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes refunded orders count threshold for tagging, customer tag to apply, and refunded orders count metafield namespace dot key.
Use this task to get an email alert with a list of the returned items whenever a return is marked as closed.
Runs Occurs whenever a return is closed. Configuration includes email recipients and include pos returns.
Use this task to send a staff email, the moment Shopify registers a successful delivery.
Runs Occurs whenever a fulfillment event is created. Configuration includes email recipient, email subject, and email body.
This task sends a new-order email alert to somebody specific, based on the contents of a cart attribute. Useful for allowing customers to select their salesperson, alerting the appropriate salesperson when the order is placed.
Runs Occurs whenever an order is created. Configuration includes cart attribute name, cart attribute values and email addresses, email subject, email body, and only send for paid orders.
This task works by monitoring the number of orders created per hour, and clearing the inventory for all in-stock items when the hourly order limit is reached. Optionally, this task can restore inventory to its original levels at minute zero of the next hour, or on demand.
Runs Occurs whenever an order is created and Occurs every hour. Configuration includes maximum hourly orders, only count orders matching this query, only clear inventory for products with this tag, restore inventory levels the next hour, and restore inventory levels on demand.
Does what it says on the tin. :) Any order with a total price of 0.00 will be archived/closed, immediately upon order fulfillment.
Runs Occurs whenever an order is fulfilled.
This task scans your incoming orders, tagging customers based on the Shopify app responsible for creating each order. Run this task manually to tag your customers based on their historical orders.
Runs Occurs whenever an order is created, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes app titles and customer tags and test mode.
Either triggered manually, or configured to run daily, this task will look for the oldest products in the collection of your choice, and delete as many of them as you wish.
Runs Occurs when a user manually triggers the task. Configuration includes collection id, number of products to delete at once, test mode, and run daily.
Use this task to easily check in on customers, after an order of theirs is cancelled. Optionally, queue up the email for a certain number of hours from the time of cancellation.
Runs Occurs whenever an order is cancelled. Configuration includes only send for first time customers, hours to wait after cancellation, email subject, and email body.
When new orders are created, this task will check to see if the customer has any of the configured metafields, and if so it will copy the metafield values to the paired order attributes.
Runs Occurs whenever an order is created. Configuration includes customer metafields and order attributes.
This task does exactly as it sounds :) Add time delays to your Shopify Flow workflows. Choose your time delays by using offsets in the Subscriptions field. Learn more about offsets here.
Runs Occurs whenever an order is created, with a 5 minute delay, Occurs whenever an order is created, with a 5 day delay, and Occurs whenever an order is created, with a 5 month delay.
Use this task to quickly delete draft orders from your account, optionally filtering by status, or by draft order age. Useful for keeping things tidy. :)
Runs Occurs when a user manually triggers the task. Configuration includes delete open draft orders, delete draft orders that have invoices sent, delete completed draft orders, minimum draft order age in days, and run daily at midnight.
This task runs when an order is updated. When the tag of your choice is found in the order's tag list, all of its fulfillments (if any) will be cancelled, and the aforementioned tag will be removed.
Runs Occurs whenever an order is updated. Configuration includes required order tag.
Automatically generate a PDF to be emailed to the address on file for the order(s) when sent to Mechanic. This task listens for orders sent to Mechanic via Admin and Bulk action links in the Shopify admin.
Runs Occurs when a user sends orders to Mechanic and Occurs when a user sends an order to Mechanic. Configuration includes email subject, email body, pdf attachment filename, and pdf html template.
When new orders are created, this task will check to see if any of the configured metafields are set on the company which placed the order, and if so then it will add order tags based on the metafield values.
Runs Occurs whenever an order is created and Occurs when a user sends an order to Mechanic. Configuration includes metafields and tag prefixes and truncate long tags.
Running on a schedule or manually, this task will create automated collections based on the validation values of the configured product metafield definitions. Additionally, configuring one or more exact sales channel names will enable publishing of any newly created collections by this task to those sales channels.
Runs Occurs when a user manually triggers the task and Occurs when a Mechanic action is performed. Configuration includes product metafields and collection title prefixes, names of sales channels to publish collections to, run daily, run hourly, and test mode.
Use this task to auto-approve return requests, typically made by customers using self-serve from their account. Choose to limit the auto-approval to orders with any of a set of tags, products with any of a set of tags, or specific product categories or types. Optionally, configure email recipients to be notified when any auto-approval occurs.
Runs Occurs whenever a return is requested and Occurs when a Mechanic action is performed. Configuration includes limit to orders with any of these tags, limit to products with any of these tags, limit to these product categories or types, and notification email recipients.
This task will scan for all orders that have a financial status of "authorized" or optionally "partially paid", and will attempt to capture all open authorized payments for them. This task can be scheduled to run daily, and can be run on demand.
Runs Occurs when a user manually triggers the task. Configuration includes include partially paid orders, run daily, and hours to wait after midnight when running daily.
Useful for keeping an eye on unexpected cancellations by third party shipping services.
Runs Occurs whenever a fulfillment is updated. Configuration includes email recipient, email subject, and email body.
Use this task to set the available inventory of a single product variant at a single location in your shop at a specific time on your choice of recurring days. Great for daily or weekly product drops!
Runs Occurs when a user manually triggers the task. Configuration includes variant, inventory quantity to set, location name, hours offset from midnight, minutes offset from the hour, run daily, and days to run.
Use this task with the companion publishing task (see this task's documentation) to make a certain collection of products available on a schedule, and unavailable on another schedule.
Runs Occurs every Monday at midnight (in local time), with a 18 hour delay, Occurs every Tuesday at midnight (in local time), with a 18 hour delay, Occurs every Wednesday at midnight (in local time), with a 18 hour delay, Occurs every Thursday at midnight (in local time), with a 18 hour delay, Occurs every Friday at midnight (in local time), with a 18 hour delay, Occurs every Saturday at midnight (in local time), with a 14 hour delay, and Occurs every Sunday at midnight (in local time), with a 14 hour delay. Configuration includes collection id.
Running daily, or manually, this task query for all customers if their first order was a year or more ago and they do not yet have the configured tag to apply. Alternatively, you may choose to tag customers if their account was created at least a year ago.
Runs Occurs when a user manually triggers the task and Occurs every day at midnight (in local time). Configuration includes customer tag to apply, customer search query, days to wait before tagging, and use account creation date instead of first order date.
Running when an order is updated, this task captures payment in proportion to the order value that has been fulfilled. For example, for an order with a subtotal of $10 and a total of $15 with shipping/taxes/discounts, this task will capture $7.50 when $5 of the order's value has been fulfilled.
Runs Occurs whenever an order is updated. Configuration includes payment gateway names.
This task looks up orders by their order number, adds the note of your choice to the order record, and removes that same note 12 hours later. A bespoke task for a very specific merchant need, we publish this task as an example of getting creative with Mechanic. :)
Runs Occurs when a user manually triggers the task with text and Occurs whenever user/orders/remove_note is triggered. Configuration includes hours to wait and order note to add.
This task monitors for updates to a customer's state (account disabled, password set, invited, or invitation declined), and sends alert emails for any state changes you care about.
Runs Occurs whenever a customer is updated and Occurs whenever a customer is created. Configuration includes email when a customer declines an invitation, email when a customer account is disabled, email when a customer initially sets an account password, email when a customer is invited, and email recipient.
This task auto-captures payment if the customer has selected a certain shipping method. Useful for expedited order fulfillments.
Runs Occurs whenever an order is created. Configuration includes allowed shipping methods.
Shopify's order group filters allow you to filter by the tags the order contains – but not the tags a order does not contain. Use this task to sync an "inverse" tag to all orders who do not have a particular tag, allowing you to filter orders in Shopify by that inverse tag.
Runs Occurs whenever an order is created, Occurs whenever an order is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes order tag to watch and order tag to use when missing.
Use this task to identify orders that are for customers who have previously ordered from your store. Optionally, ignore more frequent purchasers, by ignoring customers who've made an order recently. Useful for making sure to include a welcome-back gift in order shipments. :)
Runs Occurs whenever an order is created. Configuration includes ignore customers who previously ordered after this date, ignore customers who previously ordered less than x days ago, and order note to add.
Use this task to automatically switch collections over to an appropriate theme template, when every product in the collection has gone completely out of stock, and to switch them back when inventory arrives.
Runs Occurs whenever an inventory level is updated, Occurs when a user manually triggers the task, and Occurs when a bulk operation is completed. Configuration includes collection template suffix when all products are out of stock, default collection template suffix, run every time an inventory level is updated, run daily, and run hourly.
This task will send a follow-up email to your customer after their order is paid, waiting for a configurable number of days before doing so.
Runs Occurs whenever an order is created. Configuration includes product vendor, email subject, email body, and number of days to wait before sending email.
When a customer orders an item on sale (technically, when the order contains a product variant that includes a "compare at" price), this task automatically adds a tag to their account. Useful for keeping track of customers who take advantage of sale pricing!
Runs Occurs whenever an order is created and Occurs when a user manually triggers the task. Configuration includes tag to add.
Don't keep your customers waiting! Stay on top of orders that have yet to be delivered, by auto-archiving every order once every item has reached the customer.
Runs Occurs whenever a fulfillment event is created.
Tag orders with the Locksmith secret link used when placing an order. Optionally, tag the customer as well.
Runs Occurs whenever an order is created. Configuration includes query parameter name, cart attribute name, tag customer with parameter value, and only tag the customer for their first order.
Use this task to tag products with their category from Shopify's standard product taxonomy. Run this task manually to scan every active product in your store. Optionally, set it to run daily to scan active products updated in the last day.
Runs Occurs when a user manually triggers the task. Configuration includes apply this prefix to tags and run task daily.
Using Zapiet to track store pickups? This task filters for orders that are tagged by Zapiet for pickup, and emails you a report of how many orders are scheduled for each of the next few days. Useful for scanning the week ahead, and blacking out dates that are at capacity.
Runs Occurs when a user manually triggers the task and Occurs every day at midnight (in local time). Configuration includes tagged with, date tag format, days ahead, email recipient, and email subject.
This task integrates Report Toaster and ShipStation. On order fulfillment, Mechanic calls the ShipStation API to retrieve the shipping cost, and this cost is sent to Report Toaster.
Runs Occurs whenever an order is fulfilled, Occurs when a Mechanic action is performed, and Occurs when a user manually triggers the task with text. Configuration includes api username and api password.
When new orders are created, this task will check to see if any of the configured order metafields are set on the order, and if so then it will add order tags based on the metafield values.
Runs Occurs whenever an order is created and Occurs when a user sends an order to Mechanic. Configuration includes metafields and tag prefixes and truncate long tags.
Use this task to quickly reset product types in bulk based on product titles. When run manually, it will query for all products in the shop and for each product with a matched keyword in the title, the task will assign the paired product type to it.
Runs Occurs when a user manually triggers the task. Configuration includes product types and keywords.
Use this task to automatially keep your Discounts list clean by deleting any that have been expired for a configurable amount of days. Choose whether to delete automatic or code discounts, or both. Optionally, limit the deletions to discounts created by specific apps.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes days after expiration to delete, delete automatic discounts, delete code discounts, and only delete discounts created by these apps.
When an order is fulfilled, this task will scan the tracking information for each fulfillment. The name of each tracking company on file – i.e. the fulfillment carrier – will be used to look up a new order tag to apply, per the task's configuration.
Runs Occurs whenever an order is fulfilled. Configuration includes fulfillment carriers and order tags.
This task prepends an HTML message to the beginning of the product description, for each product that goes out of stock, and then restores the original product description when the product is back in stock. Optionally, you may choose to append the HTML message to the end of the product description, instead of prepending it to the beginning.
Runs Occurs whenever an inventory level is updated and Occurs when a user manually triggers the task. Configuration includes only modify products with this tag, add this html to product description, and add the html to end of product description instead of beginning.
Use this task when you want to record your external PayPal transactions as Shopify orders. Are you using PayPal subscriptions? Or receiving direct payments you'd like to record in Shopify? Use this task, or file a task request to have it modified for more purpose-specific uses. :) Again, this isn't for PayPal as a Shopify payment provider – it's for any time you might be using PayPal outside of your Shopify store.
Runs Occurs whenever user/paypal/ipn is triggered. Configuration includes only import these transaction types, only import completed transactions, send receipt, default memo, order requires shipping, mark as fulfilled, and send fulfillment receipt.
The collection update webhook does not fire when product memberships change based on the smart collection's rules. This task bridges that gap by monitoring smart collections at regular intervals to see if the list of their product IDs has changed, and if so it will trigger the custom event topic you configure.
Runs Occurs every hour and Occurs when a user manually triggers the task. Configuration includes run frequency, custom event topic, collections to monitor, and extra logging.
Use this task with the companion unpublishing task (see this task's documentation) to make a certain collection of products available on a schedule, and unavailable on another schedule.
Runs Occurs every Monday at midnight (in local time), with a 9 hour delay, Occurs every Tuesday at midnight (in local time), with a 9 hour delay, Occurs every Wednesday at midnight (in local time), with a 9 hour delay, Occurs every Thursday at midnight (in local time), with a 9 hour delay, Occurs every Friday at midnight (in local time), with a 9 hour delay, Occurs every Saturday at midnight (in local time), with a 10 hour delay, and Occurs every Sunday at midnight (in local time), with a 10 hour delay. Configuration includes collection id.
Use this task to automatically roll out your products on specific days of the week. This task runs every midnight, in your shop's local timezone, and it scans your catalog for unpublished products tagged with the current day of the week (e.g. "Monday", "tuesday", etc).
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task.
Keep customers happy by making sure your vendors have up-to-date shipping information. This keeps your vendors happy, too!
Runs Occurs whenever an order is updated. Configuration includes vendors and email addresses, email body, and email subject.
Use this task to copy metaobject field values to the referencing products' tags. Configure a product metafield that is a metaobject_reference type (or list.metaobject_reference), and add the metaobject field keys which contain the values to be added as tags, along with paired tag prefixes for each. Then run the task manually, or schedule it to run daily, and it will scan all active products in the shop on each run and tag them as needed.
Runs Occurs when a user manually triggers the task. Configuration includes product metafield, metaobject field keys and tag prefixes, remove outdated prefixed tags, run daily, and test mode.
This task watches for newly-created collections, waits a configurable number of days, and then sends a staff email if no orders have been placed for products that are in the new collection.
Runs Occurs whenever a collection is created, with a 2 day delay. Configuration includes email recipient, email subject, email body, and days to wait before checking.
Useful for custom orders, this task lets you offer multiple product and variant listings for what is ultimately the same stock. A purchase for a single product leads to the inventory for all other listings, of the same product type, being lowered by the amount ordered.
Runs Occurs when a user manually triggers the task and Occurs every 10 minutes. Configuration includes product types to monitor and only sync active products.
Use this task to automatically detect and tag orders that contain a complete bundle of products. Configure this task with as many bundles as you like, specifying a tag to add and a list of required SKUs.
Runs Occurs whenever an order is created. Configuration includes tags and required skus.
Use this task to automatically tag customers as members when they purchase a minimum quantity of products. And, check on those customers on a regular basis to ensure that they maintain their order quantity minimums.
Runs Occurs whenever an order is paid and Occurs whenever user/membership/renewal is triggered, with a 12 month delay. Configuration includes minimum qualifying order quantity, membership tag, months of order history to consider for renewal, minimum qualifying order quantity for renewal, and months between renewal checks.
This task auto-tags today's new orders, as they're processed, and auto-untags them when the date changes. Optionally, choose to untag outside of a rolling 24-hour window, instead of untagging yesterday's orders at midnight.
Runs Occurs whenever an order is created and Occurs every day at midnight (in local time). Configuration includes use rolling 24 hour window and order tag.
This task shows how to call an external API using the HTTP action type to first get a limited page of products, and then paginate through the responses until all of the products are fetched.
Runs Occurs when a user manually triggers the task, Occurs when a Mechanic action is performed, and Occurs whenever user/demo_paginated_api/fetched_products is triggered.
Use this task to automatically keep vendors up to date as an order evolves. Configure this task with a list of known vendor names and their email addresses, and this task will email them whenever it notices the tag of your choice on the order.
Runs Occurs whenever an order is updated. Configuration includes order tag to watch for, vendors and email addresses, email subject, email body, and ignore orders older than this task.
Use this task to publish a banner, to be displayed across your online storefront. This task comes with some pre-configured HTML and CSS – customize to taste. :)
Runs . Configuration includes starting date and time, ending date and time, banner html, and banner parent css selector.
Email Pirate Ship exports to Mechanic and add those shipping costs to orders with Report Toaster.
Runs Occurs when your Mechanic account receives an email. Configuration includes email subject, order name column, prepend pound sign to order name, and shipping cost column.
Useful for enforcing order limits on the backend, use this task to ensure that orders with too many of certain products will be automatically cancelled.
Runs Occurs whenever an order is created. Configuration includes skus and quantity cancellation thresholds, email customer when cancelling, refund payment for cancelled orders, restock inventory for cancelled orders, cancellation reason to set, and staff note for timeline.
This task demonstrates how to send emails that respect the customer's language preference, by matching their locale to a pre-written email translation.
Runs Occurs whenever a customer is created. Configuration includes default locale, email subject translations, and email body translations.
This task allows you to easily see which customers have open draft orders. Using the tag of your choice, it will set it on any customers with at least one open draft order (including draft orders where an invoice has been sent).
Runs Occurs whenever a draft order is created, Occurs whenever a draft order is updated, Occurs every day at midnight (in local time), and Occurs when a user manually triggers the task. Configuration includes customer tag to apply.
This task watches for orders for a certain donation product, and tallies up the total donation amount in a store metafield, allowing you to display this value in your online storefront.
Runs Occurs when a user manually triggers the task, Occurs whenever an order is created, and Occurs whenever an order is paid. Configuration includes metafield namespace, metafield key, donation product handle, and recalculate nightly.
This task illustrates Shopify's recommendation of implementing reconciliation, in the case of missing Shopify events. This implementation handles the rare case that Shopify fails to deliver a webhook (orders/create, in this example), by scanning for unprocessed orders every 15 minutes.
Runs Occurs whenever an order is created, Occurs every 15 minutes, and Occurs when a user manually triggers the task. Configuration includes run on order create, reconcile every 15 minutes, and reconcile on manual run.
Use this task to easily keep track of who's responsible for manually creating new customers.
Runs Occurs whenever a customer is created. Configuration includes staff names and tags.
This task runs immediately after each new fulfillment is created, and adds a prefix to its tracking number, if a tracking number is present.
Runs Occurs whenever a fulfillment is created. Configuration includes tracking number prefix to add and notify customer.
Useful for customers who need recurring reminders to reorder. Optionally filtering by a customer tag, it monitors the most recent order for each customer, and sends them reminders every x days since that order.
Runs Occurs every day at midnight (in local time) and Occurs when a bulk operation is completed. Configuration includes only include customers having this tag, number of days to wait between emails, email subject, email body, and test mode.
Useful for Canadian stores with limited shipping zones, this task inspects the FSA (the first three characters of the postal code) for each order's shipping address. If an FSA is found that's not on a preconfigured list, this task sends an email to the recipients of your choice.
Runs Occurs whenever an order is created. Configuration includes supported fsa values, email recipients, email subject, and email body.
Use this task to receive an alert when your store reaches a maximum number of orders per day. Unlike inventory-limiting tasks, this task only sends notifications without making any changes to your store's inventory or product availability.
Runs Occurs whenever an order is created, Occurs every day at midnight (in local time), and Occurs when a user manually triggers the task. Configuration includes maximum daily orders, notification email recipients, only count orders matching this query, email subject, and email body.
This task demonstrates Mechanic's opt-in ability to perform a task's generated actions in a sequence, rather than in parallel. To try this task, enable the "Perform action runs in sequence" option, in the task's advanced settings.
Runs Occurs when a user manually triggers the task. Configuration includes fail the sixth action.
Does what it says on the tin. :) Provide your GetResponse API key (found under the account menu, under "Integrations & API" and "API") and a list token (found in the settings for your list – look for 5-6 letters and numbers), and Mechanic will automatically send each new customer account (full name and email address) over to GetResponse.
Runs Occurs whenever a customer is created. Configuration includes getresponse api key and getresponse list token.
Demonstration: Create Google sheets, and list and create files in Google Drive
Runs Occurs when a user manually triggers the task and Occurs when a Mechanic action is performed. Configuration includes google account, create google sheet demo, list google drive files demo, and create google drive file demo.
The merchant who created this task uses another app for validating orders in bulk, resulting in a list of order numbers that should be captured. This task prompts the merchant for a list of order numbers, which Mechanic then captures one by one.
Runs Occurs when a user manually triggers the task with text.
Use this task to auto-delete product metafields that are older than the configured minimum age in days. Useful for removing transient metafields a certain number of days after they have been created.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes product metafields to monitor, minimum age in days before deletion, and test mode.
This task watches for newly-paid orders. When an order contains a certain line item, this task retrieves a file from the URL of your choice, and emails that file to the customer. Because URLs are easier to share, this makes for a safer way to distribute downloadable materials.
Runs Occurs whenever an order is paid. Configuration includes required line item title, email subject, email body, attachment filename, and attachment url.
This advanced task allows you to schedule section publishing and unpublishing for your store. To use this task, enter a datetime to publish, a theme ID, and template names paired with one or more section IDs to publish or unpublish. If the configured datetime matches the current task run time at a scheduled 10 minute interval, then it will publish and/or unpublish the theme sections as configured.
Runs Occurs every 10 minutes, Occurs when a user manually triggers the task, and Occurs when a Mechanic action is performed. Configuration includes datetime to publish, theme id, template names and section ids to publish, and template names and section ids to unpublish.
This task is here to illustrate managing tracking numbers. If a default tracking number is right for your orders, you can use this task to make sure that one is added the instant a fulfillment is created.
Runs Occurs whenever a fulfillment is created. Configuration includes default tracking number.
Google Drive File Upload Demo
Runs Occurs when a user manually triggers the task and Occurs when a Mechanic action is performed. Configuration includes google account and overwrite files with the same name.
Use this task to clear out your draft orders, on demand. Filter by draft order status (open, invoice sent, closed), or by draft order tags.
Runs Occurs when a user manually triggers the task. Configuration includes include open draft orders, include invoice sent draft orders, include closed draft orders, only delete draft orders having this tag, and ignore draft orders having this tag.
This task illustrates how to use a typeface from Google Fonts, embedding it in a generated PDF which is then emailed to the recipient of your choice.
Runs Occurs when a user manually triggers the task. Configuration includes destination email address.
This task auto-cancels incoming orders when it finds all of a certain set of risk assessment facts. Risk assessment facts must match exactly, so double-check your configuration! Optionally, this task can also auto-tag the order, email the customer, restock the inventory, and/or refund payment.
Runs Occurs whenever an order is updated. Configuration includes required risk assessment facts, cancellation reason to set, ignore unpaid orders, refund payment for cancelled orders, restock inventory for cancelled orders, email customer when cancelling, staff note for timeline, and add this order tag when cancelling.
This task will run daily to scan order timeline events from the past week to see if any orders have new shipping provider charges for labels. Qualifying orders will be tagged with the tag of your choice.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes order tag to add.
This task demonstrates how to structure Mechanic Liquid to send and receive the results of a ShopifyQL query. The default query has been adapted from the Total sales by vendor report available in Shopify Analytics.
Runs Occurs when a user manually triggers the task. Configuration includes shopifyql query.
This task will monitor when customers submit a new Shopify Form to your shop, and then create a row in a linked Google Sheet with the specific data from the form that you specify.
Runs Triggers when tags are added to a customer and Occurs when a user manually triggers the task. Configuration includes google account, spreadsheet title, spreadsheet id, form id, and column headers and customer metafields.
Use this task to notify customers about product-specific information, that should only be delivered when a successful fulfillment is registered for their purchased product.
Runs Occurs whenever a fulfillment is created and Occurs whenever a fulfillment is updated. Configuration includes required product id, email subject, and email body.
Use this task to auto-delete customer metafields that are older than the configured minimum age in days. Useful for removing transient metafields a certain number of days after they have been created.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes customer metafields to monitor, minimum age in days before deletion, and test mode.
Use this task to automatically delete non-purchased products created by Neon Sign Customiser. Set the number of days old products should be before Mechanic deletes a product.
Runs Occurs when a user manually triggers the task. Configuration includes products must be x number of days old, test mode, live mode, and run daily.
Demonstration: Create and update a table in Airtable
Runs Occurs when a user manually triggers the task and Occurs when a Mechanic action is performed. Configuration includes airtable account and airtable base id.
Demonstration: Post to a Slack channel
Runs Occurs when a user manually triggers the task. Configuration includes slack account and slack channel id.
This task will run daily to sort the selected collections, moving products with sales in the lookback period to the top in descending order by the sort metric (e.g. "Net sales"). All other products in each collection will be left in the previously sorted order. Choose the length of the sales lookback period in days and the metric you wish to use for sorting.
Runs Occurs every day at midnight (in local time) and Occurs when a user manually triggers the task. Configuration includes collections to sort, lookback period in days, and sort metric.