🚀 New! Kestra raises $3 million to grow Learn more

​Develop a ​Trigger

Here is how you can develop a Trigger.

The Trigger example below will create an execution randomly:

public class Trigger extends AbstractTrigger implements PollingTriggerInterface, TriggerOutput<Trigger.Random> {
    private final Duration interval = Duration.ofSeconds(60);

    protected Double min = 0.5;

    public Optional<Execution> evaluate(ConditionContext conditionContext, TriggerContext context) {
        RunContext runContext = conditionContext.getRunContext();
        Logger logger = conditionContext.getRunContext().logger();
        double random = Math.random();

        if (random < this.min) {
            return Optional.empty();

        Execution execution = Execution.builder()
            .state(new State())

        return Optional.of(execution);

    public class Random implements io.kestra.core.models.tasks.Output {
        private Double random;

You need to extend PollingTriggerInterface and implement the Optional<Execution> evaluate(ConditionContext conditionContext, TriggerContext context) method.

You can have any properties you want, like for any task (validation, documentation, ...), and everything is working the same way.

The evaluate method will receive these arguments:

  • ConditionContext conditionContext: a ConditionContext which includes various properties such as the RunContext in order to render your properties.
  • TriggerContext context: to have the context of this call (flow, execution, trigger, date, ...).

In this method, you add any logic you want: connect to a database, connect to remote file systems, ... You don't have to take care of resources, Kestra will run this method in its own thread.

This method must return an Optional<Execution> with:

  • Optional.empty(): if the condition is not validated.
  • Optional.of(execution): with the execution created if the condition is validated.

You have to provide a Output for any output needed (result of query, result of file system listing, ...) that will be available for the flow tasks within the {{ trigger.* }} variables.


Remember to document your triggers. For this, we provide a set of annotations explained in the Document each plugin section.