4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, allowing users to interact with various resources such as campaigns, contacts, tags, opt-ins, sign-in forms, global fields, opt-in cases, and storage fields. Specifically, for the Field resource with the Get operation, it retrieves information about global fields defined in 4leads.

Typical use cases include:

  • Fetching details of a specific global field by its ID.
  • Searching and retrieving multiple global fields based on search criteria, pagination, and page size.
  • Integrating global field data into workflows for marketing automation, contact management, or reporting.

For example, a user might want to retrieve a single global field to update or validate its value, or fetch a list of global fields matching certain names to synchronize with another system.

Properties

Name Meaning
Search for multiple results (bReturnAll) Boolean flag to choose between returning a single global field object (false) or a list of objects (true).
Global Field (globalFieldId) Select a specific global field either from a searchable list or by entering its numeric ID. Required if bReturnAll is false.
Additional Fields (globalFieldQs) Collection of optional query parameters used when bReturnAll is true:
- Search String: Text to search within global field names.
- Page Size: Number of results per page.
- Page Number: The page number to retrieve in the result set.

Output

The node outputs an array of JSON objects representing one or more global fields retrieved from 4leads.

  • When fetching a single global field (bReturnAll = false), the output contains one object with detailed properties of that global field.
  • When fetching multiple global fields (bReturnAll = true), the output is an array of objects, each representing a global field matching the search criteria and pagination settings.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • The node depends on internal handlers that communicate with 4leads endpoints to fetch global field data.
  • No additional external services are required beyond the 4leads API.

Troubleshooting

  • Invalid Global Field ID: If the provided global field ID does not match the expected numeric format, the node will throw a validation error. Ensure the ID consists only of digits.
  • Empty Results: When searching with filters (search string, page size, page number), no results may be returned if the criteria do not match any global fields. Adjust search parameters accordingly.
  • 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 credentials.
  • Pagination Issues: Providing a page number or page size that exceeds available data may result in empty responses. Use sensible values based on total records.

Links and References

Discussion