Trigger a flow based on an HTTP response
type: "io.kestra.plugin.core.http.Trigger"
Send a Slack alert if the price is below a certain threshold. The flow will be triggered every 30 seconds until the condition is met. Then, the stopAfter
property will disable the trigger to avoid unnecessary API calls and alerts.
id: http_price_alert
namespace: company.team
tasks:
- id: send_slack_alert
type: io.kestra.plugin.notifications.slack.SlackIncomingWebhook
url: "{{ secret('SLACK_WEBHOOK') }}"
payload: |
{
"channel": "#price-alerts",
"text": "The price is now: {{ json(trigger.body).price }}"
}
triggers:
- id: http
type: io.kestra.plugin.core.http.Trigger
uri: https://fakestoreapi.com/products/1
responseCondition: "{{ json(response.body).price <= 110 }}"
interval: PT30S
stopAfter:
- SUCCESS
Trigger a flow if an HTTP endpoint returns a status code equals to 200
id: http_trigger
namespace: company.team
tasks:
- id: log_response
type: io.kestra.plugin.core.log.Log
message: '{{ trigger.body }}'
triggers:
- id: http
type: io.kestra.plugin.core.http.Trigger
uri: https://api.chucknorris.io/jokes/random
responseCondition: "{{ response.statusCode == 200 }}"
stopAfter:
- SUCCESS
The fully-qualified URI that points to the HTTP destination
The full body as a string
List of conditions in order to limit the flow trigger.
application/json
The request content type
false
If true, the HTTP response body will be automatically encrypted and decrypted in the outputs if encryption is configured
When true, the encryptedBody
output will be filled, otherwise the body
output will be filled
The form data to be send
The headers to pass to the request
PT1M
duration
Interval between polling.
The interval between 2 different polls of schedule, this can avoid to overload the remote system with too many calls. For most of the triggers that depend on external systems, a minimal interval must be at least PT30S. See ISO_8601 Durations for more information of available interval values.
GET
The HTTP method to use
The HTTP request options
{{ response.statusCode < 400 }}
The condition on the HTTP response to trigger a flow which can be any expression that evaluates to a boolean value.
The condition will be evaluated after calling the HTTP endpoint, it can use the response itself to determine whether to start a flow or not. The following variables are available when evaluating the condition:
response.statusCode
: the response HTTP status coderesponse.body
: the response body as a stringresponse.headers
: the response headers
Boolean coercion allows 0, -0, null and '' to evaluate to false, all other values will evaluate to true.
The condition will be evaluated before any 'generic trigger conditions' that can be configured via the conditions
property.
The SSL request options.
This property is deprecated. Instead use the options.ssl
property.
CREATED
RUNNING
PAUSED
RESTARTED
KILLING
SUCCESS
WARNING
FAILED
KILLED
CANCELLED
QUEUED
RETRYING
RETRIED
SKIPPED
List of execution states after which a trigger should be stopped (a.k.a. disabled).
The body of the response.
Kestra will by default store the task output using this property. However, if the encryptBody
property is set to true
, kestra will instead encrypt the output and store it using the encryptedBody
output property.
The status code of the response.
The encrypted body of the response.
If the encryptBody
property is set to true
, kestra will automatically encrypt the output before storing it, and decrypt it when the output is retrieved in a downstream task.
The form data to be sent in the request body
When sending a file, you can pass a list of maps (i.e. a list of key-value pairs) with a key 'name' and value of the filename, as well as 'content' key with the file's content as value (e.g. passed from flow inputs or outputs from another task).
The headers of the response.
uri
The URL of the current request.
duration
The time allowed to establish a connection to the server before failing.
PT5M
duration
The time allowed for a read connection to remain idle before closing it.
partial-time
SLA daily deadline
Use it only for DAILY_TIME_DEADLINE
SLA.
partial-time
SLA daily end time
Use it only for DAILY_TIME_WINDOW
SLA.
partial-time
SLA daily start time
Use it only for DAILY_TIME_WINDOW
SLA.
DURATION_WINDOW
DAILY_TIME_DEADLINE
DAILY_TIME_WINDOW
DURATION_WINDOW
SLIDING_WINDOW
The type of the SLA
The default SLA is a sliding window (DURATION_WINDOW
) with a window of 24 hours.
duration
The duration of the window
Use it only for DURATION_WINDOW
or SLIDING_WINDOW
SLA.
See ISO_8601 Durations for more information of available duration value.
The start of the window is always based on midnight except if you set windowAdvance parameter. Eg if you have a 10 minutes (PT10M) window,
the first window will be 00: 00 to 00: 10 and a new window will be started each 10 minutes
duration
The window advance duration
Use it only for DURATION_WINDOW
SLA.
Allow to specify the start time of the window
Eg: you want a window of 6 hours (window=PT6H), by default the check will be done between: 00: 00 and 06: 00, 06: 00 and 12: 00, 12: 00 and 18: 00, and 18: 00 and 00: 00.
If you want to check the window between 03: 00 and 09: 00, 09: 00 and 15: 00, 15: 00 and 21: 00, and 21: 00 and 3: 00, you will have to shift the window of 3 hours by settings windowAdvance: PT3H
The address of the proxy server.
The password for proxy authentication.
The port of the proxy server.
DIRECT
DIRECT
HTTP
SOCKS
The type of proxy to use.
The username for proxy authentication.
{{ trigger.date }}
The date to test.
Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.
1
The list of conditions to validate.
If any condition is true, it will allow the event's execution.
String against which to match the execution namespace depending on the provided comparison.
EQUALS
PREFIX
SUFFIX
Comparison to use when checking if namespace matches. If not provided, it will use EQUALS
by default.
false
Whether to look at the flow namespace by prefix. Shortcut for comparison: PREFIX
.
Only used when comparison
is not set
false
If true, allow a failed response code (response code >= 400)
List of response code allowed for this request
The authentification to use.
The password for HTTP basic authentication.
The username for HTTP basic authentication.
duration
The time allowed to establish a connection to the server before failing.
duration
The time an idle connection can remain in the client's connection pool before being closed.
UTF-8
The default charset for the request.
true
Whether redirects should be followed automatically.
ALL
TRACE
DEBUG
INFO
WARN
ERROR
OFF
NOT_SPECIFIED
The log level for the HTTP client.
REQUEST_HEADERS
REQUEST_BODY
RESPONSE_HEADERS
RESPONSE_BODY
The enabled log.
The maximum content length of the response.
The proxy configuration.
The address of the proxy server.
The password for proxy authentication.
The port of the proxy server.
DIRECT
HTTP
SOCKS
The type of proxy to use.
The username for proxy authentication.
duration
The time allowed for a read connection to remain idle before closing it.
duration
The maximum time allowed for reading data from the server before failing.
The SSL request options
The timeout configuration.
1
The list of conditions to exclude.
If any conditions is true, it will prevent the event's execution.
FIRST
LAST
SECOND
THIRD
FOURTH
Are you looking for the first or the last day in the month?
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
SATURDAY
SUNDAY
The day of week.
{{ trigger.date }}
The date to test.
Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.
date-time
The date to test must be after this one.
Must be a valid ISO 8601 datetime with the zone identifier (use 'Z' for the default zone identifier).
date-time
The date to test must be before this one.
Must be a valid ISO 8601 datetime with the zone identifier (use 'Z' for the default zone identifier).
{{ trigger.date }}
The date to test.
Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.
CREATED
RUNNING
PAUSED
RESTARTED
KILLING
SUCCESS
WARNING
FAILED
KILLED
CANCELLED
QUEUED
RETRYING
RETRIED
SKIPPED
List of states that are authorized.
CREATED
RUNNING
PAUSED
RESTARTED
KILLING
SUCCESS
WARNING
FAILED
KILLED
CANCELLED
QUEUED
RETRYING
RETRIED
SKIPPED
List of states that aren't authorized.
The token for bearer token authentication.
The flow id.
The namespace of the flow.
The password for HTTP basic authentication.
The username for HTTP basic authentication.
The namespace of the flow or the prefix if prefix
is true.
false
If we must look at the flow namespace by prefix (checked using startWith). The prefix is case sensitive.
The flow id.
The namespace of the flow.
time
The time to test must be after this one.
Must be a valid ISO 8601 time with offset.
time
The time to test must be before this one.
Must be a valid ISO 8601 time with offset.
{{ trigger.date }}
The time to test.
Can be any variable or any valid ISO 8601 time. By default, it will use the trigger date.
List of labels to match in the execution.
Whether to disable checking of the remote SSL certificate.
Only applies if no trust store is configured. Note: This makes the SSL connection insecure and should only be used for testing. If you are using a self-signed certificate, set up a trust store instead.
^[a-zA-Z0-9][a-zA-Z0-9_-]*
1
A unique id for the condition
true
Whether to reset the evaluation results of SLA conditions after a first successful evaluation within the given time period.
By default, after a successful evaluation of the set of SLA conditions, the evaluation result is reset, so, the same set of conditions needs to be successfully evaluated again in the same time period to trigger a new execution.
This means that to create multiple executions, the same set of conditions needs to be evaluated to true
multiple times.
You can disable this by setting this property to false
so that, within the same period, each time one of the conditions is satisfied again after a successful evaluation, it will trigger a new execution.
{
"type": "DURATION_WINDOW"
}
Define the time period (or window) for evaluating preconditions.
You can set the type
of sla
to one of the following values:
DURATION_WINDOW
: this is the defaulttype
. It uses a start time (windowAdvance
) and end time (window
) that are moving forward to the next interval whenever the evaluation time reaches the end time, based on the defined durationwindow
. For example, with a 1-day window (the default option:window: PT1D
), the SLA conditions are always evaluated during 24h starting at midnight (i.e. at time 00: 00: 00) each day. If you setwindowAdvance: PT6H
, the window will start at 6 AM each day. If you setwindowAdvance: PT6H
and you also override thewindow
property toPT6H
, the window will start at 6 AM and last for 6 hours — as a result, Kestra will check the SLA conditions during the following time periods: 06: 00 to 12: 00, 12: 00 to 18: 00, 18: 00 to 00: 00, and 00: 00 to 06: 00, and so on.SLIDING_WINDOW
: this option also evaluates SLA conditions over a fixed timewindow
, but it always goes backward from the current time. For example, a sliding window of 1 hour (window: PT1H
) will evaluate executions for the past hour (so between now and one hour before now). It uses a default window of 1 day.DAILY_TIME_DEADLINE
: this option declares that some SLA conditions should be met "before a specific time in a day". With the string propertydeadline
, you can configure a daily cutoff for checking conditions. For example,deadline: "09: 00: 00"
means that the defined SLA conditions should be met from midnight until 9 AM each day; otherwise, the flow will not be triggered.DAILY_TIME_WINDOW
: this option declares that some SLA conditions should be met "within a given time range in a day". For example, a window fromstartTime: "06: 00: 00"
toendTime: "09: 00: 00"
evaluates executions within that interval each day. This option is particularly useful for declarative definition of freshness conditions when building data pipelines. For example, if you only need one successful execution within a given time range to guarantee that some data has been successfully refreshed in order for you to proceed with the next steps of your pipeline, this option can be more useful than a strict DAG-based approach. Usually, each failure in your flow would block the entire pipeline, whereas with this option, you can proceed with the next steps of the pipeline as soon as the data is successfully refreshed at least once within the given time range.
duration
The duration of the window
Deprecated, use timeWindow.window
instead.
duration
The window advance duration
Deprecated, use timeWindow.windowAdvance
instead.
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
SATURDAY
SUNDAY
The day of week.
{{ trigger.date }}
The date to test.
Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.
CREATED
RUNNING
PAUSED
RESTARTED
KILLING
SUCCESS
WARNING
FAILED
KILLED
CANCELLED
QUEUED
RETRYING
RETRIED
SKIPPED
List of states that are authorized.
CREATED
RUNNING
PAUSED
RESTARTED
KILLING
SUCCESS
WARNING
FAILED
KILLED
CANCELLED
QUEUED
RETRYING
RETRIED
SKIPPED
List of states that aren't authorized.
ISO 3166-1 alpha-2 country code. If not set, it uses the country code from the default locale.
It uses the Jollyday library for public holiday calendar that supports more than 70 countries.
{{ trigger.date }}
The date to test.
Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.
ISO 3166-2 country subdivision (e.g., provinces and states) code.
It uses the Jollyday library for public holiday calendar that supports more than 70 countries.