To help you learn more about the many patterns and capabilities in Azure Logic Apps, here are common examples and scenarios.
Key scenarios for logic apps
Azure Logic Apps provides resilient orchestration and integration for different services. The Logic Apps service is "serverless", so you don't have to worry about scale or instances - all you have to do is define the workflow (trigger and actions). The underlying platform handles scale, availability, and performance. Any scenario where you need to coordinate multiple actions, especially across multiple systems, is a great use case for Azure Logic Apps. Here are some patterns and examples.
Respond to triggers and extend actions
Every logic app begins with a trigger. For example, your workflow can start with a schedule event, a manual invocation, or an event from an external system, such as the "when a file is added to an FTP server" trigger. Azure Logic Apps currently supports over 100 ready-to-use connectors, ranging from on-premises SAP to Microsoft Cognitive Services. For systems and services that might not have published connectors, you can also extend logic apps.
- Create custom triggers or actions
- Set up long-running actions for workflow runs
- Respond to external events and actions with webhooks
- Call, trigger, or nest workflows with synchronous responses to HTTP requests
- Tutorial: Respond to Twilio SMS webhooks and send a text response
- Tutorial: Build an AI-powered social dashboard in minutes with Logic Apps and Power BI
Error handling, logging, and control flow capabilities
Logic apps include rich capabilities for advanced control flow, like conditions, switches, loops, and scopes. To ensure resilient solutions, you can also implement error and exception handling in your workflows. For notification and diagnostic logs for workflow run status, Azure Logic Apps also provides monitoring and alerts.
- Perform different actions with switch statements
- Process items in arrays and collections with loops and batches in logic apps
- Author error and exception handling in a workflow
- Turn on monitoring, logging, and alerts for existing logic apps
- Turn on monitoring and diagnostics logging when creating logic apps
- Use case: How a healthcare company uses logic app exception handling for HL7 FHIR workflows
Deploy and manage logic apps
You can fully develop and deploy logic apps with Visual Studio, Visual Studio Team Services, or any other source control and automated build tools. To support deployment for workflows and dependent connections in a resource template, logic apps use Azure resource deployment templates. Visual Studio tools automatically generate these templates, which you can check in to source control for versioning.
- Create an automated deployment template
- Build and deploy logic apps from Visual Studio
- Monitor the health of your logic apps
Content types, conversions, and transformations within a run
You can access, convert, and transform multiple content types by using the many functions
in the Azure Logic Apps workflow definition language.
For example, you can convert between a string, JSON, and XML with
the @json() and @xml() workflow expressions.
The Logic Apps engine preserves content types to support
content transfer in a lossless manner between services.
- Handle non-JSON content types,
like
application/xml,application/octet-stream, andmultipart/formdata - How workflow expressions work in logic apps
- Reference: Azure Logic Apps workflow definition language
Other integrations and capabilities
Logic apps also offer integration with many services, like Azure Functions, Azure API Management, Azure App Services, and custom HTTP endpoints, for example, REST and SOAP.
- Create a real-time social dashboard with Azure Serverless
- Call Azure Functions from logic apps
- Scenario: Trigger logic apps with Azure Functions
- Blog: Call SOAP endpoints from logic apps