I want multiple Http invoker(Http Trigger) in logic app. Logic app is not allowing another invoker(Http Trigger) in app.
Logic app with single invoker
I want multiple HTTP request invoke(In EX. - When Http request is received(Trigger)) in single logic app.
Please let me know any workaround.
While you can't have multiple Triggers in a single Logic App, you can separate the Triggers from the working logic.
Basically, create 1 Logic App with each Trigger format, then have all your Trigger Logic Apps call the same working Logic App.
Related
I am Practicing on a Project and using Rails as a api backend and React as Front end framework. I have implemented Authentication in React but now how I am got stuck at the question of how to implement authorization.
We know in Rails we use cancancan or other gem for authorization which is session based but I cant use cancancan now because My whole front-end is in rails. Are there any ways of doing this work?
If all the permissions are at the backend part, some of requests must return 401 and your frontend part must respond accordingly (render a popup e.g, show a message).
If you are trying to hide some unavailable parts (menu items, buttons, pages) beforehand, your frontend part must get a list of user roles / permissions from the back beforehand and render page using this infromation. You can provide this along with authentication request or as a separate request.
I, personally, prefer pundit over cancancan
I am trying to send an email alert when certain conditions are met by creating an alert rule in Azure monitor. For this, I also created an action group which tells what action to take when trigger conditions are met. In logic app I am using dynamic content which will come through POST http request, but in action group on azure portal I don't see any option to populate those parameters for POST request. Can anybody help me how to make a post request with request parameters to logic app in Azure portal?
There is no need to send parameters from Action group to logic app. When an action group is tested or the condition satisfied, automatically details will come in Http post request. Using expressions, you can retrieve details from Http post request to use in next action.
I have reproduced issue from my side. Below are steps I followed,
Created Action group in Azure monitor and added action type as Logic App.
Created logic app as shown below,
In Send Email action, I have used dynamic content from Http request trigger as shown below,
When I test action group, It triggered logic app and run details are shown below,
Output of Http trigger:
Send email Action:
5. As You can see in above picture, I am not getting values in Send email action.
So tried with writing expression instead of using dynamic content to get data from http trigger as shown below,
triggerbody()?['data']?['essentials']?['monitorCondition']
triggerbody()?['data']?['essentials']?['fireDateTime']
7. Tested logic app again and getting values as shown below,
Refer to this MS Doc for more information
I have a logic app that calls API endpoint through APIM. when I call endpoint in the logic app using the webhook connector, webhook keeps running and doe snot resume logic app.
While if I tried the same API endpoint through postman, it respond back within 3-5 seconds.
Below is the screenshot.
Not sure if i am missing anything.
This is outside the intended use of the webhook http task.
https://learn.microsoft.com/en-us/azure/connectors/connectors-native-webhook
You'll want to use the regular http post task, but you can extend the timeout in the settings to accommodate your long-running http call.
(click the triple dots in the top-right, then utilize the "Action Timeout" setting).
You could also try disabling asyncronous behavior:
https://learn.microsoft.com/en-us/azure/connectors/connectors-native-http#avoid-http-timeouts-for-long-running-tasks
If the logic app still times out, you will probably need to design a different solution.
I have a logic app with http trigger. I am trying to create a proxy for the logic app using APi management. The issue I am facing is that APi management when calling the Logic App, adds operation name which makes the logic app url invalid.
Example: logic app url: azure/invoke
API manager operation name: pass
Looking at trace logs, URL to call Logic app is:
azure/invoke/pass
I am trying to manually add url to backend service with Blank API design instead of using LogicApp.
API management preserves operation URL template while forwarding request to backend API. You can use rewrite-uri policy to control that behavior. In your scenario try adding <rewrite-uri template="/"/>
Anyone struggling why this is happening. The url in the front end is being passed in to the back end. You can either make it empty, add a policy to trim that off
I have created an Azure function (generic webhook) and I am calling the webhook from a Logic App. This all works successfully however I want to add security so I have enabled authentication on the function app (which contains the webhook function) but now my logic app fails on the step that calls the webhook due to an authorization error. Presumably I need to add some authorization information (client id etc?) into the logic app but I am unsure how to do this?
This is the workflow of the logic app:
And this is where I have enabled authenticationin the function app which contains the webhook:
Any ideas how to get this working?