Overview
The node is designed as a "Datastore Node" that supports operations to interact with a datastore property. Specifically, it can set, get, or clear a property in the datastore. In the provided context, the focus is on the Clear Datastore Property operation, which clears a specified field in the datastore.
This node would be beneficial in workflows where you need to manage persistent data across executions, such as clearing cached values, resetting configuration fields, or removing temporary data stored in a datastore.
For example, if you have a workflow that stores user session data or API tokens in a datastore field, this node can clear those fields when they are no longer needed or before starting a new session.
Properties
| Name | Meaning |
|---|---|
| Field in Datastore | The specific datastore field to operate on (e.g., spreadsheet_id). This identifies which property will be cleared in the datastore. |
Output
The node outputs an array of items, each containing a JSON object with a single key named key. The value of key is a string indicating the operation performed along with a timestamp, for example:
{
"key": "clearDatastoreProperty 2024-06-01T12:00:00.000Z"
}
No binary data output is produced by this node.
Dependencies
- No external services or APIs are directly called within the node.
- The node relies on n8n's internal mechanisms for managing input and output data.
- No special environment variables or credentials are required for the Clear Datastore Property operation.
Troubleshooting
- Unsupported Operation Error: If an unsupported operation is specified, the node throws an error stating the operation is not implemented. Ensure the operation parameter is correctly set to one of the supported values (
setDatastoreProperty,getDatastoreProperty, orclearDatastoreProperty). - Empty or Missing Field: Since the
Field in Datastoreproperty is required, leaving it empty may cause unexpected behavior or errors. Always provide a valid field name. - No Actual Clearing Logic: The current implementation only returns a message indicating the operation was called but does not perform any real clearing of data. Users expecting actual datastore manipulation should verify if additional configuration or custom code is necessary.