Overview
The WeeDB Key Value Create node allows you to store a key-value pair in a WeeDB database from within an n8n workflow. This is useful for persisting small pieces of data, such as configuration values, tokens, or state information that can be retrieved later in your automation processes.
Practical examples:
- Saving a user's session token after authentication.
- Storing the last processed record ID to avoid duplicate processing.
- Keeping feature flags or runtime configuration values accessible across workflow executions.
Properties
| Display Name | Type | Meaning |
|---|---|---|
| Key | String | The identifier under which the value will be stored in WeeDB. |
| Value | String | The actual data/content to save under the specified key. |
Output
The node outputs a JSON object with the result of the storage operation. The structure is:
{
"item": <result>
}
Where <result> contains the response from the WeeDB set operation, typically confirming the key and value saved.
Dependencies
- WeeDB Database: Requires access to a WeeDB instance.
- Credentials: You must configure a credential named
weeDBConnectionin n8n, which should include at least adatabaseId. - n8n Environment: No additional environment variables are required beyond the credential setup.
Troubleshooting
"Failed to initialize WeeDB":
This error occurs if the node cannot connect to the WeeDB instance using the provided credentials.
Resolution: Check that yourweeDBConnectioncredential is correctly configured and that thedatabaseIdis valid.Missing or Invalid Key/Value:
If either the Key or Value fields are empty or invalid, the operation may not behave as expected.
Resolution: Ensure both fields are filled with appropriate string values.
Links and References
- n8n Documentation: Credentials
- (If available) WeeDB documentation for further details on usage and API responses.