# Inputs

Kestra's flow can be parameterized using inputs. Inputs will be available in variable context and can be used during the whole flow, in order to customize it depending on inputs.

A good example is when an identifier is needed (ex: storeId, paymentId) in order to change the save path for the uploaded files.

# Declaring inputs

You can declare as many inputs as necessary for any flow. Input can be required or not.
If the input is required, the flow cannot start if the input is not provided during the creation of the execution.
Also, every input will be parsed during the creation of the execution and any invalid inputs will cause a refusal to create the execution.


If the execution is not created due to invalid or missing inputs, no execution will be found on the executions list.


id: my-flow
namespace: io.kestra.docs

  - name: string
    type: STRING
  - name: optional
    type: STRING
    required: false
  - name: int
    type: INT
  - name: bool
    type: BOOLEAN
  - name: float
    type: FLOAT
  - name: instant
    type: DATETIME
  - name: date
    type: DATE
  - name: time
    type: TIME
  - name: duration
    type: DURATION
  - name: file
    type: FILE
  - name: optionalFile
    type: FILE
    required: false
  - name: instantDefaults
    type: DATETIME
    defaults: "2013-08-09T14:19:00Z"
  - name: json
    type: JSON
  - name: uri
    type: URI
    required: false
  - name: nested.string
    type: STRING
    required: false
  - name: nested.more.int
    type: INT
    required: false
  - name: nested.bool
    type: BOOLEAN
    required: false

# Input types

The available input fields available are as follows:


No control is done on this input type (no parsing), can be any string.


Must be a valid integer (without any decimals).


Must be a valid float (with any decimals).


Must be a valid true or false as string.


Must be a valid full ISO 8601 (opens new window) datetime with the timezone expressed in UTC from a text string such as


Must be a valid full ISO 8601 (opens new window) date without the timezone from a text string such as 2007-12-03.


Must be a valid full ISO 8601 (opens new window) time without the timezone from a text string such as 10:15:30.


Must be a valid full ISO 8601 (opens new window) duration from a text string such as PT5M6S.


Must be a file sent with multipart/form-data. All the files are automatically uploaded to Storage and are available for further tasks. The return will be a fully qualified url with the form kestra:///.../.../. Kestra is able to handle this url and this input can be passed as is to task.


Must be a valid json as string and will be converted to typed form.


Must be a valid uri and will be kept as a string.

# Input properties

These are the properties available for all input types :

# name

The input name to be used with vars {{ inputs.my-name }}

# required

If the input is required. If required, no defaults value and no input provide, the execution will not be created.

# defaults

The default value if no input is provided. Must be a string.

# description

A markdown description in order to document the inputs.

# Nested Inputs

If you use a . inside the name of the inputs, the input will be nested. For example, when you declated the input with:

  - name: nested.string
    type: STRING
    required: false

You can reach this input with: {{ inputs.nested.string }}. This is a convenient way to handle strong typing on input (with validation) without using raw JSON that will not be validated.

# Using input value in flow

Every input is available with dynamic variables such as: {{ inputs.NAME }}.

For example, if you declare your input :

  - name: my-file
    type: FILE
  - name: my-value
    type: STRING
    required: true

You can use the value of the inputs with {{ inputs.my-value }}.

# Send inputs programmatically

The flow my-flow above can be triggered programmatically. Here is an example with curl:

curl -v "http://kestra:8080/api/v1/executions/trigger/io.kestra.docs/my-flow" \
    -H "Transfer-Encoding:chunked" \
    -H "Content-Type:multipart/form-data" \
    -F string="a string"  \
    -F optional="an optionnal string"  \
    -F int=1  \
    -F float=1.255  \
    -F instant=2020-01-14T23:00:00.000Z \
    -F "files=@/tmp/128M.txt;filename=my-file"

All files must be sent in the form of data files with a header filename=my-file, which will be the name of the input.

Here is an example with python:

import io
import requests
from requests_toolbelt.multipart.encoder import MultipartEncoder

with open("/tmp/128M.txt", 'rb') as fh:
  url = f"http://kestra:8080/api/v1/executions/trigger/io.kestra.docs/my-flow"
  mp_encoder = MultipartEncoder(fields={
    "string": "a string",
    "optional": "an optionnal string",
    "int": 1,
    "float": 1.255,
    "instant": "2020-01-14T23:00:00.000Z",
    "files": ("file", fh, "text/plain")
  result = requests.post(
      headers={"Content-Type": mp_encoder.content_type},

# Send inputs via WebUI

With such a flow, the web ui lets you enter some inputs by generating a form accordingly on the flow > trigger view. The input form for the task above looks like below:

Flow inputs

Once the inputs are provided, you can trigger an execution flow that will run with contextual inputs as variables.