> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firmhouse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Liquid tags for dynamic content

> Use Liquid tags in Firmhouse email templates, webhooks, and payment descriptions to insert dynamic content like customer names and order details.

Firmhouse uses Liquid tags for dynamic content in email templates, webhooks, and payment descriptions. These tags allow you to personalize communications with customer-specific information like names, order details, and payment status.

## Available Tags

The complete list of available Liquid tags is maintained in our [developer documentation](https://developer.firmhouse.com/liquid/email-template-overview). This includes variables for:

* **Order** - Order amounts, status, tracking codes, confirmation URLs
* **Invoice** - Invoice numbers, amounts, payment URLs, status
* **Subscription** - Customer details, addresses, billing dates, payment methods
* **Payment** - Payment amounts, status, retry information, failure reasons
* **Product** - Product titles, prices, SKUs, images
* **Plan** - Plan IDs, slugs, names, prices, images
* **Project** - Your business/company details

## Using Liquid Tags

Tags are used in the format `{{object.attribute}}`. For example:

* `{{subscription.full_name}}` - Customer's full name
* `{{order.amount}}` - Order total with currency formatting
* `{{invoice.pay_now_url}}` - Link for customer to pay an invoice

Not all variables are applicable to every email type. For example, `{{order.track_and_trace_code}}` is only available in track and trace confirmation emails.

## Localized tag values

Localized Liquid values use the locale of the surface that renders the template:

* My Account Portal templates use the current language from the portal URL. This can differ from the subscription language when the visitor selects another portal language.
* Email templates, webhooks, payment descriptions, and other subscription-based templates use the subscription language.

Raw and localized properties remain separate. For example, `promotion.public_name` returns the original public description, while `promotion.localized_public_name` returns its translation for the rendering locale and falls back to the original description when that translation is blank.

## Ordered product status and recurrence

When iterating over `subscription.ordered_products`, use these fields to distinguish how each item behaves:

* `ordered_product.status` returns `active`, `returned`, or `owned`.
* `ordered_product.recurring` returns `true` when the product recurs and `false` for a one-off item.

For example:

```liquid theme={null}
{% for ordered_product in subscription.ordered_products %}
  {% if ordered_product.status == "active" and ordered_product.recurring %}
    {{ ordered_product.product.title }} renews with the subscription.
  {% endif %}
{% endfor %}
```

## Extra Fields

If you have custom [Extra Fields](https://docs.firmhouse.com/configure/extra-fields.md) configured, you can access them using `{{extra_field.field_name}}`. For example, if you have a birthday field: `{{extra_field.birthday}}`

## Learn More

For the complete and up-to-date list of all available Liquid tags, see the [Firmhouse developer documentation on Liquid](https://developer.firmhouse.com/liquid/email-template-overview).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.