NATS - JetStream icon

NATS - JetStream

NATS - JetStream

Actions2

Acknowledge a Message

AI-generated

Overview

This node integrates with NATS JetStream, a messaging system for streaming data. Specifically, the "Acknowledge a Message" operation allows the workflow to acknowledge a message that was received earlier by a NATS - JetStream Trigger node. This is useful in scenarios where you want to confirm successful processing of a message to prevent it from being redelivered.

Practical examples include:

  • Confirming receipt and processing of messages in event-driven architectures.
  • Managing message flow control in distributed systems using JetStream.
  • Ensuring reliable message consumption in workflows that process streaming data.

Properties

Name Meaning
Will acknowledge an message from the stream consumer earlier in the workflow by a NATS - JetStream Trigger node This is a notice property indicating that this operation will acknowledge a previously received message from the stream consumer. It does not require user input but informs about the action performed.

Output

The output JSON contains the acknowledged message data as it was received from the trigger node. The node returns the original message JSON wrapped in an array, confirming the acknowledgment.

No binary data output is involved in this operation.

Dependencies

  • Requires a valid connection to a NATS JetStream server.
  • Needs an API key credential configured in n8n for authenticating with the NATS server.
  • The node depends on the nats client library and internal helper functions to manage connections and perform acknowledgments.

Troubleshooting

  • Common issues:
    • Failure to connect to the NATS JetStream server due to incorrect credentials or network issues.
    • Attempting to acknowledge a message when no prior message was received or available in the workflow context.
  • Error messages:
    • Connection errors typically indicate misconfigured credentials or unreachable server endpoints.
    • Errors during acknowledgment may occur if the message has already been acknowledged or expired; ensure the message context is valid.
  • Resolutions:
    • Verify API key and server URL configurations.
    • Ensure the workflow includes a NATS - JetStream Trigger node before this acknowledgment node.
    • Use the "Continue On Fail" option to handle errors gracefully within the workflow.

Links and References

Discussion