In previous chapters, we discussed how to automate business process with Azure Logic Apps and its different concepts such as workflow, connectors, trigger, and actions. In this chapter, we will dive deep into Azure Logic Apps by creating a complex business workflow using features such as control flow, looping, and exception handling. We will look at the Logic Apps code view and play around with the workflow definition language. We will explore the ability to call nested Logic Apps directly from Logic Apps designer.

This chapter introduces the following topics:

Azure Logic Apps provide a new way to automate business processes and running them in reliable way in cloud. Anyone who can use Azure should be able to start building business process that orchestrate data, connect systems, and services across cloud and on-premise resources.

Any workflow that is created in Logic Apps has an associated workflow definition that contains the actual logic that gets executed within the Logic App engine. The workflow definition is a JSON definition file that contains one or more triggers that initiate the Logic app and associated single or multiple actions.

{ 
      "$schema": "<schema-of the-definition>", 
      "contentVersion": "<version-number-of-definition>", 
      "parameters": { <parameter-definitions-of-definition> }, 
      "triggers": [ { <definition-of-flow-triggers> } ], 
      "actions": [ { <definition-of-flow-actions> } ], 
      "outputs": { <output-of-definition> }     
}