Liquid
Safe template language created by Shopify.
Liquid is an open-source template language created by Shopify and used in Shopify themes, Jekyll, and many hosted applications. Its main fit for email is safe user-editable templates, stored templates, and commerce-style dynamic content.
An agent stack treats email as a two-way primitive. Inbound has to arrive as structured JSON a tool call can consume, sends have to be safe to retry when a model loop repeats itself, and every action needs an audit trail. A provider without inbound parsing only solves half the problem.
Against inbound parsing into tool calls and model-generated sends that must not duplicate, Liquid covers SDK breadth, and does not cover inbound parsing, idempotency keys, webhook coverage, event stream, batch sending, and multi-tenant support. Whether that gap matters depends on how central those are to the build.
- Inbound parsing: No
- Idempotency keys: No
- Webhooks: No
- Operating since: Not published
- Event stream: No
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: No
- SDKs: ruby
- Multi-tenant: No
Not applicable; template language only.
Products that need safe, user-editable email templates or Shopify-adjacent personalization.
Teams that want a full responsive email design system out of the box.
- › Designed for safe customer-facing template editing
- › Strong fit for stored templates and ecommerce-style personalization
- › MIT-licensed and well documented
- › No email layout framework or rendering compatibility layer by itself
- › Many real-world Liquid variants differ from core Liquid behavior
- › Ruby-first official implementation may not match every stack preference
Features at a glance
| API | No |
| SMTP | No |
| SDKs | ruby |
| Webhooks | No |
| Templates | basic |
| React Email | No |
| Batch send | No |
| Scheduled send | No |
| Suppressions | No |
| Multi-tenant | No |
| Inbound parsing | No |
| Event stream | No |
| Idempotency keys | No |
| Dedicated IP | No |