Flow

type: "io.kestra.plugin.core.trigger.Flow"

Kestra is able to trigger flow after another one. This allows chaining flows without need to update the base flows. With that, you can break the responsibility between different flows, and thus to different teams.

Examples

This flow will be triggered after each successful execution of flow company.team.trigger_flow and forward the uri of my_task taskId outputs.

id: trigger_flow_listener
namespace: company.team

inputs:
  - id: from_parent
    type: STRING

tasks:
  - id: only_no_input
    type: io.kestra.plugin.core.debug.Return
    format: "v1: {{ trigger.executionId }}"

triggers:
  - id: listen_flow
    type: io.kestra.plugin.core.trigger.Flow
    inputs:
      from-parent: '{{ outputs.my_task.uri }}'
    conditions:
      - type: io.kestra.plugin.core.condition.ExecutionFlowCondition
        namespace: company.team
        flowId: trigger_flow
      - type: io.kestra.plugin.core.condition.ExecutionStatusCondition
        in:
          - SUCCESS

Properties

conditions

• Type: array
• SubType: Condition
• Dynamic: ❌
• Required: ❌

List of conditions in order to limit the flow trigger.

inputs

• Type: object
• Dynamic: ❌
• Required: ❌

Fill input of this flow based on output of current flow, allowing to pass data or file to the triggered flow.

If you provide invalid input, the flow will not be created! Since there is no task started, you can't log any reason that's visible on the Execution UI. So you will need to go to the Logs tabs on the UI to understand the error.

stopAfter

• Type: array
• SubType: string
• Dynamic: ❌
• Required: ❌

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

Outputs

executionId

• Type: string
• Required: ✔️

The execution ID that triggered the current flow.

flowId

• Type: string
• Required: ✔️

The flow ID whose execution triggered the current flow.

flowRevision

• Type: integer
• Required: ✔️

The flow revision that triggered the current flow.

namespace

• Type: string
• Required: ✔️

The namespace of the flow that triggered the current flow.

state

• Type: string
• Required: ✔️
• Possible Values:
  • CREATED
  • RUNNING
  • PAUSED
  • RESTARTED
  • KILLING
  • SUCCESS
  • WARNING
  • FAILED
  • KILLED
  • CANCELLED
  • QUEUED
  • RETRYING
  • RETRIED

The execution state.

Definitions