4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform to manage various resources such as contacts, campaigns, tags, opt-ins, and more. Specifically, for the Contact - Get operation, it retrieves contact information from 4leads either by a specific contact ID or by searching/filtering multiple contacts.

Common scenarios where this node is beneficial include:

  • Fetching detailed information about a single contact using their unique identifier.
  • Searching for multiple contacts based on criteria like name or email substring.
  • Paginating through large sets of contacts to process or analyze them in batches.

Practical examples:

  • Retrieve a contact's details by selecting them from a list or entering their ID.
  • Search for all contacts whose names contain a certain domain (e.g., "@example.com") and process them.
  • Fetch a specific page of contacts with a defined page size to integrate with other systems.

Properties

Name Meaning
The email of a contact can be used as an alternative ID. A notice informing that the contact's email can alternatively be used as an identifier when retrieving a contact.
Contact Select a contact either from a searchable list or by specifying the contact's ID directly. This identifies which contact to retrieve when returning a single object.
Search for multiple results Boolean flag indicating whether to return a single contact object (false) or a list of contacts matching search criteria (true).
Additional Fields When returning multiple contacts (bReturnAll = true), these fields allow specifying:
• Search String: Text to search within contact name fields.
• Page Size: Number of results per page (e.g., 5, 10, 20, 50, 200).
• Page Number: Which page of results to retrieve (1-based).

Output

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

  • When fetching a single contact, the output is a single JSON object with the contact's details.
  • When fetching multiple contacts, the output is an array of contact objects matching the search criteria and pagination settings.

Each contact object contains fields as defined by the 4leads API for contacts (not detailed here due to source code abstraction).

No binary data output is indicated for 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 for contacts.
  • No additional external dependencies are required beyond the configured API authentication.

Troubleshooting

  • Issue: No contacts returned when searching with a search string.
    Cause: The search string may not match any contact names or emails.
    Resolution: Verify the search string is correct and matches existing contacts.

  • Issue: Error when providing an invalid contact ID.
    Cause: The specified contact ID does not exist or is malformed.
    Resolution: Ensure the contact ID is valid and exists in 4leads.

  • Issue: Pagination parameters ignored or no results on certain pages.
    Cause: Page number or page size may exceed available data range.
    Resolution: Adjust page number and size to valid ranges based on total contacts.

  • Error messages: Typically originate from the 4leads API; check error details for authentication issues, invalid parameters, or rate limits.

Links and References

Discussion