Call HTTP or HTTPS endpoints with Azure Logic Apps
With Azure Logic Apps and the Hypertext Transfer Protocol (HTTP) connector, you can automate workflows that communicate with any HTTP or HTTPS endpoint by building logic apps. For example, you can monitor the service endpoint for your website. When an event happens at that endpoint, such as your website going down, the event triggers your logic app's workflow and runs the specified actions.
You can use the HTTP trigger as the first step in your worklfow for checking or polling an endpoint on a regular schedule. On each check, the trigger sends a call or request to the endpoint. The endpoint's response determines whether your logic app's workflow runs. The trigger passes along any content from the response to the actions in your logic app.
You can use the HTTP action as any other step in your workflow for calling the endpoint when you want. The endpoint's response determines how your workflow's remaining actions run.
Based the target endpoint's capability, this connector supports Transport Layer Security (TLS) versions 1.0, 1.1, and 1.2. Logic Apps negotiates with the endpoint over using the highest supported version possible. So, for example, if the endpoint supports 1.2, the connector uses 1.2 first. Otherwise, the connector uses the next highest supported version.
If you're new to logic apps, review What is Azure Logic Apps?
An Azure subscription. If you don't have an Azure subscription, sign up for a free Azure account.
The URL for the target endpoint you want to call
Basic knowledge about how to create logic apps
The logic app from where you want to call the target endpoint To start with the HTTP trigger, create a blank logic app. To use the HTTP action, start your logic app with a trigger.
Add HTTP trigger
Sign in to the Azure portal, and open your blank logic app in Logic App Designer, if not open already.
In the search box, enter "http" as your filter. Under the triggers list, select the HTTP trigger.
Provide the HTTP trigger's parameters and values you want to include in the call to the target endpoint. Set up recurrence for how often you want the trigger to check the target endpoint.
For more information about the HTTP trigger, parameters, and values, see Trigger and action types reference.
Continue building your logic app's workflow with actions that run when the trigger fires.
Add HTTP action
Before your logic app can access any service, you must create a connection between your logic app and that service. If you didn't previously create this connection, you're prompted for connection information when you add a trigger or action for that service to your logic app. The Logic Apps Designer provides an easy way for you to create this connection directly from your logic app.
Sign in to the Azure portal, and open your logic app in Logic App Designer, if not open already.
Under the last step where you want to add the HTTP action, choose New step.
In this example, the logic app starts with the HTTP trigger as the first step.
In the search box, enter "http" as your filter. Under the actions list, select the HTTP action.
To add an action between steps, move your pointer over the arrow between steps. Choose the plus sign (+) that appears, and then select Add an action.
Provide the HTTP action's parameters and values you want to include in the call to the target endpoint.
When you're done, make sure you save your logic app. On the designer toolbar, choose Save.
To set authentication, choose Show advanced options inside the action or trigger. For more information about available authentication types for HTTP triggers and actions, see Trigger and action types reference.
- For questions, visit the Azure Logic Apps forum.
- To submit or vote on feature ideas, visit the Logic Apps user feedback site.
- Learn about other Logic Apps connectors
Send feedback about: