Actions9
- Namespace Actions
- Key-Value Actions
Overview
This node integrates with Cloudflare Workers KV, a globally distributed key-value storage system. It allows users to manage key-value pairs within specified namespaces on Cloudflare's platform. The "Delete Multiple" operation specifically enables the deletion of multiple keys in a single request from a given namespace.
Common scenarios for this node include:
- Bulk removal of cached or temporary data stored in Cloudflare KV.
- Cleaning up multiple outdated or invalid keys efficiently.
- Managing large datasets where batch operations reduce API calls and improve performance.
For example, if you have a list of session tokens or feature flags stored as keys in a namespace, you can delete several of them at once by providing their keys comma-separated.
Properties
| Name | Meaning |
|---|---|
| Namespace ID | The ID of the KV namespace where the keys reside. |
| Keys | Comma-separated list of keys to delete from the specified namespace (e.g., key1,key2). |
Output
The output JSON contains the response from Cloudflare's API after attempting to delete the specified keys. Typically, it includes a success indicator and any relevant metadata returned by the API.
Example output structure:
{
"success": true,
// Additional API response fields may be present
}
If an error occurs during deletion, the output will contain error details instead.
Dependencies
- Requires a valid Cloudflare account with access to Workers KV.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The node communicates with Cloudflare's REST API endpoint for KV namespaces and values.
Troubleshooting
Common issues:
- Invalid or missing Namespace ID: Ensure the namespace ID is correct and accessible.
- Incorrect keys format: Keys must be provided as a comma-separated string without extra spaces.
- API authentication errors: Verify that the API token has sufficient permissions for KV operations.
- Network or rate limiting errors from Cloudflare.
Error messages:
"Key not found": Returned if one or more keys do not exist; these keys are skipped or reported individually.- HTTP 401/403 errors: Indicate authentication or permission problems; check API token validity.
- Other HTTP errors: May indicate malformed requests or server issues; review the error message and adjust parameters accordingly.