Actions33
- Campaign Actions
- Contact Actions
- Field Actions
- Opt-In Actions
- Opt-in-Case Actions
- Sign in Form Actions
- Storage-Field Actions
- Tag Actions
Overview
This node integrates with the 4leads platform to update a specific storage field. It allows users to modify properties of a storage entry such as its name, type, key, and value. This is useful in scenarios where you need to programmatically manage or update stored data fields within 4leads, for example updating user metadata, counters, timestamps, or textual information associated with a storage key.
Practical examples:
- Updating a numeric counter that tracks user actions.
- Changing a text label or description stored in 4leads.
- Setting a datetime field to record the last update time.
Properties
Name | Meaning |
---|---|
Storage | Select the target storage entry to update. Can be chosen from a list or specified by ID (numeric). |
Name | The new name to assign to the storage field. |
Type | The type of the storage field. Options: Text, Numeric, Datetime, Numeric-sum. |
Key | The new key identifier for the storage field. |
Value (Text) | The text value to set if the storage type is "Text". |
Value (Numeric) | The numeric value to set if the storage type is "Numeric" or "Numeric-sum". |
Value (Datetime) | The datetime value to set if the storage type is "Datetime". |
Output
The node outputs an array of JSON objects representing the updated storage entries. Each object corresponds to a storage field after the update operation, containing its current state including any changed properties.
No binary data output is indicated.
Dependencies
- Requires an API authentication token credential for 4leads.
- Uses internal 4leads API methods to fetch and update storage fields.
- No additional external dependencies beyond the 4leads API and n8n's credential system.
Troubleshooting
- Invalid Storage ID: If specifying storage by ID, ensure it is numeric only; otherwise, a validation error will occur.
- Missing Required Fields: The "Storage" property is mandatory; failure to provide it will cause errors.
- Type Mismatch: Ensure the value provided matches the selected storage type (e.g., do not provide text for a numeric field).
- API Errors: Network issues or invalid API credentials can cause failures; verify API key validity and connectivity.
- Empty Results: If no storage matches the selection criteria, the node may return empty output.
Links and References
- 4leads Official Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes