Mechanic
🧑‍💻 Get Mechanic!🧑‍🔧 Task library🗳 Task requests🦾 Mechanic.dev
Search…
Introduction
💯
status.mechanic.dev
🙋
"I need something custom!"
🤓
Hire a Mechanic developer
Resources
🧑💻
Task library
🚀
Slack community
🤝
Partner directory
Tutorials
Core Concepts
Events
Tasks
Actions
Runs
Interacting with Shopify
Platform
🔆
Policies
Cache
Email
Events
GraphQL
Integrations
Liquid
Basics
Filters
Keyword literals
Mechanic objects
Action object
Cache object
Event object
Options object
Task object
REST Admin API
Mechanic tags
Liquid console
Shopify
Webhooks
Techniques
Writing a high-quality task
Tagging Shopify resources
Debouncing events
Responding to action results
Working with external APIs
Finding a resource ID
Migrating templates from Shopify to Mechanic
Securing Mechanic webhooks
Monitoring Mechanic
FAQ
Powered By GitBook
Mechanic objects
Mechanic makes a variety of Liquid environment variables available, containing specific Liquid objects. (The shop variable, for example, is always available and always contains the Shop object.)
Mechanic's Liquid objects mapping to Shopify resources all contain data pulled from the Shopify's REST Admin API reference. These objects are listed here:
Shopify variables in Mechanic do not necessarily contain the same attributes as Liquid variables used in Shopify (in places like themes or email templates) – even if they share the same name.
In Mechanic, Shopify variables always contain data from Shopify events, which are delivered to Mechanic via webhook. This means that Shopify variables always have the same data structure as Shopify webhooks, corresponding to Shopify's REST representation for this data.
For example, while Shopify themes support customer.name, Mechanic does not (because Shopify's REST representation of the customer resource does not contain a "name" property). On the other hand, Mechanic supports customer.created_at, while Shopify themes do not.
Previous
newline
Next
Action object
Last modified 6mo ago
Copy link
Edit on GitHub