Build Logic App workflow definitions with triggers and actions.
Last verified: May 2026
Build Logic App workflow definitions with triggers and actions.
Required Fields
definitiondefinition.$schemaOutput will appear here...The builder generates a Logic App workflow definition JSON conforming to the Workflow Definition Language schema: triggers (Request, Recurrence, EventGrid, Service Bus), actions (HTTP, Compose, Condition/Switch, ForEach, Until), connections (managed connectors with API connection references), and outputs. The output includes the parameters, definition, and connections sections needed for ARM template deployment.
The Azure Logic App Workflow Builder helps you create Logic App workflow definitions with triggers, actions, conditions, and loops. Logic Apps provide a low-code integration platform with hundreds of connectors, but the underlying JSON workflow definition can be complex. This tool provides a visual builder for constructing workflow logic and generates the JSON definition you can deploy via ARM templates, Bicep, or the Azure portal.
Your operations team needs an approval workflow: when a high-cost VM is requested in dev/test, send a Teams message to the team lead, wait for response (Approve/Reject), then either provision or notify the requester of denial. The builder generates the workflow JSON: HTTP trigger receives the request, sends Teams adaptive card via the Teams connector, waits for approval up to 24 hours, branches based on response. End-to-end: 30 minutes to working workflow vs. half-day if hand-crafting the JSON.
Standard Logic Apps support multiple workflows per app, sharing the underlying compute. This is dramatically more cost-efficient than Consumption for high-volume scenarios — instead of paying per execution, you pay flat for the App Service plan and run unlimited workflows. The break-even is typically ~500K actions/month.
Logic App expressions like @triggerBody() and @action('PreviousAction').outputs are powerful but make workflows hard to maintain. For non-trivial logic, prefer using a Function action (Azure Functions) over chained expressions — easier to test, easier to debug, easier to onboard new team members.
Always set a timeout on HTTP actions. The default is 1 hour, which means a hung downstream service will hold a workflow execution open for 60 minutes — racking up costs and blocking parallel executions. A 30-second timeout is typically sufficient and forces sane fallback behavior.
Consumption Logic Apps are multi-tenant, serverless, and billed per action execution. Standard Logic Apps run on a dedicated single-tenant runtime (based on Azure Functions), support multiple workflows per app, offer better performance, and support local development with VS Code. Standard is recommended for enterprise workloads.
The tool generates the JSON workflow definition (code view format) that both Consumption and Standard Logic Apps use under the hood. You can paste this into the Logic App code editor or include it in ARM/Bicep templates for automated deployment.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.