Trigger
Consume messages periodically from a AMQP queue and create one execution per batch.
Note that you don't need an extra task to consume the message from the event trigger. The trigger will automatically consume messages and you can retrieve their content in your flow using the {{ trigger.uri }} variable. If you would like to consume each message from a AMQP queue in real-time and create one execution per message, you can use the io.kestra.plugin.amqp.RealtimeTrigger instead.
type: "io.kestra.plugin.amqp.Trigger"id: amqp_trigger
namespace: company.team
tasks:
- id: trigger
type: io.kestra.plugin.amqp.Trigger
url: amqp://guest:guest@localhost:5672/my_vhost
maxRecords: 2
queue: amqpTrigger.queue
A client-generated consumer tag to establish context.
The queue to pull messages from.
Serializer / Deserializer used for the message.
The broker host.
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.
The maximum duration to wait for new rows.
It's not an hard limit and is evaluated every second.
The broker password.
The broker port.
List of execution states after which a trigger should be stopped (a.k.a. disabled).
The broker username.
The broker virtual host.
Number of rows consumed.
File URI containing consumed messages.