4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform to manage various resources, including Storage-Fields. Specifically, for the Storage-Field resource with the Create operation, it allows users to create a new storage field by specifying its name, type, key, and value. This is useful in scenarios where you want to store custom data fields dynamically within 4leads, such as adding metadata or additional attributes to contacts or campaigns.

Practical examples include:

  • Creating a text-based storage field to hold notes or descriptions.
  • Creating numeric fields to track counts or scores.
  • Creating datetime fields to record timestamps.
  • Using numeric-sum type fields to accumulate values over time.

Properties

Name Meaning
Name The name of the storage field to create.
Type The data type of the field. Options: Text, Numeric, Datetime, Numeric-sum.
Key The unique key identifier for the storage field.
Value (Text) The text value to assign to the field (required if Type is Text).
Value (Numeric) The numeric value to assign to the field (required if Type is Numeric or Numeric-sum).
Value (Datetime) The datetime value to assign to the field (required if Type is Datetime).

Output

The node outputs an array of JSON objects representing the created storage fields. Each object corresponds to a storage field created in 4leads and contains details about that field as returned by the 4leads API.

If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON.

Dependencies

  • Requires an active connection to the 4leads API via an API authentication token configured in n8n credentials.
  • The node depends on internal handler modules to process operations per resource; for Storage-Field creation, it uses a dedicated storage handler module.
  • No other external services or environment variables are explicitly required beyond the 4leads API credential.

Troubleshooting

  • Common issues:

    • Missing required parameters such as Name, Key, or Value will likely cause errors.
    • Providing a Value type that does not match the selected Type (e.g., text value for a numeric field) may result in validation errors.
    • API authentication failures due to invalid or missing API keys.
    • Network connectivity issues when calling the 4leads API.

  • Error messages and resolutions:

    • "Missing required parameter" — Ensure all required fields (Name, Key, and appropriate Value) are filled.
    • "Invalid API credentials" — Verify the API key credential is correctly set up in n8n.
    • "Type mismatch error" — Confirm the Value input matches the selected Type.
    • "Network error" — Check internet connection and API endpoint accessibility.

Links and References

Discussion