Actions8
- Bucket Actions
- Object Actions
Overview
This node integrates with NATS JetStream Object Store, allowing users to manage buckets and objects within those buckets. Specifically, it supports operations such as creating, deleting, and retrieving information about buckets, as well as uploading, downloading, deleting, and getting info on objects stored inside these buckets.
The "Delete Object" operation under the "Object" resource enables users to delete a specific object (file or data) from a given bucket in the NATS JetStream Object Store.
Common scenarios:
- Cleaning up outdated or unnecessary files stored in a bucket.
- Automating file lifecycle management by removing objects after processing.
- Managing storage space by deleting large or temporary objects programmatically.
Practical example:
You have a bucket named my-files containing various reports. After processing a report reports/2024/sales.pdf, you want to delete it automatically to free up space. This node can be configured to delete that specific object by specifying the bucket name and object path.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the bucket where the object resides. Must contain only letters, numbers, hyphens, and underscores; no spaces or dots allowed. Example: my-files. |
| Object Name | The name or path of the object to delete within the bucket. Can include forward slashes for organization. Examples: images/logo.png, documents/report.pdf, or reports/2024/sales.pdf. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm successful deletion or provide relevant metadata or status information returned by the NATS JetStream Object Store API.
If an error occurs during deletion, the output will contain error details including the message and the item index.
The node does not output binary data for this operation.
Dependencies
- Requires a valid connection to a NATS JetStream server with access to the Object Store feature.
- Needs credentials providing authentication to the NATS server (an API key or token).
- Uses the official NATS client libraries bundled with the node.
- No additional environment variables are explicitly required beyond the credential setup.
Troubleshooting
- Invalid bucket name: Bucket names must not contain spaces or dots and should only use letters, numbers, hyphens, and underscores. Using invalid characters will cause validation errors.
- Unknown bucket or object operation: If an unsupported operation is specified, the node throws an error indicating the unknown operation.
- Object not found: Attempting to delete a non-existent object may result in an error from the NATS server.
- Connection issues: Failure to connect to the NATS server due to incorrect credentials or network problems will cause the node to error out.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, collecting errors in the output.
To resolve errors:
- Verify bucket and object names follow naming rules.
- Ensure the NATS server is reachable and credentials are correct.
- Confirm the object exists before attempting deletion.