Actions11
Overview
This node manages NATS JetStream consumers, streams, and messages. Specifically for the Consumer - Get Info operation, it retrieves detailed information about a specific consumer within a given JetStream stream. This is useful when you want to inspect the configuration or status of a consumer, such as its delivery policy, acknowledgment settings, or current state.
Practical examples include:
- Monitoring consumer configurations in a message streaming system.
- Debugging issues by checking consumer details.
- Automating audits of JetStream consumers in your infrastructure.
Properties
| Name | Meaning |
|---|---|
| Stream Name | The name of the JetStream stream where the consumer exists. The stream must already exist. |
| Consumer Name | The name of the consumer to retrieve information about. |
Output
The output is a JSON object containing detailed information about the specified consumer. This includes all relevant metadata and configuration details returned by the JetStream management API for that consumer. The exact structure depends on the JetStream server response but typically includes fields like consumer configuration, state, delivery policies, and other runtime info.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a NATS JetStream server.
- Needs an API key credential configured in n8n for authenticating with the NATS server.
- Uses bundled NATS client libraries internally to communicate with the JetStream server.
Troubleshooting
Common Issues:
- Specifying a non-existent stream or consumer name will cause errors.
- Network connectivity problems to the NATS server can cause operation failures.
- Insufficient permissions or invalid credentials will prevent retrieving consumer info.
Error Messages:
Unknown consumer operation: get— indicates the operation name is incorrect or unsupported.NATS JetStream operation failed: ...— generic failure; check underlying error message for details.The stream must exist before creating consumers— ensure the stream name is valid and exists.
Resolutions:
- Verify the stream and consumer names are correct and exist on the JetStream server.
- Confirm network access and credentials are properly configured.
- Use the "continue on fail" option to handle errors gracefully in workflows.