HTTP triggers are another type of scheduled trigger that can either poll or post to specific HTTP endpoints on a configured schedule. Apart from basic configuration settings, HTTP triggers support multiple authentication protocols such as basic, certificate, managed service identity, and OAuth authentication.
In the following code for the HTTP scheduled trigger, we can set the recurrence property with things such as frequency, interval, startTime, and endTime, along with its schedule. This HTTP trigger performs a GET operation against the external endpoint with the authentication type as Basic:
As an HTTP trigger is a scheduled trigger, it has built-in support for all the properties available in the recurrence trigger. You can configure an HTTP scheduled task using properties such as schedule and runtime configuration. HTTP triggers also inherit some additional properties from the request trigger, such as splitOn, the retry policy, and support for headers.
HTTP trigger properties are listed in the following table:
|
Name |
Optional/mandatory |
Description |
|
Recurrence |
Mandatory |
An object to define the recurrence property of the HTTP trigger |
|
Headers |
Optional |
An object to define the HTTP header properties |
|
Body |
Optional |
The body of the HTTP trigger |
|
Authentication |
Optional |
Types of authentication include basic, OAuth, none, and managed service identity |
|
retryPolicy |
Optional |
An object that customizes the retry behavior when failures occur with the HTTP status codes 408, 429, and 5XX |
|
Queries |
Optional |
Query parameters to include with the HTTP request |
|
operationOptions |
Optional |
The default behavior of the HTTP trigger |
|
Type |
Mandatory |
HTTP trigger |
|
splitOn |
Optional |
Splits incoming JSON arrays into objects |
|
Method |
Mandatory |
The HTTP method to use for polling the specified endpoint: GET, PUT, POST, PATCH, DELETE |
|
runtimeconfiguration |
Optional |
An object to change the runtime property of the HTTP trigger |
|
URI |
Mandatory |
The endpoint URI |
To work with HTTP triggers, the external endpoint should return a valid status code and understand the semantics of the HTTP protocol, such as the status code, retry-after header, and location header.
You can learn more about properties of HTTP triggers, such as HTTP status code and retry policies, in the Microsoft documentation: https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-actions-triggers#http-trigger.