Comment on page
Shopify admin action links
Use these access points within the Shopify admin to send resources like orders and customers to Mechanic for processing.
For supported resources, you'll find "Send to Mechanic" links within the Shopify admin. These links point to a Mechanic app URL that translates selected Shopify resources into Mechanic events for on-demand processing. Depending on the user's resource and task selections, their submission may result in one or more new events. Event data consists of the latest stable REST Admin API representation of the selected resource(s).
Tasks can qualify for this style of on-demand Shopify resource processing by subscribing to event topics like mechanic/user/{resource} (singular) for individual processing, and mechanic/user/{resources} (plural) for batch processing. See Supported resources below for a complete table of resources and event topics.
Shopify admin action links are a form of run link, and as such equivalent URLs may be constructed manually using known resource IDs. For example, an admin order notification email could be written to include such a link, allowing the email recipient to send the relevant order to Mechanic.
Resource object | URL parameter | Individual mode event topic | Batch mode event topic |
|---|---|---|---|
customer | mechanic/user/customer | mechanic/user/customers | |
order | mechanic/user/order | mechanic/user/orders | |
draft_order | mechanic/user/draft_order | mechanic/user/draft_orders | |
product | mechanic/user/product | mechanic/user/products | |
variant | mechanic/user/variant | mechanic/user/variants | |
collection | mechanic/user/collection | |
Mechanic distinguishes between "individual" and "batch" modes to enable a greater variety of possible workflows. Some tasks may benefit from having knowledge of all selected resources at the same time within the same task run, while some tasks may be more suited to receiving a single resource at a time.
For example, tasks that are created to print deliberately-sorted pick lists might benefit from batch mode, whereas tasks aimed at refunding specific orders might benefit from individual mode.
This mode creates an event for each selected Shopify resource, resulting in as many events as there were selected resources. Tasks subscribing to an individual mode event topic (e.g. mechanic/user/order or mechanic/user/customer) may use an environment variable named after the singularized resource name, e.g.
order or customer.{% log product_title: product.title %}
This mode creates one (1) event whose data consists of an array holding all selected Shopify resources, up to a maximum of 50 resources total. No matter how many resources were selected, only one event is created. Tasks subscribing to a batch mode event topic (e.g. mechanic/user/orders or mechanic/user/customers) may use an environment variable named after the pluralized resource name, e.g.
orders or customers.{% for product in products %}
{% log product_title: product.title %}
{% endfor %}
For supported Shopify resources, the "Send to Mechanic" action link can be found in the "More actions" menu. Click this link to route the currently-viewed Shopify resource to Mechanic.
A Shopify admin action link on the details page for a specific order
For supported Shopify resources, the "Send to Mechanic" link is also available as a bulk action, supporting selections of up to 50 resources at once. Find the "Send to Mechanic" link after in the menu of additional actions, in the floating action list that appears after selecting one or more resources.
A Shopify admin action link on a list of orders
Sending one (1) resource to Mechanic via bulk action (on a resource list page) is the same as sending an individual resource to Mechanic via the "More actions" menu (on that resource's detail page). The two paths arrive in the same place, and the choice between batch mode and individual mode is available either way.
https://admin.shopify.com/store/$SHOP_NAME/apps/mechanic/tasks/run?resource_type=$RESOURCE_TYPE&ids[]=123&ids[]=456
These URLs may be manually constructed, using resource type parameter values drawn from the Supported resources table above, and using integer REST resource IDs.
Using a Shopify admin action link brings the user to the page shown below, in which selected resources are shown for preview, and a choice of processing mode is offered.
Select to send your resources as an array of resources in a single event, or as a single resource in many events
After selecting a processing mode, select from the available compatible tasks – i.e. from enabled tasks that subscribe to a relevant event topic. You can send this event to one or more tasks that subscribe to the correct event topic.
To qualify a task to receive these events, subscribe to an event topic from the Supported resources table above.
For these events, Mechanic makes available an environment variable named after the third term in the event topic. For example, a mechanic/user/order event will make available a variable called
order, which contains an Order object with data pulled from the Shopify Admin REST API. By contrast, a mechanic/user/orders event will make available a variable called orders, which contains an array of Order objects.Event data for these topics is often very similar to data from Shopify events, but there are occasionally differences. For example, shopify/orders/* events do not include customer data. By contrast, customer data is included in the Shopify Admin REST API representation for the Order resource. Therefore, event data for mechanic/user/order and mechanic/user/orders events do contain information about the customer, unlike shopify/orders events.
Your task subscriptions will make them eligible to recieve these events from the Shopify admin
Tasks that already subscribe to related Shopify event topics lend themselves well to invocation via Shopify admin action links. For example, a task subscribing to shopify/orders/create may be adapted to these action links by adding mechanic/user/order to the task's subscriptions.
The Send a PDF invoice when an order is created task, from the Mechanic task library, is well-suited to this kind of adaptation. To illustrate, here is the portion of the task code that addresses the order itself:
1
{% if order.email != blank and order.financial_status == "pending" %}
2
{% action "email" %}
3
{
4
"to": {{ order.email | json }},
5
"subject": {{ options.email_subject__required | strip | json }},
6
"body": {{ options.email_body__multiline_required | strip | newline_to_br | json }},
7
"reply_to": {{ shop.customer_email | json }},
8
"from_display_name": {{ shop.name | json }},
9
"attachments": {
10
{{ options.pdf_attachment_filename__required | json }}: {
11
"pdf": {
12
"html": {{ options.pdf_html_template__code_multiline_required | json }}
13
}
14
}
15
}
16
}
17
{% endaction %}
18
{% endif %}
Because this task straightforwardly references the
order environment variable, this task is a good candidate for a subscription to mechanic/user/order. Once modified in that way, the task will be able to send PDF invoices on demand, whenever a user sends orders to the task via a "Send to Mechanic" link.Last modified 10d ago