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, allowing users to interact with various resources such as campaigns, contacts, tags, opt-ins, and storage fields. Specifically, for the Storage-Field resource with the Set Value operation, the node sets a new value for a specified storage field within 4leads.
Common scenarios include updating configuration or metadata stored in 4leads storage fields dynamically during workflow execution. For example, you might update a flag or status value in a storage field based on external triggers or data processing results.
Properties
| Name | Meaning |
|---|---|
| Storage | Select the target storage field to update. You can choose from a list of storages or specify the storage by its numeric ID. |
| Value | The new string value to set for the selected storage field. |
Output
The node outputs an array of JSON objects representing the result(s) of the storage update operation. Each object corresponds to the updated storage field's state or confirmation of the update. The exact structure depends on the 4leads API response but generally includes identifiers and the new value.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the 4leads platform via an API key credential.
- The node depends on internal handlers that communicate with 4leads API endpoints.
- Proper configuration of the 4leads API credentials in n8n is necessary.
Troubleshooting
- Invalid Storage ID: If specifying storage by ID, ensure it is a numeric string; otherwise, validation will fail.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Storage Not Found: Selecting a storage that does not exist or is inaccessible will cause errors.
- Empty Value: The "Value" property is required; leaving it empty will cause the node to throw an error.
- API Rate Limits: Frequent updates may hit API rate limits; consider adding delays or batching operations.
Links and References
- 4leads Official Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes