Skip to content

Compose using Liquid for Azure Logic Apps

Compose using Liquid for Azure Logic Apps

Render Liquid templates as a built-in action in Logic Apps Standard: JSON or XML in, JSON or exact text out. Beyond standard Liquid, templates can call C# helper methods compiled with Roslyn, look values up in Azure Functions, read XML with XPath, and write safe JSON, with every render in a supervised worker process that has a hard deadline.

Service provider/serviceProviders/lamboLiquidComposeOperation ComposeLiquid, shown in the designer as Compose using Liquid.

Step 1

Get started

What the action does, how it is licensed, what you need, and a first workflow.

IntroductionWhat Compose using Liquid does, and how it differs from the Logic Apps Liquid action.LicensingDeveloper, trial and production licenses, the LAMBOGENIUS_LICENSE setting, and where no license is needed.RequirementsThe Logic Apps project type, runtime and tools the action needs.Quick startInstall the package, add the connection and a template, and run a workflow locally.

Step 2

Use the action

Inputs and outputs, templates, parameters and workflow variables, C# helpers, Azure Functions, and XML with XPath.

Inputs and outputsEvery input of the ComposeLiquid action and what it returns.TemplatesDeployed and inline templates, partials, template folders, whitespace, filters and ToJson.Parameters and variablesPass values from app settings, workflow parameters, the trigger and workflow variables, and read typed results back.C# helpersThe csharp block, CallCSharp, what helpers may do, and how they are compiled and stopped.Azure FunctionsCall HTTP-triggered Functions from templates with CallFunction, the registry, authentication and the wire contract.XML and XPathRead XML content with XmlValue and XmlValues, namespace prefixes, and what XPath may select.

Step 3

Samples

Eight runnable Logic Apps with checked demos.

SamplesEight runnable Logic Apps covering every mode, workflow variables and every kind of failure.

Step 4

Operate

Settings and limits, error codes, deploying to Azure, and fixing common problems.

Configuration and limitsApp settings for templates, scripts, workers and Functions, retries, and the size and time limits.Error codesEvery error code, its HTTP status, and how a workflow reads it.Deploy to AzureWhat the Logic App needs in Azure, publishing the package's worker, identities and checks after deployment.TroubleshootingCommon problems and how to fix them.