- Logic Apps helps build solutions that integrate apps, data, systems, and services across enterprises or organizations
- It automates tasks and business processes as workflows.
- Every logic app workflow starts with a trigger, which fires when a specific event happens, or when new available data meets specific criteria.
- Each time that the trigger fires, the Logic Apps engine creates a logic app instance that runs the workflow's actions.
- These actions can also include data conversions and flow controls, such as conditional statements, switch statements, loops, and branching.
- You can create or edit logic app definitions in JSON by working in "code view" mode.
- You can also use Azure PowerShell commands and ARM (Azure Resource Manager) templates for select tasks.
Key Terms
- Workflow: Visualize, design, build, automate, and deploy business processes as series of steps.
- Managed connectors: Your logic apps need access to data, services, and systems.
- Triggers: Many Microsoft-managed connectors provide triggers that fire when events or new data meet specified conditions.
- For example, an event might be getting an email or detecting changes in your Azure Storage account.
- Each time the trigger fires, the Logic Apps engine creates a new logic app instance that runs the workflow.
- Actions: Actions are all the steps that happen after the trigger.
- Each action usually maps to an operation that's defined by a managed connector, custom API, or custom connector.
- Enterprise Integration Pack: For more advanced integration scenarios, Logic Apps includes capabilities from BizTalk Server.
- The Enterprise Integration Pack provides connectors that help logic apps easily perform validation, transformation, and more.