Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
The node is designed to update a contact's information in an external system. It allows users to specify the contact by their unique ID and update various details such as email address, SMS number, and custom data fields. This node is useful in scenarios where contact information needs to be kept current, such as syncing user profiles, updating marketing lists, or managing subscriber data dynamically.
Practical examples include:
- Updating a subscriber's email after they change it on a website.
- Adding or modifying custom data fields related to a contact's preferences or status.
- Changing the SMS number for contacts who opt-in for SMS notifications.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update. This is required to specify which contact to modify. |
| Email Address | The new email address to assign to the contact. |
| SMS Number | The new SMS number to assign to the contact. |
| Data Fields | Optional custom data fields to update for the contact. Each field consists of: |
| - Field Name: Select from available fields or specify an ID via expression. | |
| - Field Value: The value to set for the selected data field. |
Output
The node outputs JSON data representing the updated contact information as returned by the external service. This typically includes the contact's ID, updated email, SMS number, and any modified data fields. If the external API supports binary data output (e.g., profile images), it would be included accordingly, but this node primarily focuses on JSON contact data.
Dependencies
- Requires connection to an external contact management or marketing platform via an API.
- Needs appropriate API authentication credentials configured in n8n (such as an API key or token).
- The node relies on internal methods and routing logic bundled within its implementation to handle API requests and responses.
Troubleshooting
- Missing Contact ID: The update operation requires a valid contact ID. Ensure this property is provided; otherwise, the node will fail to identify which contact to update.
- Invalid Field Names: When specifying custom data fields, ensure the field names exist in the external system. Using invalid or misspelled field IDs may cause errors.
- Authentication Errors: Verify that the API credentials are correctly configured and have sufficient permissions to update contacts.
- API Rate Limits: Frequent updates might hit rate limits imposed by the external service. Implement error handling or retries if necessary.
Links and References
- n8n Expressions Documentation — For using expressions in field values.
- Refer to the external service's API documentation for detailed information on contact update endpoints and data field definitions.