# Flow trigger

type: "io.kestra.core.models.triggers.types.Flow"

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

# Example

This flow will be triggered after each successful execution of the flow io.kestra.tests.trigger-flow and forward the uri of my-task taskId outputs.

id: trigger-flow-listener
namespace: io.kestra.tests
revision: 1

inputs:
  - name: fromParent
    type: STRING

tasks:
  - id: onlyNoInput
    type: io.kestra.core.tasks.debugs.Return
    format: "v1: {{trigger.executionId}}"

triggers:
  - id: listenFlow
    type: io.kestra.core.models.triggers.types.Flow
    inputs:
      fromParent: '{{ outputs.myTask.uri }}'
    conditions:
      - type: io.kestra.core.models.conditions.types.ExecutionFlowCondition
        namespace: io.kestra.tests
        flowId: trigger-flow
      - type: io.kestra.core.models.conditions.types.ExecutionStatusCondition
        in:
          - SUCCESS

This flow will be triggered after the successful execution of both flows flow-a & flow-b during the current day. When the conditions are met, the counter is reset and can be re-triggered during the same day. See MultipleCondition for more details

id: trigger-multiplecondition-listener
namespace: io.kestra.tests

tasks:
  - id: onlyListener
    type: io.kestra.core.tasks.debugs.Return
    format: "let's go "

triggers:
  - id: multipleListenFlow
    type: io.kestra.core.models.triggers.types.Flow
    conditions:
      - id: multiple
        type: io.kestra.core.models.conditions.types.MultipleCondition
        window: P1D
        windowAdvance: P0D
        conditions:
          flow-a:
            type: io.kestra.core.models.conditions.types.ExecutionFlowCondition
            namespace: io.kestra.tests
            flowId: trigger-multiplecondition-flow-a
          flow-b:
            type: io.kestra.core.models.conditions.types.ExecutionFlowCondition
            namespace: io.kestra.tests
            flowId: trigger-multiplecondition-flow-b

# Inputs

# id

  • Type: String
  • Required: ✔

unique for a flow

# inputs

  • Type: Map<String, Object>
  • Required: ❌
  • Dynamic: ✔

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

WARNING

If you provide an invalid input, the flow will be created and already state as FAILED! Since no task is started, you cannot log any reason visible on the ui.
So you will need to go to the server logs to understand the error.

# conditions

  • Type: List<Condition>
  • Required: ❌

List of Conditions in order to limit the flow trigger.

WARNING

If you do not provide any conditions, the flow will be triggered for EVERY execution of EVERY flow on your instance.

# Variables

When the flow is triggered by another one, some context variables will be injected to allow some customization of the flow.

Parameter Description
{{ trigger.executionId }} the execution id that trigger the current flow
{{ trigger.namespace }} the namespace of the flow that trigger the current flow
{{ trigger.flowId }} the flow id that trigger the current flow
{{ trigger.flowRevision }} the flow revision that trigger the current flow

← Schedule →

 Tweet  Share  Share