Hi team,
Sharing a customer request for your consideration. The customer is implementing complex Liquid logic within webhook triggers and has encountered limitations related to size and reusability.
They are requesting a way to define reusable Liquid components or objects that can encapsulate complex logic and be referenced across multiple places (such as webhooks, triggers, or dynamic content). This would help reduce duplication, increase flexibility, and make advanced implementations easier to maintain. Primary use cases include rendering HTML content for emails and outputting full ticket conversations for CSAT workflows.
Thanks for taking a look!