4leads icon

4leads

Interact with 4leads

Actions33

Overview

The node integrates with the 4leads platform to manage various resources such as contacts, campaigns, tags, and more. Specifically, for the Contact - Update operation, it allows updating details of an existing contact in the 4leads system. This is useful in scenarios where contact information needs to be kept current, such as updating a customer's phone number, email, or address after receiving new data from another system.

Practical examples include:

  • Synchronizing updated customer details from a CRM into 4leads.
  • Correcting or enriching contact information based on user input or external data sources.
  • Automating updates to contact records when certain triggers occur in workflows.

Properties

Name Meaning
Contact The specific contact to update, selectable either from a list of existing contacts or by providing the contact's unique ID.
Additional Fields A collection of optional fields that can be updated for the contact. These include:
- Firstname The first name of the contact.
- Lastname The last name of the contact.
- E-Mail The email address of the contact.
- Mobile The mobile phone number of the contact.
- Salutation The salutation for the contact; options are "Herr" (m), "Frau" (f), or "Divers" (d).
- Company The company associated with the contact.
- Phone Number The phone number of the contact.
- Birthday The birthday of the contact (date/time).
- Position (Company) The job position of the contact within their company.
- Country The country of the contact. A comprehensive list of countries is available, including Germany, Austria, Switzerland, United Kingdom, Italy, and many others.
- Street The street address of the contact.
- Street Number The street number of the contact's address.
- ZIP Code The postal code of the contact's address.
- City The city of the contact's address.
- Fax The fax number of the contact.
- Website The website URL associated with the contact.
- Skype The Skype ID of the contact.

Note: There is also a notice indicating that the contact's email can be used as an alternative identifier.

Output

The node outputs a JSON array containing the result(s) of the update operation. Each item in the output corresponds to the updated contact record returned from the 4leads API. The structure typically includes the updated fields and metadata about the contact.

If binary data were involved, it would be summarized here, but this operation deals only with JSON data representing contact details.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • The node depends on internal handlers for managing contacts (contactHandler), which handle the communication with the 4leads service.
  • No additional external dependencies beyond the 4leads API and its authentication.

Troubleshooting

  • Common Issues:

    • Providing an invalid or non-existent contact ID will likely cause errors.
    • Missing required credentials or incorrect API keys will prevent successful API calls.
    • Attempting to update without specifying any fields may result in no changes or errors.

  • Error Messages:

    • Authentication errors indicate issues with the API key; verify and reconfigure credentials.
    • Validation errors may occur if field values do not meet expected formats (e.g., invalid email).
    • Network or timeout errors suggest connectivity problems with the 4leads API.

To resolve these, ensure correct contact selection, valid input data, and proper API credentials.

Links and References

Discussion