Overview
The node provides operations to manage contacts within the Autocust system. Specifically, the "Edit Contact" operation allows users to update an existing contact's information, including default attributes (like first name, last name, phone number, prefix), custom attributes, and optionally reassign the contact to one or multiple lists.
This node is beneficial in scenarios where contact data needs to be kept up-to-date automatically, such as syncing CRM data, updating customer profiles based on interactions, or managing marketing lists dynamically.
Practical example:
You have a contact whose phone number and last name changed. Using this node's "Edit Contact" operation, you can update those fields and also move the contact to different mailing lists for targeted campaigns.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique numeric identifier of the contact to edit. |
| Reassign Contact To Lists | Optionally assign the contact to one or more lists by selecting from available lists. |
| Default Attributes | Add or edit standard contact attributes. Options include: First Name, Last Name, Phone Number, Prefix. Each attribute requires a value. |
| Custom Attributes | Add or edit custom-defined attributes for the contact. You can select attribute names or IDs from a list and provide corresponding values. |
Output
The node outputs JSON data representing the updated contact after the edit operation completes successfully. This typically includes the contact's ID, updated attributes (default and custom), and list assignments.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authenticating with the Autocust service.
- Uses internal methods to load options dynamically for lists, segments, and attributes.
- The node depends on the Autocust API endpoints for contacts management.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID will likely cause errors.
- Attempting to assign lists or attributes that do not exist or are misspelled may result in failures.
- Missing required fields like Contact ID or attribute values can cause the operation to fail.
Error messages:
"The operation 'editContact' is not known!"— indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- API authentication errors if the API key credential is missing or invalid.
- Validation errors if required properties are missing or incorrectly formatted.
Resolutions:
- Verify the Contact ID exists before editing.
- Ensure all required fields are provided.
- Confirm API credentials are configured properly in n8n.
- Use expressions carefully when specifying attribute IDs or list IDs.
Links and References
- n8n Expressions Documentation — for using expressions in property fields.
- Autocust API documentation (not provided here) would be useful for understanding attribute and list IDs.