Book Image

Enterprise Integration with Azure Logic Apps

By : Matthew Bennett
Book Image

Enterprise Integration with Azure Logic Apps

By: Matthew Bennett

Overview of this book

Logic Apps are a visual flowchart-like representation of common programming actions, and are a flexible way to create logic without writing a single line of code. Enterprise Integration with Azure Logic Apps is a comprehensive introduction for anyone new to Logic Apps which will boost your learning skills and allow you to create rich, complex, structured, and reusable logic with instant results. You'll begin by discovering how to navigate the Azure portal and understand how your objects can be zoned to a specific environment by using resource groups. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will teach you the benefits and foundations of Logic App logic design. As you advance, you'll find out how to manage your Azure environment in relation to Logic Apps and how to create elegant and reliable Logic Apps. With useful and practical explanations of how to get the most out of Logic App actions and triggers, you'll be able to ensure that your Logic Apps work efficiently and provide seamless integration for real-world scenarios without having to write code. By the end of this Logic Apps book, you'll be able to create complex and powerful Logic Apps within minutes, integrating large amounts of data on demand, enhancing your systems, and linking applications to improve user experience.
Table of Contents (17 chapters)
1
Section 1: Logic App Fundamentals
7
Section 2: Logic App Design
13
Section 3: Logic App Maintenance and Management

Using an HTTP call to trigger a further logic app

As I mentioned previously, the initial method of using a child logic app action is, in my opinion, an inefficient solution. The replacement is to amend the SQL table so that it holds the trigger URLs for every logic app against their audit action. This way, I can send an HTTP POST call to fire the appropriate logic app, like so:

Figure 9.3 – URLs used to fire a logic app

This table is used to determine which URL is used to fire the appropriate logic app:

Figure 9.4 – Obtaining the action URL and dynamically using this to forward the HTTP POST method

By doing this, we have control over which logic app receives the message. Changing the name of a logic app will have no impact as the trigger URL that's used is not the name. However, recreating or cloning the child action logic app will produce a different URL as trigger URLs are randomized when the logic app is first...