Actions22
- Broadcasts Actions
- Embeddings Actions
- Contacts Actions
- Conversations Actions
- Tags Actions
Overview
This node operation updates an existing contact by its unique identifier. It is useful in scenarios where you need to modify or correct contact information stored in a system, such as updating a customer's profile details after receiving new data or correcting errors.
Practical examples include:
- Updating a contact's email address or phone number after they provide new contact info.
- Adding or changing notes related to a contact for better record keeping.
- Modifying demographic details like occupation, gender, or birthdate to keep the contact profile current.
Properties
| Name | Meaning |
|---|---|
| Contact Id | The unique identifier of the contact to update (required). |
| First Name | The contact's first name. |
| Last Name | The contact's last name. |
| The contact's email address. | |
| Phone | The contact's phone number. |
| Occupation | The contact's occupation or job title. |
| Gender | The contact's gender. |
| Birthdate | The contact's birthdate, typically in string format (e.g., "YYYY-MM-DD"). |
| Age | The contact's age as a number. |
| Notes | Additional notes or comments about the contact. |
Output
The node outputs JSON data representing the updated contact object. This output includes all the fields that were updated and possibly other contact details returned by the API after the update operation.
If the node supports binary data output, it would typically relate to attachments or files associated with the contact, but based on the provided information, this operation focuses on JSON data only.
Dependencies
- Requires an API key credential for authenticating requests to the external contact management service.
- The base URL for the API must be configured in the node credentials.
- The node sends HTTP requests with JSON payloads to update contact information.
Troubleshooting
- Missing Contact Id: The operation requires a valid contact ID. If omitted or incorrect, the API will likely return an error indicating the contact was not found.
- Invalid Field Values: Providing improperly formatted values (e.g., invalid date format for birthdate) may cause the API to reject the update.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to update contacts.
- Network Issues: Connectivity problems can prevent the node from reaching the API endpoint.
- API Limits: Some services impose rate limits; exceeding these may result in temporary failures.
To resolve errors, verify input data correctness, confirm credential validity, and check network connectivity.
Links and References
- Refer to the external contact management API documentation for detailed field requirements and error codes.
- n8n documentation on how to configure API credentials and use HTTP request nodes for similar operations.