> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/platform/liquid/objects.md).

# Mechanic objects

Mechanic's Liquid objects — event, task, options, globals, secrets, cache, action, and Shopify resource objects available in your task code.

Mechanic makes a variety of [**Liquid environment variables**](/core/tasks/code/environment-variables.md) available, containing specific Liquid objects. (The `shop` variable, for example, is always available and always contains the [Shop object](/platform/liquid/objects/shopify/shop.md).)

Shop-level configuration is available through globals and secrets:

{% content-ref url="/pages/Xs7gqkxVZpW2nKp1kHDU" %}
[Globals object](/platform/liquid/objects/globals.md)
{% endcontent-ref %}

{% content-ref url="/pages/JAtdwbC6ZsKsMCqyDOwR" %}
[Secrets object](/platform/liquid/objects/secrets.md)
{% endcontent-ref %}

Mechanic's Liquid objects mapping to Shopify resources all contain data pulled from the [Shopify's REST Admin API reference](https://shopify.dev/docs/admin-api/rest/reference). These objects are listed here:

{% content-ref url="/pages/-MXYcOvurGCqVZqJ91qF" %}
[Shopify REST Admin API](/platform/liquid/objects/shopify.md)
{% endcontent-ref %}

{% hint style="warning" %}
**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](https://shopify.dev/docs/admin-api/rest/reference/customers/customer) does not contain a "name" property). On the other hand, Mechanic supports `customer.created_at`, while Shopify themes do not.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.mechanic.dev/platform/liquid/objects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.