RealtimeTrigger

Consume a message in real-time from a NATS subject on a JetStream-enabled NATS server and create one execution per message.

If you would like to consume multiple messages processed within a given time frame and process them in batch, you can use the io.kestra.plugin.nats.Trigger instead.

yaml
type: "io.kestra.plugin.nats.RealtimeTrigger"

Subscribe to a NATS subject, getting every message from the beginning of the subject on first trigger execution.

yaml
id: nats
namespace: company.team

tasks:
  - id: log
    type: io.kestra.plugin.core.log.Log
    message: "{{ trigger.data }}"

triggers:
  - id: watch
    type: io.kestra.plugin.nats.RealtimeTrigger
    url: nats://localhost:4222
    username: nats_user
    password: nats_password
    subject: kestra.trigger
    durableId: natsTrigger
    deliverPolicy: All

Dynamic YES

Default All

Possible Values

AllLastNewByStartSequenceByStartTimeLastPerSubject

The point in the stream to receive messages from.

Possible settings are:

All: The default policy. The consumer will start receiving from the earliest available message.
Last: When first consuming messages, the consumer will start receiving messages with the last message added to the stream, or the last message in the stream that matches the consumer's filter subject if defined.
New: When first consuming messages, the consumer will only start receiving messages that were created after the consumer was created.
ByStartSequence: When first consuming messages, start at the first message having the sequence number or the next one available.
ByStartTime: When first consuming messages, start with messages on or after this time. The consumer is required to specify since which defines this start time.
LastPerSubject: When first consuming messages, start with the latest one for each filtered subject currently in the stream.

Dynamic YES

Min length 1

URL to connect to NATS server

The format is (nats://)server_url: port. You can also provide a connection token like so: nats://token@server_url: port

Dynamic YES

Default 10

Minimum >= 1

Messages are fetched by batch of given size.

SubType

Dynamic NO

List of conditions in order to limit the flow trigger.

Dynamic YES

Credentials files authentification

Dynamic YES

ID used to attach the subscription to a durable one, allowing the subscription to start back from a previous position

Dynamic YES

Plaintext authentication password

Dynamic YES

Minimum message timestamp to start consumption from.

By default, we consume all messages from the subjects starting from beginning of logs or depending on the current durable id position. You can also provide an arbitrary start time to get all messages since this date for a new durable id. Note that if you don't provide a durable id, you will retrieve all messages starting from this date even after subsequent usage of this task.Must be a valid iso 8601 date.

SubType string

Dynamic NO

Possible Values

CREATEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPED

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

Dynamic YES

Min length 1

Subject to subscribe to

Dynamic YES

Token authentification

Dynamic YES

Plaintext authentication username

SubType array

Format date-time

​Realtime​Trigger

RealtimeTrigger