Overview
The node provides operations to manage contacts within the Autocust system. Specifically, the "Edit Contact" operation allows users to update existing contact information, including default and custom attributes, as well as reassigning the contact to different lists. This is useful in scenarios where contact details need to be kept current or when segmenting contacts dynamically based on updated data.
Practical examples include:
- Updating a contact's phone number or name after receiving new information.
- Changing the lists a contact belongs to for targeted marketing campaigns.
- Modifying custom attributes such as preferences or tags associated with a contact.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to edit. |
| Reassign Contact To Lists | Optionally assign the contact to one or multiple lists. Lists can be selected from available options. |
| Default Attributes | Add or edit standard contact attributes such as First Name, Last Name, Phone Number, and Prefix. |
| Custom Attributes | Add or edit custom-defined attributes by selecting attribute names or IDs and specifying their values. |
Output
The node outputs JSON data representing the updated contact object after the edit operation completes successfully. This typically includes the contact's ID, updated attributes (both default and custom), and list assignments.
If the node supports binary data output, it would represent any associated files or media related to the contact, but this operation primarily deals with JSON contact data.
Dependencies
- Requires an API key credential for authenticating with the Autocust service.
- Uses internal methods to load options for lists and attributes dynamically.
- No additional external dependencies are indicated beyond the Autocust API access.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Contact ID will likely result in an error indicating the contact cannot be found.
- Attempting to assign lists or attributes that do not exist or are not accessible may cause failures.
- Missing required fields such as Contact ID will prevent execution.
Error Messages:
"The operation 'editContact' is not known!"— This occurs if the operation parameter is incorrectly set; ensure "Edit Contact" is selected.- API authentication errors due to invalid or missing credentials.
- Validation errors if attribute values do not meet expected formats.
Resolutions:
- Verify the Contact ID exists in the system before editing.
- Ensure all referenced lists and attributes are valid and accessible.
- Confirm API credentials are correctly configured in n8n.
Links and References
- n8n Expressions Documentation — For using expressions in attribute and list selections.
- Autocust API documentation (not provided here) for detailed attribute and list management.