Mechanic can do it all.

Get a million Shopify apps for the price of one. All these tasks run on Mechanic. :)

Isaac Bowen (team@usemechanic.com)
Super basic, super useful. :) Get an email alert whenever a customer account is created.
Runs when a customer is created. Configuration includes to, subject, and body.
Isaac Bowen (team@usemechanic.com)
Configure this task with a product title and/or some tags to watch for, and this task will apply the tag(s) of your choice to every customer who makes a matching purchase.
Runs when an order is paid. Configuration includes required product title, required product tags, and customer tags to apply.
Isaac Bowen (team@usemechanic.com)
This task tags every new customer, and it's easy to update it to be more specific about who gets tagged – use that chat button in the corner, and we’ll help!
Runs when a customer is created. Configuration includes tag.
Isaac Bowen (team@usemechanic.com)
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 when a customer is created, when a customer is updated, and when a user triggers the task. Configuration includes tag to watch for, ignore tag case, autotag customers after emailing, email subject, and email body.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Whenever inventory for a product is updated, this task scans all variants and all fulfillment locations, adds up all inventory related to that product, and makes sure the product is hidden if the total inventory meets your "out of stock" threshold. Optionally, it'll send you an email when it does so.
Runs when a user triggers the task and when an inventory level is updated. Configuration includes email notification recipient, out of stock inventory quantity, and only monitor products with these tags.
Isaac Bowen (team@usemechanic.com)
Clear the clutter in your orders list, automatically! On a nightly basis or on-demand, this task scans for orders that are more than two days old (customizable!), and cancels and closes the order if its financial status is still marked "pending".
Runs every day at midnight and when a user triggers the task. Configuration includes days to wait before checking order, restock inventory, send cancellation email to customer, and tag to add to the order.
Isaac Bowen (team@usemechanic.com)
Whenever inventory for a product is updated, this task scans all variants and all fulfillment locations, adds up all inventory related to that product, and makes sure the product is published if the total inventory meets your "back in stock" threshold. Optionally, it'll send you an email when it does so.
Runs when an inventory level is updated. Configuration includes email notification recipient and back in stock inventory quantity.
Jed Storie (jed@fortco.tech)
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 when an order is created. Configuration includes email subject, email body, product sku, and days to wait before emailing.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Follow up with your customers automatically, and establish the purchase -> earn-reviews -> attract-customers cycle. This task comes prefilled with a friendly email that gives the customer direct links to their purchases on your website – customize this email to taste.
Runs 7 days after an order is fulfilled. Configuration includes email subject, email body, and days to wait before emailing.
Isaac Bowen (team@usemechanic.com)
Automatically prompt customers to activate their customer accounts, after placing an order in your store – useful if your online store unlocks special offers, functionality, or content after making a purchase. Optionally, only send invitations if the customer has ordered a product with a specific tag.
Runs when an order is created. Configuration includes only invite if the customer has this tag, only invite if the order contains a product with this tag, invitation email subject, and invitation email body.
Isaac Bowen (team@usemechanic.com)
This task emails customers right away about unpaid orders, and then continues to email them every (x) days until the order is paid. This task shows off Mechanic's ability to perform repeated delayed actions.
Runs when an order is created and 1 days after user/orders/unpaid_reminder is triggered. Configuration includes subject, body, and number of days to wait between reminders.
Isaac Bowen (team@usemechanic.com)
Quickly send a thank-you email (or any other sort of follow-up email) to your customers, as soon as their order is paid. 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 when an order is paid. Configuration includes subject and body.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
This task checks the payment method for new orders immediately upon order creation, and tags the order accordingly. (If you need to tag the order later on, based on updates or when the order is paid, get in touch!)
Runs when an order is created. Configuration includes payment gateway name and comma separated tags to add.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when a user triggers the task. Configuration includes collections and tags.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when an order is updated. Configuration includes tag to watch for, email subject, email body, and ignore orders older than this task.
Isaac Bowen (team@usemechanic.com)
Useful for digital products, memberships, or anything else that needs to be fulfilled instantly. This task watches for paid orders, and auto-fulfills all line items that don't require shipping.
Runs when an order is paid.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 2 days after an order is paid. Configuration includes tag to add, staff notification recipient, send the customer an email, customer email subject, customer email body, and days to wait before followup.
Isaac Bowen (team@usemechanic.com)
This task wait for 7 days after an order placed, and – if the order is still unpaid – emails the customer, and optionally adds a tag to the order.
Runs 7 days after an order is created. Configuration includes email subject, email body, and tag to add to the order.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when a user triggers the task.
Isaac Bowen (team@usemechanic.com)
Immediately upon order creation, add one or more tags to the order. Simple as that. :)
Runs when an order is created. Configuration includes comma separated tags to add.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 6 months after an order is created and 12 months after an order is created. Configuration includes subject and body.
Isaac Bowen (team@usemechanic.com)
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 when a product is created, when a product is updated, and when a user triggers the task. Configuration includes tag for sale products and tag for all other products.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes only copy these tags.
Ken Parelius (team@usemechanic.com)
The task allows you to send an email to an address (or addresses) of your choice when a certain product is purchased.
Runs when an order is paid. Configuration includes email address, email subject, email body, reply to email address, and product title.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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.
Runs 10 days after an order is paid. Configuration includes email subject, email body, and number of days to wait.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when an order is updated. Configuration includes tag to watch for, email recipients, email subject, and email body.
Isaac Bowen (isaac@lightward.com)
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 when an order is updated. Configuration includes order tag and notify customer on fulfillment.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task, when a product is created, and when a product is updated. Configuration includes tag for cost missing.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
When orders come in, use this task to copy product tags from the order to the customer on file. Useful for automatically segmenting your customers based on attributes of their purchases. To keep things tidy, optionally configure this task to only look for a certain set of tags.
Runs when an order is created. Configuration includes only copy these tags.
Isaac Bowen (team@usemechanic.com)
Send yourself a text message, or blink your lights, or do whatever you like! This task is an example, more than anything, of what you can do by connecting Mechanic and IFTTT. Follow our guide (in the task documentation) to learn how to set up text message alerts for customer signups, and then customize any and every part of this task to your liking.
Runs when a customer is created. Configuration includes ifttt event, ifttt key, value1, value2, and value3.
Isaac Bowen (team@usemechanic.com)
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 when a fulfillment event is created. Configuration includes email recipient.
Isaac Bowen (team@usemechanic.com)
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 when some text is submitted.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Save time by letting this task keep your variant SKUs up to date, generating them based on your product handle, and the initials of each variant option. Useful for large catalogs, or for anyone who has a consistent SKU format. Like all tasks, this one is easy to update for your business's needs - get in touch if you need a hand.
Runs when a product is created and when a product is updated. Configuration includes product options to keep unabbreviated.
Isaac Bowen (team@usemechanic.com)
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.
Runs when an order is created. Configuration includes copy these tags and copy tags having this prefix.
Isaac Bowen (team@usemechanic.com)
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 when a fulfillment event is created.
Isaac Bowen (team@usemechanic.com)
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 when some text is submitted.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when an order is paid, when an order is updated, and 1 month after user/memberships/expire is triggered. Configuration includes membership product title, membership tag, and remove tag for cancelled orders.
Isaac Bowen (team@usemechanic.com)
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 Mechanic task watches for new and updated products, making sure that the product range tags stay in sync with prices available for each product. And, if you run the task manually, it'll update the tags for all products in your shop.
Runs when a user triggers the task, when a product is created, and when a product is updated. Configuration includes range maximum, range minimum, and range increment.
Mechanic Team (team@usemechanic.com)
Does exactly as it says. :)
Runs when a customer is updated. Configuration includes customer tag to watch for, customer tag to remove, and ignore tag case.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task. Configuration includes email recipient.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
This task will scan for all orders that have a financial status of "authorized", and will capture payment for them. This task can be scheduled to run daily, and can be run on demand.
Runs when a user triggers the task. Configuration includes include partially paid orders, run daily, and hours to wait after midnight when running daily.
Isaac Bowen (team@usemechanic.com)
Roll your own abandoned cart emails with this task – or, modify it to perform any other actions that your business needs when a cart is let go. :) Out of the box, this task sends customers a recovery link, with an emails subject and message that you can easily customize.
Runs 1 day after user/checkouts/abandoned is triggered, when a checkout is created, when a checkout is updated, and when an order is created. Configuration includes email subject and email body.
Isaac Bowen (team@usemechanic.com)
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 24 hours after user/draft_orders/followup is triggered and when a draft order is updated. Configuration includes send daily emails, email subject, and email body.
Isaac Bowen (team@usemechanic.com)
Useful in a million scenarios. The merchant who requested this task has discounts set up based on customer tag, and they're using this task to guarantee that qualifying customers see their discount immediately – even if they just signed up!
Runs when a customer is created. Configuration includes customer email domains and customer tag to apply.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Mechanic Team (team@usemechanic.com)
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 when an order is created and when a user triggers the task. Configuration includes shipping method titles and tags and allow partial matches for shipping method titles.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when a user triggers the task.
Isaac Bowen (team@usemechanic.com)
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 when 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.
Isaac Bowen (team@usemechanic.com)
Use this task to bring all of your inventory levels to the same place, every night.
Runs every day at midnight. Configuration includes inventory level to apply and collection.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
This task, paired with the linked instructions, creates a feed of product inventory (optionally filtering by product type).
Runs when a user triggers the task, every day at midnight, and 12 hours after every day at midnight. Configuration includes filter by product type.
Isaac Bowen (team@usemechanic.com)
Use this task to automatically maintain a minimum inventory level.
Runs when an inventory level is updated. Configuration includes minimum inventory level, location, variant ids to ignore, variant options to ignore, and product types to ignore.
Isaac Bowen (team@usemechanic.com)
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 when a fulfillment is created and when a fulfillment is updated. Configuration includes shipping status tags.
Isaac Bowen (team@usemechanic.com)
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 when a Judge.me review is created. Configuration includes metafield namespace required, metafield key, and tags to apply for review counts.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when an inventory level is updated. Configuration includes filter by these location names and filter by these product types.
Isaac Bowen (team@usemechanic.com)
Use this task to keep 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 when an order is paid and when a refund is created. Configuration includes ignore refunded purchases and tag prefix.
Isaac Bowen (isaac@lightward.com)
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 when an order is updated and 48 hours after user/orders/delete_cancelled is triggered.
Isaac Bowen (team@usemechanic.com)
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 when a customer is created. Configuration includes required customer tag, email subject, and email body.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Does what it says on the tin. :) Optionally, emails you an alert when a product goes out of stock.
Runs when an inventory level is updated and when a user triggers the task. Configuration includes out of stock inventory level, product tag, and email alert recipient.
Isaac Bowen (team@usemechanic.com)
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 1 minute after a customer is created. Configuration includes invitation email subject and invitation email body.
Isaac Bowen (team@usemechanic.com)
When an order is created, this task adds the location of the purchase to the customer's tags. Useful for stores with multiple Shopify-powered locations.
Runs when an order is created and when a user triggers the task. Configuration includes tag for online orders.
Isaac Bowen (team@usemechanic.com)
Automatically generate an invoice PDF, to be emailed to the address on file for the order. Useful for working with billing departments. :)
Runs when an order is created. Configuration includes email subject, email body, pdf attachment filename, and pdf html template.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task and every day at midnight. Configuration includes number of days to keep a product in this collection, number of products to keep in this collection, and collection.
Isaac Bowen (team@usemechanic.com)
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 when an order is paid. 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.
Isaac Bowen (team@usemechanic.com)
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 when a user 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.
Mechanic Team (team@usemechanic.com)
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 every Monday at midnight and when a user 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.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes only for orders including this product tag, email recipients, email subject, email body, and only for paid orders.
Isaac Bowen (team@usemechanic.com)
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 when a user 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.
Isaac Bowen (team@usemechanic.com)
Super simple: this task monitors for order fulfillments, and automatically archives orders when they're fulfilled.
Runs when an order is fulfilled and when a user triggers the task.
Isaac Bowen (team@usemechanic.com)
Use this task to copy each product's vendor to the product's tag. :)
Runs when a product is created, when a product is updated, and when a user triggers the task.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Need to reach customers who purchased something specific? This task scans your order history over the last 60 days, looking for paid orders for the product you specify, and sends each one an email that you can customize.
Runs when some text is submitted. Configuration includes email subject, email body, days back to search, and test mode.
Isaac Bowen (team@usemechanic.com)
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 when an order is paid. Configuration includes customer tag.
Isaac Bowen (team@usemechanic.com)
This task makes order comments more portable, by copying them to the order note during a regular scan (nightly, hourly, or manually). Once copied over, they can be included on printed invoices, or used anywhere you might use the order note.
Runs when a user triggers the task. Configuration includes only scan orders matching this query, comment date format, run daily, and run hourly.
Isaac Bowen (team@usemechanic.com)
This task features products on a schedule, optionally publishing/unpublishing as they're featured/unfeatured. Use this task to make available exclusive products on the hourly/daily/etc, or simply to showcase a rotating selection of your best products.
Runs when a user triggers the task. Configuration includes product ids to be featured, featured collection, number of products to feature at once, manage product publishing, maximum number of times to feature a product, price multiplier for featured products, tag to add after a product has been featured for the last time, run hourly, and run daily at midnight.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Use this task to easily set the shipment status of your single-fulfillment orders. Just add a tag, and a new fulfillment event will be recorded, using the corresponding shipment status.
Runs when an order is updated. Configuration includes shipping status tags.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task and when a refund is created. Configuration includes cancel pending fulfillments, cancel open fulfillments, and cancel successful fulfillments.
Isaac Bowen (team@usemechanic.com)
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 when a product is created, when a product is deleted, and when a product is updated. Configuration includes recipient email.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task. Configuration includes invitation email subject, invitation email body, and only invite customers with this tag.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 2 days after a collection is created. Configuration includes email recipient, email subject, email body, and days to wait before checking.
Isaac Bowen (team@usemechanic.com)
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 when 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.
Isaac Bowen (team@usemechanic.com)
Keeps a cached list of all the passcodes associated with a visitor, and upon sign-in or checkout, saves that list to the customer's "note" field in Shopify. (Requires activation of Locksmith webhooks - hit up team@uselocksmith.com to get started with those.)
Runs when Locksmith sends a session ping and when an order is created.
Mechanic Team (team@usemechanic.com)
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 when an order is created and when a user triggers the task. Configuration includes required customer tag and remove tag from customer after processing their order.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when a customer is created. Configuration includes getresponse api key and getresponse list token.
Isaac Bowen (team@usemechanic.com)
Have your referral partners send customers using ?ref=referral-code-here URLs, then use this task to automatically tag each customer's order according to the ref code they arrived with. (The referral code will be saved in a browser cookie for one year.)
Runs when an order is created.
Isaac Bowen (team@usemechanic.com)
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 when an order is fulfilled.
Isaac Bowen (team@usemechanic.com)
Use this task to sell a single product in different pack sizes, keeping inventory levels synchronized appropriately, storing the "master" inventory level in a product tag (e.g. "inventory:50").
Runs when an order is created, when a product is created, and when a product is updated. Configuration includes product inventory tag prefix, variant pack size option name, variant pack size metafield namespace, variant pack size metafield key, and run when orders are paid instead of when they are created.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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. This task also supports sending invitations in bulk, to all tagged customers who haven't previously been invited.
Runs when a customer is created, when a customer is updated, and when a user triggers the task. Configuration includes tag to watch for, ignore tag case, invitation email subject, and invitation email body.
Isaac Bowen (team@usemechanic.com)
Use this task to add tags to your products, based on their options, for easy filtering. For example, use this task to tag your shirts with "Color-Blue" and "Size-XL", allowing products to be easily located by what options they offer.
Runs when a product is created, when a product is updated, and when a user triggers the task. Configuration includes product options to consider.
Isaac Bowen (team@usemechanic.com)
Use this task to easily contact all of your customers at once, optionally filtering by customer tag.
Runs when a user triggers the task. Configuration includes only send to customers having this tag, email subject, and email body.
Isaac Bowen (team@usemechanic.com)
You know what's worth celebrating? SPACE. Use this task to activate a discount code every time the International Space Station passes over your store (or some other location of your choice), powered by Mechanic webhooks, IFTTT, and NASA. 🚀
Runs when user/space/iss is triggered. Configuration includes discount code, notification email address, and discount percentage.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when an inventory level is connected, when an inventory level is updated, and when a user triggers the task. Configuration includes metafield namespace and location ids and metafield keys.
Mechanic Team (team@usemechanic.com)
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 when a user triggers the task and every 10 minutes. Configuration includes product types to monitor.
Isaac Bowen (team@usemechanic.com)
This task watches for order cancellations, and adds or removes tags according to your preference.
Runs when an order is updated and when a user triggers the task. Configuration includes tags to add and tags to remove.
Isaac Bowen (team@usemechanic.com)
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 when a product is created. Configuration includes track inventory using shopify and allow orders for out of stock products.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Short and simple. :) Upon the fulfillment of an authorized order, this task attempts to capture payment for that order.
Runs when an order is fulfilled.
Isaac Bowen (team@usemechanic.com)
Use this task to tag customers who reach a certain spending threshold, by scanning a rolling period of order history. Useful for rewarding customers who keep a consistent spend total.
Runs when a user triggers the task, every day at midnight, when an order is created, when an order is updated, and when an order is deleted. Configuration includes minimum total spent, customer tag, and days of order history to consider.
Isaac Bowen (team@usemechanic.com)
This task works by monitoring the number of orders created per day, and clearing the inventory for all in-stock items when the daily order limit is reached. Optionally, this task can restore inventory to its original levels at midnight the next day, or on demand.
Runs when an order is created and every day at midnight. Configuration includes maximum daily orders, only clear inventory for products with this tag, restore inventory levels the next day, and restore inventory levels on demand.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes cart attribute to monitor and cart attribute values and tags to add.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task and every 10 minutes. Configuration includes product types to monitor.
Isaac Bowen (team@usemechanic.com)
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 when user/paypal/ipn is triggered. Configuration includes send receipt, default memo, order requires shipping, mark as fulfilled, and send fulfillment receipt.
Isaac Bowen (team@usemechanic.com)
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 18 hours after every Monday at midnight, 18 hours after every Tuesday at midnight, 18 hours after every Wednesday at midnight, 18 hours after every Thursday at midnight, 18 hours after every Friday at midnight, 14 hours after every Saturday at midnight, and 14 hours after every Sunday at midnight. Configuration includes collection.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when a user triggers the task. Configuration includes discount codes and tags and untag customers instead of tagging them.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Mechanic Team (team@usemechanic.com)
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 when a customer is updated and when user/customers/expire_tax_exempt is triggered. Configuration includes tax exempt tag and days before removing tax exempt status.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when a user triggers the task. Configuration includes tag to add.
Isaac Bowen (team@usemechanic.com)
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 when an order is paid and 12 months after user/membership/renewal is triggered. 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.
Isaac Bowen (team@usemechanic.com)
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 order, marking the order as paid if you so chose.
Runs when a user triggers the task and every day at midnight. Configuration includes draft order tag, cycle start date, number of days in cycle, complete the order after creating, complete the order and mark as paid after creating, send email invoice after creating, email invoice subject, email invoice bcc, and email invoice custom message.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Use this task to make a single product or page available for a limited window of time, on a monthly basis. Redirect your visitors to a specific page when that resource is unavailable.
Runs when a user triggers the task and every day at midnight. Configuration includes resource type, resource, day of the month to publish resource, day of the month to unpublish resource, and redirect url when resource is not published.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes tags and required skus.
Isaac Bowen (team@usemechanic.com)
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 when a user 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.
Mechanic Team (team@usemechanic.com)
This task auto-captures payment if the customer has selected a certain shipping method. Useful for expedited order fulfillments.
Runs when an order is created. Configuration includes allowed shipping methods.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
This task applies the tag of your choice to incoming orders, based on the risk level determined for the order. Run this task manually to tag all orders in your store's records, according to their respective risk levels. Combine this task with an email task, to email customers when their order is flagged.
Runs when an order is updated and when a user triggers the task. Configuration includes risk levels and tags.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task, when user/reorder_collection/stage_2 is triggered, and when user/reorder_collection/stage_3 is triggered. Configuration includes base sort order, collection titles or ids, run hourly, and run daily.
Isaac Bowen (team@usemechanic.com)
Using Fulfillment By Amazon for your business? Stay on top of your customer experience by getting notified whenever FBA is unable to fulfill your order.
Runs when a fulfillment is created and when a fulfillment is updated. Configuration includes email recipient, email subject, and email body.
Isaac Bowen (team@usemechanic.com)
This task monitors incoming orders, and tags them with information about the customer's web browser.
Runs when an order is created and when a user triggers the task. Configuration includes include browser version.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Offer free samples to your customers at a nominal fee, and offer them that value back as a discount on a future order. This task generates a discount code, good for the amount of the sample order, and emails it to the customer.
Runs when an order is paid. Configuration includes sample order total, number of days before discounts expire, email subject, email body, and number of hours to wait.
Mechanic Team (team@usemechanic.com)
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 when a customer is updated and when 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.
Isaac Bowen (team@usemechanic.com)
The merchant who requested this task removed the first- and last-name fields from their storefront's registration form, to speed up the customer signup process. This task fills in those blanks by copying the customer's name from the billing or shipping address (whichever is available), upon their first purchase.
Runs when an order is created.
Isaac Bowen (team@usemechanic.com)
This task scans all orders (optionally filtering by the query of your choice), and copies any new timeline comments to the customer's note. Useful for getting a snapshot of order activity when looking at the customer's record. Runs manually, hourly, and/or daily.
Runs when a user triggers the task. Configuration includes only scan orders matching this query, add new comments to the beginning, comment date format, run daily, and run hourly.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Mechanic Team (team@usemechanic.com)
This task applies customer tags based on how many orders they've placed. Add multiple tags, with a minimum orders count each, to advance your customers through different tiers as they place more orders. Optionally, only keep the customer tag with the highest matching order minimum.
Runs when a customer is created, when a customer is updated, and when a user triggers the task. Configuration includes order count minimums and tags, only keep the tag for the highest minimum count, and only tag customers with an active account.
Isaac Bowen (team@usemechanic.com)
Add a tag, have the order automatically archived/closed. Simple. :)
Runs when an order is created, when an order is updated, and when a user triggers the task. Configuration includes required tag.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task and every day at midnight. Configuration includes date metafield namespace and date metafield key.
Isaac Bowen (team@usemechanic.com)
Use this task to sell vouchers for future purchases. Buy a product, receive an emailed discount code for a discount on another specific product.
Runs when an order is paid. Configuration includes voucher product ids and entitled product ids, discount code prefix, discount value, email subject, and email body.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when an inventory level is updated and when an inventory level is connected. Configuration includes email recipient, email subject, and email body.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and when user/orders/send_vendor_email is triggered. Configuration includes vendors and email addresses, email subject, and email body.
Isaac Bowen (team@usemechanic.com)
Keep customers happy by making sure your vendors have up-to-date shipping information. This keeps your vendors happy, too!
Runs when an order is created and when an order is updated. Configuration includes vendor email configuration, email subject, and email body.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes required product tag, team email, email subject, and email body.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Ken Parelius (team@usemechanic.com)
This task allows you to send an email to someone when a certain variant is purchased. Requires the variant ID.
Runs when an order is paid. Configuration includes email address, email subject, email body, reply to email address, and variant.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task. Configuration includes query, test mode, and live mode.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task, when a product is created, and when a product is updated. Configuration includes product tags and template suffixes.
Mechanic Team (team@usemechanic.com)
This task immediately 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, and attempt to void or refund payment.
Runs when an order is updated. Configuration includes cancellation reason, attempt to void or refund payment for cancelled orders, email customer when cancelling, and add this order tag when cancelling.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
This task watches for newly-created orders, and checks each line item for that variant's total inventory quantity. If the inventory quantity is 0 or less, the task will add the tag of your choice to the order (unless the order already has that tag).
Runs when an order is created. Configuration includes apply this order tag.
Mechanic Team (team@usemechanic.com)
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 when an inventory level is updated and when a user 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.
Isaac Bowen (team@usemechanic.com)
This task formats the publish date of each product (according to the format you choose), adds a prefix (also of your choosing), and applies it to each product.
Runs when a user triggers the task, when a product is created, and when a product is updated. Configuration includes date format and tag prefix.
Isaac Bowen (team@usemechanic.com)
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 9 hours after every Monday at midnight, 9 hours after every Tuesday at midnight, 9 hours after every Wednesday at midnight, 9 hours after every Thursday at midnight, 9 hours after every Friday at midnight, 10 hours after every Saturday at midnight, and 10 hours after every Sunday at midnight. Configuration includes collection.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Useful for quickly preparing labels, or planning a drop-off route.
Runs when a user triggers the task. Configuration includes orders search query, include name in formatted address, include company in formatted address, and csv email recipient.
Isaac Bowen (team@usemechanic.com)
Use this task to record which Locksmith passcodes your customer used, before placing their order.
Runs when Locksmith sends a session ping and when an order is created. Configuration includes note prefix.
Isaac Bowen (team@usemechanic.com)
Use this task to prompt your users for a code, redirecting them to an appropriate destination based on what they enter. Some assembly required, with sample Javascript and HTML provided. :)
Runs . Configuration includes redirects and codes, require case sensitive codes, and invalid code message.
Isaac Bowen (team@usemechanic.com)
This task automatically fulfills orders on a weekly schedule, fulfilling orders with certain tags on certain days, at certain times, from certain locations.
Runs 11 hours after every Monday at midnight, 9 hours after every Tuesday at midnight, 12 hours after every Wednesday at midnight, and when a user triggers the task. Configuration includes notify customer on fulfillment, order tags and weekly fulfillment schedule, and order tags and location names.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (isaac@lightward.com)
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 when a collection is created and when a collection is updated. Configuration includes collection tag and collection.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes tag to add.
Isaac Bowen (team@usemechanic.com)
This task manages your published product catalog, 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 every day at midnight and when a user triggers the task.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task and every day at midnight. Configuration includes tag for any, tag for open, tag for submitted, tag for won, and tag for lost.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when an order is created and when a user triggers the task. Configuration includes standardize billing postcodes, standardize shipping postcodes, and only scan open orders when running manually.
Isaac Bowen (team@usemechanic.com)
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.
Runs when a user triggers the task and every day at midnight. Configuration includes out of stock quantity, report recipient email, and report subject.
Isaac Bowen (team@usemechanic.com)
Keep your draft order list tidy - use this task to automatically delete orders that are older than a configurable number of days.
Runs when a user triggers the task. Configuration includes days to wait before deleting a draft order, test mode, and run daily.
Isaac Bowen (team@usemechanic.com)
This task appends order notes to the related customer's note, whenever the order note changes.
Runs when an order is created and when an order is updated. Configuration includes note prefix.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
Use this task to make repeat business easy. Set the number of days to wait, then let this task automatically email your customers a one-click reorder link X days after their purchase, sending them straight to checkout with their entire cart pre-filled.
Runs 30 days after an order is paid. Configuration includes order referral code, email subject, email body, and days to wait.
Isaac Bowen (team@usemechanic.com)
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 when some text is submitted and 12 hours after user/orders/remove_note is triggered. Configuration includes order note to add.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes customer tags and assigned email recipients, email subject, and email body.
Isaac Bowen (team@usemechanic.com)
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.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Mechanic Team (team@usemechanic.com)
Use this task to easily keep track of who's responsible for which orders. Works for draft orders, too!
Runs when an order is created and when a draft order is created. Configuration includes tag orders, tag draft orders, and staff names and tags.
Isaac Bowen (team@usemechanic.com)
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 when a fulfillment is created. Configuration includes default tracking number.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task, when an order is created, and when an order is paid. Configuration includes metafield namespace, metafield key, donation product handle, and recalculate nightly.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes product vendor, email subject, email body, and number of days to wait before sending email.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 every day at midnight and when a user triggers the task.
Isaac Bowen (team@usemechanic.com)
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. You can choose between a threshold defined by line item quantity (for the total number of units sold), by line item subtotals (for the total amount of money each product earned), or by number of orders (for the total number of times a customer placed an order including that product). You can also reconfigure the query used to fetch orders, to get specific about what orders you want to consider.
Runs when a user triggers the task and every day at midnight. 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.
Isaac Bowen (team@usemechanic.com)
This task monitors purchases for a specific product ID, and raises the price every time it's purchased, by the amount that you specify. (To be specific, this task will raise the price on the _individual variant_ that was purchased.)
Runs when an order is paid. Configuration includes product, increase price by this much, and maximum price.
Isaac Bowen (team@usemechanic.com)
Selling scheduled events? Using this task, you can automatically tag customers after the event has been completed. Simply tag a product with "autotag Authorized May 15", for example, and Mechanic will tag purchasers of that product with "Authorized", on May 15th.
Runs when an order is paid and when user/autotag/customer is triggered. Configuration includes autotag prefix.

Not seeing the task you need? Submit a request, from within the app. You can also use that chat button in the corner. :)

Know a bit of code? Create your own task! It’s easy, and we have lots of documentation.

Isaac Bowen (team@usemechanic.com)
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 when a customer is created and when 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.
Mechanic Team (team@usemechanic.com)
This task will monitor incoming orders for any products that are included in the collection you choose.
Runs when an order is paid. Configuration includes required collection, email address, email subject, and email body.

Custom task

Do it yourself, or get in touch
It’s easy and fast to create custom tasks for Mechanic. If you’re a developer or are comfortable with some Liquid code, get started with that button over there. Otherwise, just log into the app to post a task request.