> 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/tags.md). # Mechanic tags Custom Liquid tags in Mechanic — action, log, error, permissions, and more for producing task output. Mechanic extends Liquid with custom tags that go beyond what standard Liquid provides. These tags are how tasks produce output — defining actions, logging data, raising errors, and more. ## Available tags * [action](/platform/liquid/tags/action.md) — defines an [action](/core/actions.md) to be performed after the task finishes rendering (e.g. a Shopify API call, an email, an HTTP request) * [log](/platform/liquid/tags/log.md) — outputs structured data to the task run's log, useful for debugging and auditing * [error](/platform/liquid/tags/error.md) — raises an error that halts the task run and marks it as failed * [assign](/platform/liquid/tags/assign.md) — an enhanced version of Liquid's assign tag, with support for nested hash key assignment * [permissions](/platform/liquid/tags/permissions.md) — explicitly declares Shopify access scopes the task requires, supplementing Mechanic's automatic permission detection * [liquid](/platform/liquid/tags/liquid.md) — evaluates a string as a Liquid template at runtime, useful for dynamic template rendering --- # 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/tags.md?ask=&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.