4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform to interact with various resources, including storage fields. Specifically, for the Storage-Field resource and the Get operation, it allows users to retrieve either a single storage object by its ID or multiple storage objects based on search criteria and pagination.

Common scenarios where this node is beneficial include:

  • Fetching detailed information about a specific storage entity in 4leads.
  • Searching through multiple storage entries using text filters.
  • Paginating through large sets of storage data to process or analyze them incrementally.

Practical examples:

  • Retrieve a particular storage field by specifying its ID to update or use its data downstream.
  • Search for all storages containing a certain keyword in their name and process the results in batches.

Properties

Name Meaning
Search for multiple results (bReturnAll) Boolean flag to choose between returning a single storage object (false) or a list of storage objects (true).
Storage (storageId) When bReturnAll is false, select a specific storage by either choosing from a searchable list or entering its numeric ID.
Additional Fields (storageQs) When bReturnAll is true, optional parameters to refine the search:
• Search String: Text to filter storage names (e.g., searching for names containing "@muster.de").
• Page Size: Number of results per page (e.g., 5, 10, 20, 50, 200).
• Page Number: The page index to retrieve (starting at 1).

Output

The node outputs an array of JSON objects representing storage entities retrieved from 4leads.

  • If a single storage is requested (bReturnAll = false), the output contains one object with details of that storage.
  • If multiple storages are requested (bReturnAll = true), the output contains an array of storage objects matching the search criteria and pagination settings.

Each storage object typically includes properties such as its ID, name, and other metadata relevant to the storage field in 4leads.

The node does not output binary data.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • Uses internal helper methods to fetch storage data, including support for searching and pagination.
  • No additional external dependencies beyond the 4leads API and the configured credential.

Troubleshooting

  • Invalid Storage ID: If the provided storage ID is not numeric or does not exist, the node may throw an error. Ensure the ID is correct and numeric.
  • Empty Results: When searching with a search string or pagination, if no results are returned, verify the search terms and page numbers are valid.
  • API Authentication Errors: If the API key credential is missing or invalid, the node will fail to connect. Verify the API key configuration in n8n.
  • Pagination Issues: Requesting a page number beyond the available range may return empty results; adjust the page number accordingly.

Links and References

Discussion