4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, allowing users to perform various operations on different resources such as Campaigns, Contacts, Tags, Opt-Ins, Sign-in Forms, Global Fields, Opt-in Cases, and Storage Fields. Specifically, for the Contact resource with the Get Field List operation, the node retrieves a list of fields associated with a contact in 4leads.

Typical use cases include:

  • Fetching all custom or standard fields related to a specific contact for data synchronization.
  • Using the retrieved field list to dynamically build forms or update contact information in workflows.
  • Integrating contact data from 4leads into other systems by first understanding the available fields.

Example: A marketing automation workflow might retrieve the field list of a contact to decide which fields need updating based on user interactions.

Properties

Name Meaning
Contact Select the contact whose field list you want to retrieve. You can select a contact either from a searchable list or specify the contact ID directly.

Note: There is also a notice property shown for some operations related to contacts, indicating that the email of a contact can be used as an alternative identifier.

Output

The node outputs a JSON array where each item represents a field associated with the specified contact. Each field object typically contains metadata about the field such as its name, type, value, and possibly other attributes defined by 4leads.

If binary data were involved (not indicated here), it would represent file attachments or similar content related to the contact fields.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • The node depends on internal handlers for each resource; for contacts, it uses a dedicated contact handler module.
  • No additional external dependencies are required beyond the 4leads API access.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Specifying a non-existent contact ID will result in errors or empty results.
    • Network connectivity problems may prevent successful API calls.

  • Error messages:

    • Authentication errors indicate invalid or expired API keys; reconfigure credentials.
    • "Contact not found" or similar messages suggest verifying the contact ID or selection.
    • Timeout or network errors require checking internet connectivity or 4leads service status.

Links and References

Discussion