Trigger a flow based on an HTTP response

yaml
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.

yaml
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

yaml
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

Dynamic YES

The fully-qualified URI that points to the HTTP destination

Dynamic YES

The full body as a string

Dynamic NO

List of conditions in order to limit the flow trigger.

Dynamic YES

Default application/json

The request content type

Dynamic NO

Default 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.

Dynamic YES

The form data to be send

SubType string

Dynamic YES

The headers to pass to the request

Dynamic NO

Default PT1M

Format 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.

Dynamic YES

Default GET

The HTTP method to use

Dynamic NO

The HTTP request options

Dynamic YES

The query string parameter to use

Adds parameter to URI query. The parameter name and value are expected to be unescaped and may contain non ASCII characters. The value can be a string or a list of strings. This method will not override parameters already existing on uri and will add them as array.

Dynamic YES

Default {{ 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 code
response.body: the response body as a string
response.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.

Dynamic NO

The SSL request options

This property is deprecated. Instead use the options.ssl property.

SubType string

Dynamic NO

Possible Values

CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTED

List of execution states after which a trigger should be stopped (a.k.a. disabled).

The body of the response

Kestra, by default, stores 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).

SubType array

The headers of the response

Format uri

The URL of the current request

Dynamic YES

Format duration

The time allowed to establish a connection to the server before failing.

Dynamic YES

Default PT5M

Format duration

The time allowed for a read connection to remain idle before closing it.

Dynamic NO

Format partial-time

SLA daily deadline

Use it only for DAILY_TIME_DEADLINE SLA.

Dynamic NO

Format partial-time

SLA daily end time

Use it only for DAILY_TIME_WINDOW SLA.

Dynamic NO

Format partial-time

SLA daily start time

Use it only for DAILY_TIME_WINDOW SLA.

Dynamic NO

Default DURATION_WINDOW

Possible Values

DAILY_TIME_DEADLINEDAILY_TIME_WINDOWDURATION_WINDOWSLIDING_WINDOW

The type of the SLA

The default SLA is a sliding window (DURATION_WINDOW) with a window of 24 hours.

Dynamic NO

Format 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

Dynamic NO

Format 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

Dynamic YES

The address of the proxy server.

Dynamic YES

The password for proxy authentication.

Dynamic NO

The port of the proxy server.

Dynamic YES

Default DIRECT

Possible Values

DIRECTHTTPSOCKS

The type of proxy to use.

Dynamic YES

The username for proxy authentication.

Dynamic NO

Dynamic YES

Default {{ trigger.date }}

The date to test.

Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.

Dynamic NO

Min items 1

The list of conditions to validate.

If any condition is true, it will allow the event's execution.

Dynamic NO

Dynamic YES

String against which to match the execution namespace depending on the provided comparison.

Dynamic NO

Dynamic YES

Possible Values

EQUALSPREFIXSUFFIX

Comparison to use when checking if namespace matches. If not provided, it will use EQUALS by default.

Dynamic NO

Default false

Whether to look at the flow namespace by prefix. Shortcut for comparison: PREFIX.

Only used when comparison is not set

Dynamic NO

Default false

If true, allow a failed response code (response code >= 400)

SubType integer

Dynamic YES

List of response code allowed for this request

Dynamic NO

The authentification to use.

Dynamic NO

The password for HTTP basic authentication. Deprecated, use auth property with a BasicAuthConfiguration instance instead.

Dynamic NO

The username for HTTP basic authentication. Deprecated, use auth property with a BasicAuthConfiguration instance instead.

Dynamic NO

Format duration

The time allowed to establish a connection to the server before failing.

Dynamic NO

Format duration

The time an idle connection can remain in the client's connection pool before being closed.

Dynamic NO

Default UTF-8

The default charset for the request.

Dynamic NO

Default true

Whether redirects should be followed automatically.

Dynamic NO

Possible Values

ALLTRACEDEBUGINFOWARNERROROFFNOT_SPECIFIED

The log level for the HTTP client.

SubType string

Dynamic NO

Possible Values

REQUEST_HEADERSREQUEST_BODYRESPONSE_HEADERSRESPONSE_BODY

The enabled log.

Dynamic NO

The maximum content length of the response.

Dynamic NO

The proxy configuration.

Dynamic NO

The address of the proxy server.

Dynamic NO

The password for proxy authentication.

Dynamic NO

The port of the proxy server.

Dynamic NO

Possible Values

DIRECTHTTPSOCKS

The type of proxy to use.

Dynamic NO

The username for proxy authentication.

Dynamic NO

Format duration

The time allowed for a read connection to remain idle before closing it.

Dynamic NO

Format duration

The maximum time allowed for reading data from the server before failing.

Dynamic NO

The SSL request options

Dynamic NO

The timeout configuration.

Dynamic NO

Min items 1

The list of conditions to exclude.

If any condition is true, it will prevent the event's execution.

Dynamic NO

Dynamic YES

Possible Values

FIRSTLASTSECONDTHIRDFOURTH

Are you looking for the first or the last day in the month?

Dynamic YES

Possible Values

MONDAYTUESDAYWEDNESDAYTHURSDAYFRIDAYSATURDAYSUNDAY

The day of week.

Dynamic NO

Dynamic YES

Default {{ trigger.date }}

The date to test.

Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.

Dynamic NO

Dynamic YES

Format 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).

Dynamic YES

Format 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).

Dynamic YES

Default {{ trigger.date }}

The date to test.

Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.

Dynamic NO

SubType string

Dynamic YES

Possible Values

CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTED

List of states that are authorized.

SubType string

Dynamic YES

Possible Values

CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTED

List of states that aren't authorized.

Dynamic NO

Dynamic YES

The token for bearer token authentication.

Dynamic YES

The flow id.

Dynamic YES

The namespace of the flow.

Dynamic NO

Dynamic YES

The password for HTTP basic authentication.

Dynamic YES

The username for HTTP basic authentication.

Dynamic NO

The namespace of the flow or the prefix if prefix is true.

Dynamic NO

Default false

If we must look at the flow namespace by prefix (checked using startsWith). The prefix is case sensitive.

Dynamic NO

The flow id.

Dynamic NO

The namespace of the flow.

Dynamic NO

Dynamic YES

Format time

The time to test must be after this one.

Must be a valid ISO 8601 time with offset.

Dynamic YES

Format time

The time to test must be before this one.

Must be a valid ISO 8601 time with offset.

Dynamic YES

Default {{ trigger.date }}

The time to test.

Can be any variable or any valid ISO 8601 time. By default, it will use the trigger date.

Dynamic NO

List of labels to match in the execution.

Dynamic NO

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.

Dynamic NO

SubType

Dynamic NO

The list of preconditions to wait for

The key must be unique for a trigger because it will be used to store the previous evaluation result.

Dynamic NO

Validation RegExp ^[a-zA-Z0-9][a-zA-Z0-9_-]*

Min length 1

A unique id for the condition

Dynamic NO

Default 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.

Dynamic NO

Default

{
  "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 default type. 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 duration window. 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 set windowAdvance: PT6H, the window will start at 6 AM each day. If you set windowAdvance: PT6H and you also override the window property to PT6H, 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 time window, 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 property deadline, 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 from startTime: "06: 00: 00" to endTime: "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.

Dynamic NO

Format duration

The duration of the window

Deprecated, use timeWindow.window instead.

Dynamic NO

Format duration

The window advance duration

Deprecated, use timeWindow.windowAdvance instead.

Dynamic YES

Dynamic NO

Dynamic YES

Possible Values

MONDAYTUESDAYWEDNESDAYTHURSDAYFRIDAYSATURDAYSUNDAY

The day of week.

Dynamic NO

Dynamic YES

Default {{ trigger.date }}

The date to test.

Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.

Dynamic NO

SubType string

Dynamic YES

Possible Values

CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTED

List of states that are authorized.

SubType string

Dynamic YES

Possible Values

CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTED

List of states that aren't authorized.

Dynamic NO

Dynamic YES

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.

Dynamic YES

Default {{ trigger.date}}

The date to test.

Can be any variable or any valid ISO 8601 datetime. By default, it will use the trigger date.

Dynamic YES

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.