Using a logic app action to call a child logic app
As your logic develops, you might notice that certain sections need to be called multiple times, or that they might need to be called by several logic apps that are similar. The term orchestrator refers to a logic app that will take a trigger action and, depending on what logic is required, route the data message to the appropriate child logic app for the message to be dealt with correctly and for the correct fields to be populated.
Let's look at a real-life example. I am taking data from an old, closed system that does not contain any Web APIs (web-based RESTful web programming interfaces) that can be used to send data or a direct link that will allow me to obtain data in Azure. I do some Read APIs that allow me to obtain data, but not the other way around. By writing a C# app that will query the closed system's audit logs, I might not be able to get to the actual data, but I can understand which action has just taken...