NATS Object Store
Store and retrieve objects (files, data) in NATS JetStream Object Store - manage buckets and objects
Actions8
- Object Actions
- Bucket Actions
Overview
This node integrates with NATS JetStream Object Store, allowing users to manage buckets and objects within those buckets. Specifically, the Bucket - Delete operation deletes an existing bucket from the object store.
Common scenarios for this node include:
- Cleaning up unused or temporary buckets in your NATS JetStream Object Store.
- Automating lifecycle management of storage buckets as part of a larger workflow.
- Managing storage resources programmatically without manual intervention.
For example, you might use this node to delete a bucket named "my-files" after processing and archiving its contents elsewhere.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the Object Store bucket to delete. Bucket names can only contain alphanumeric characters, dashes, and underscores. |
Output
The output JSON contains the result of the delete operation. While the exact structure depends on the underlying NATS JetStream response, it typically confirms successful deletion or provides error details if the operation failed.
Example output JSON might look like:
{
"success": true,
"bucket": "my-files"
}
If an error occurs, the node will return an error object describing the issue.
Dependencies
- Requires a valid connection to a NATS JetStream server with access to the Object Store feature.
- Needs an API key credential configured in n8n for authenticating with the NATS server.
- The node uses internal utilities to validate bucket names and manage connections.
Troubleshooting
- Invalid Bucket Name: Bucket names must only contain alphanumeric characters, dashes, and underscores. Using invalid characters will cause validation errors.
- Unknown Operation Error: If the operation name is incorrect or unsupported, the node throws an error indicating the unknown operation.
- Connection Issues: Failure to connect to the NATS server due to incorrect credentials or network issues will prevent execution.
- Bucket Not Found: Attempting to delete a non-existent bucket may result in an error from the NATS server.
- To handle errors gracefully, enable the "Continue On Fail" option in the node settings.