4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, allowing users to interact with various 4leads resources such as contacts, campaigns, tags, global fields, opt-ins, and more. Specifically, for the Contact resource with the Get Value operation, the node retrieves the value of a specified global field for a selected contact. This is useful in scenarios where you want to fetch custom data associated with a contact, such as preferences, scores, or any other metadata stored in global fields.

Practical examples include:

  • Fetching a contact's subscription status stored in a global field.
  • Retrieving a custom attribute like "customer tier" or "last purchase date" from a contact record.
  • Using the contact's email as an alternative identifier to get the global field value.

Properties

Name Meaning
Global Field Select the global field whose value you want to retrieve. Options: select from list or enter ID (numeric only).
Contact Select the contact for which to get the global field value. Options: select from list or enter contact ID.
Notice Informational note that the contact's email can be used as an alternative ID.

Output

The node outputs a JSON array containing the retrieved values of the specified global field for the selected contact(s). Each item in the output corresponds to one input item processed and includes the value of the global field requested.

If the node supports binary data output (not indicated explicitly here), it would typically represent attachments or files related to the contact or global field, but this operation focuses on retrieving textual or structured data values.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • The node depends on several internal handlers for different resources; for the Contact Get Value operation, it uses the global field handler and contact handler modules.
  • The node requires proper permissions to access contacts and global fields within the 4leads account.

Troubleshooting

  • Invalid Global Field ID: If the global field ID does not match the expected numeric format, the node will throw a validation error. Ensure the ID is numeric or select the field from the provided list.
  • Contact Not Found: If the specified contact ID or email does not exist, the node may return empty results or an error. Verify the contact exists in 4leads.
  • API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm the API key is correctly set up in n8n credentials.
  • Empty Output: If the global field has no value for the contact, the output may be empty or null. Check that the field is populated in 4leads.

Links and References

Discussion