Mechanic is an automation development platform, for Shopify.

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

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)
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.
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, void payment when possible, cancel fulfillment and restock to default location, send cancellation email to customer, and tag to add to the order.
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.

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)
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. Run this task manually to tag all customers who have a paid order already on file for a qualifying product.
Runs when an order is paid, when a user triggers the task, and when a bulk operation finishes. Configuration includes required product title, required product tags, and customer tags to apply.
Isaac Bowen (team@usemechanic.com)
This task monitors inventory updates, and pulls the product from the selected 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. This task can also be run manually, to scan all products at once.
Runs when a user triggers the task and when an inventory level is updated. Configuration includes sales channel names, email notification recipient, and out of stock inventory quantity.
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 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 not yet been invited, 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.

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 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.
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.
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.
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)
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)
This task sends repeating/looping reminders to customers, reminding them every x days (or hours!) about unpaid orders, until the order is no longer "pending" or until the order is cancelled.
Runs when an order is created and 1 days after user/orders/unpaid_reminder is triggered. Configuration includes number of days to wait between emails, use hours instead of days, send the first email when the order is created, email subject, and email body.
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)
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.

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 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 7 days after an order is created. Configuration includes email subject, email body, tag to add to the order, number of days to wait, and use hours instead of days.
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 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.
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)
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.

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)
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)
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)
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)
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.

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 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 (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 and when user/memberships/expire is triggered. Configuration includes membership product title, membership tag, days to wait before untagging, and remove tag immediately for cancelled orders.
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)
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.

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)
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)
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)
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.

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 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)
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.
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 watches for newly-created orders, and copies any discount codes present to the order's tags.
Runs when an order is 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)
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.
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 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)
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.

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-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 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.
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.
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.

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)
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.
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)
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 tag prefix, ignore refunded purchases, enable running manually, customer query when running manually, and use test mode when running manually.
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.

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 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 when a user triggers the task and when a bulk operation finishes. 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.
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 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 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.
Ken Parelius and Isaac Bowen (team@usemechanic.com)
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.
Runs when 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.
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.

Isaac Bowen (team@usemechanic.com)
This task runs immediately after an order is created, and captures an authorized transaction if one is present. Choose which risk levels to capture for, and optionally choose to filter by order tag. You may also choose to only capture funds for line items that do not require shipping.
Runs when an order is created. Configuration includes number of minutes to wait before capturing, capture orders with a high risk level, capture orders with a medium risk level, capture orders with a low risk level, required order tag, and only capture for line items that do not require shipping.
Isaac Bowen (team@usemechanic.com)
This task watches for cancellations of orders that have a single-use discount code. When one is found, this task creates a new single-use discount code, for the related customer, and emails it to them.
Runs when an order is cancelled. Configuration includes ignore discount codes containing this text, email subject, email body, and email bcc.
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 easily contact all of your customers at once, optionally filtering by customer tag. Important: This task can only be used in a transactional context - it cannot be used be used for marketing emails, or any type of message that would require an unsubscribe link.
Runs when a user triggers the task. Configuration includes only send to customers having this 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)
Useful for keeping an eye on unexpected cancellations by third party shipping services.
Runs when a fulfillment is updated. Configuration includes email recipient, email subject, and email body.
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.
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)
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.

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 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 and when a user triggers the task. Configuration includes customer email domains and customer tag to apply.
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 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.
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.

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 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)
Use this task to receive an immediate email alert, whenever a variant's total inventory hits 0, when added up across all locations.
Runs when an inventory level is updated. Configuration includes email subject, email body, and email recipient.
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)
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.
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)
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.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task. Configuration includes product tags and maximum age in days, use product publish times instead of creation times, 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.

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)
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)
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.
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.

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 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.
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.
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)
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.

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 an email alert whenever a single customer exceeds a configurable order count, over the last configurable number of hours.
Runs when an order is created. Configuration includes order count threshold, number of hours to look back, email recipient, email subject, and email body.
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.
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.
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, ignore unpaid orders, 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)
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.
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)
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 when an inventory level is updated. Configuration includes minimum inventory level, location, 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.
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)
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 vendors and email addresses, email body, and email subject.
Isaac Bowen (team@usemechanic.com)
This task watches for incoming orders, and tags them if they contain a product that matches by title or by product tags. Run this task manually to scan your store's order history, tagging older orders that qualify.
Runs when an order is created, when a user triggers the task, and when a bulk operation finishes. Configuration includes required product title, required product tags, and order tags to apply.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task and when a bulk operation finishes.
Isaac Bowen (team@usemechanic.com)
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 5 days after an order is fulfilled. Configuration includes test mode, qualifying fulfillment statuses, klaviyo api token, klaviyo event name, and days to wait before checking.

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 user triggers the task and when a collection is updated. Configuration includes collection tag and collection.
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.
Isaac Bowen (team@usemechanic.com)
Run this task to scan all of your customers and their order histories in bulk, 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 - useful for adding customer tags that expire after ordering!
Runs when a user triggers the task and when a bulk operation finishes. 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.
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.

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 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)
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)
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 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.

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)
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 when 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.
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.
Isaac Bowen (team@usemechanic.com)
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 every day at midnight and when a user triggers the task. Configuration includes dates and tags to add, dates and tags to remove, product ids, use hour specificity, and test mode.
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.

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 print price tags whenever a SKU is added? Use this task to tag products that need your attention, whenever their SKUs change.
Runs when a user triggers the task, when a product is created, and when a product is updated. Configuration includes product tag to add and tag with the titles of each variant having a new sku.
Isaac Bowen (team@usemechanic.com)
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 when a draft order is created, when a user triggers the task, and when a bulk operation finishes. Configuration includes tag prefix.
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 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 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.
Ken Parelius (team@usemechanic.com)
This task automatically adds the tag of your choice to incoming orders, based on the country in the order's shipping address.
Runs when an order is created. Configuration includes country code and tag to apply.
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)
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.

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 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 when an order is created and when 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.
Isaac Bowen (team@usemechanic.com)
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 when an order is created. Configuration includes order tag value.
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)
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.

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)
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.
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 keep track of who created what order. This task watches for new orders, and tags each one with the name of the store staff member who created it (if that's how the order was created). This task can also be run manually, to scan and tag all orders already in your store.
Runs when an order is created, when a user triggers the task, and when a bulk operation finishes. Configuration includes include pos orders and tag 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 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 when a user triggers the task and when a bulk operation finishes. 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.
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.
Isaac Bowen (team@usemechanic.com)
This task monitors all variants having a SKU that you configure, and ensures that changes to inventory quantity are reflected across all variants sharing that SKU.
Runs when a user triggers the task and every 10 minutes. Configuration includes product skus to monitor.
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 user triggers the task, when a product is created, and when a product is updated. Configuration includes product options to consider and run for products when they are created or updated.

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 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 when a customer is created and when 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.
Isaac Bowen (team@usemechanic.com)
Use this task to tag orders, as they are created, if every single line item is related to a variant that's in stock. Optionally, choose to tag qualifying unfulfilled orders whenever an inventory level is updated.
Runs when an order is created and when a user triggers the task. Configuration includes ignore line items not fulfilled manually, order tag to add, scan unfulfilled orders when inventory is updated, test mode, run every 10 minutes, and run hourly.
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.
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.

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 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 when an order is updated. Configuration includes email trigger tag, email sent tag, email subject, and email body html.
Isaac Bowen (team@usemechanic.com)
Useful for enforcing order limits on the backend, use this task to ensure that too many of a certain product cannot be purchased. This task can be configured with multiple SKUs, too!
Runs when an order is created. Configuration includes skus to watch for, quantity threshold for cancellation, send cancellation email to customer, attempt to refund or void payment in full, and reason for cancellation.
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.
Isaac Bowen (team@usemechanic.com)
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 when a product is created. Configuration includes sales channel 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 (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)
Use this task to automatically remove a certain customer tag whenever a particular product is refunded, for that customer.
Runs when a refund is created. Configuration includes product ids and customer tag to remove.
Isaac Bowen (team@usemechanic.com)
This task re-sorts your chosen collections by any product property that you choose. A property lookup can be something simple, like "published_at", or more complicated: use multiple property lookups, like "metafields", "store", and "priority", to sort collections by product metafield values.
Runs when a user triggers the task. Configuration includes product property lookups, reverse sort, collection titles or ids, run hourly, and run daily.
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.

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.
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 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)
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.

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 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 when a user triggers the task. Configuration includes metafield namespace, metafield key, monitor new products, and test mode.
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.
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.

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 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)
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)
Does exactly as it says: this task will publish all 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 every ten minutes, hourly, or daily.
Runs when a user triggers the task. Configuration includes sales channel names, only publish products matching this query, test mode, run every 10 minutes, run hourly, and run daily.
Isaac Bowen (team@usemechanic.com)
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 when a fulfillment is created, when a fulfillment is updated, when a user triggers the task, and when a bulk operation finishes.

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)
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.
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)
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.

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.
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 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 and when a bulk operation finishes. Configuration includes only process customers matching this query, 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 daily, and run hourly.
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.

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)
An integration with Kount, this task allows you to immediately capture payments for orders that Kount has deemed to be of a certain risk level.
Runs when an order is created. Configuration includes number of minutes to wait before capturing, capture orders with a high risk level, capture orders with a medium risk level, and capture orders with a low risk level.
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)
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 when an inventory level is updated, when a user triggers the task, and when a bulk operation finishes. Configuration includes back in stock inventory level, product tags and maximum age in days, run daily, and run hourly.
Isaac Bowen (team@usemechanic.com)
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 when a user triggers the task. Configuration includes collection, number of products to delete at once, test mode, and run daily.

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)
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.
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)
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.
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.

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 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 when a bulk operation finishes and when a user 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.
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)
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.
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.

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.
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)
This task monitors customer accounts, and applies the tag of your choice to customers that have an enabled account, with a registered email address and active password. It untags customers whose accounts are disabled. This task can be run manually to tag/untag all existing customers.
Runs when a customer is created, when a customer is updated, and when a user triggers the task. Configuration includes customer tag to apply and test mode.
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.

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 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 14 days after an order is fulfilled. 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.
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)
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.
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.

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.
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.
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)
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, from whichever sales channel you select. 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 when a user triggers the task and when a bulk operation finishes. 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.

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 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)
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)
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.
Mechanic Team (team@usemechanic.com)
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 when an order is created and when 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, 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.

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)
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 when an inventory level is updated, when a user triggers the task, and when a bulk operation finishes. 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.
Isaac Bowen (team@usemechanic.com)
This task watches for incoming updates to inventory levels, and auto-tags the product according to the largest in-stock size. This task is specifically made to work with numeric variant options (e.g. "10", "11", "12", etc).
Runs when an inventory level is updated, when a user triggers the task, and when a bulk operation finishes. Configuration includes largest size tag prefix, size option name, minimum number of variants in stock before tagging, and run daily.
Isaac Bowen (team@usemechanic.com)
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 when a fulfillment is created. Configuration includes tracking number prefix to add and notify customer.

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)
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.
Isaac Bowen (team@usemechanic.com)
Purely for demonstration purposes, this task illustrates how one might set up a script to send Slack messages.
Runs when a user triggers the task. Configuration includes slack incoming webhook url.
Isaac Bowen (team@usemechanic.com)
Short and simple. Captures order payment for un-cancelled orders that have a financial status of "authorized", after waiting 30 days (or another timespan of your choice).
Runs 30 days after an order is created. Configuration includes days to wait before capturing.
Ken Parelius (team@usemechanic.com)
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 when an order is created. Configuration includes city and 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.

Isaac Bowen (team@usemechanic.com)
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 when a customer is created. Configuration includes ignore customers having this tag.
Isaac Bowen (team@usemechanic.com)
Useful when you discover that an order shouldn't have been fulfilled at all. :) After choosing an order tag in this task's configuration, add that tag to any order to have its fulfillments all cancelled, and the tag removed.
Runs when an order is updated and when user/orders/cancel_fulfillment is triggered. Configuration includes required order tag.
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.
Isaac Bowen (team@usemechanic.com)
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 when an order is created and every day at midnight. Configuration includes use rolling 24 hour window and order 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)
Just as it says. :) Archives orders immediately upon fulfillment, or after a configurable number of days.
Runs when an order is fulfilled. Configuration includes days to wait after fulfillment before archiving.
Isaac Bowen (team@usemechanic.com)
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 when a product is created and when a product is updated. Configuration includes product tags and collection ids.
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)
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 when a user triggers the task and when a bulk operation finishes. Configuration includes 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.

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.
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)
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)
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.

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 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.
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 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.
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.

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 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 when 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.
Isaac Bowen (team@usemechanic.com)
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 when a fulfillment is created and when a fulfillment is updated. Configuration includes 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.