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:
This table is used to determine which URL is used to fire the appropriate logic app:
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...