Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Update Contact" operation in the WTS Chat node allows users to modify existing contact records within the WTS system. This operation is useful for keeping contact information current and accurate, such as updating names, phone numbers, emails, social media handles, tags, custom fields, metadata, and marketing UTM parameters.
Typical scenarios include:
- Correcting or adding missing contact details.
- Updating contact status or portfolio assignments.
- Adding or modifying tags and sequences associated with a contact.
- Enriching contacts with custom fields or metadata for segmentation or personalization.
- Tracking marketing campaign data via UTM parameters.
For example, a user might update a contact's email address and add new tags after a recent interaction, or change the contact's status from "Not Sent" to "Active" to reflect engagement.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update. This is required to specify which contact record will be modified. |
| Fields | The list of contact fields to update. Options include: Annotation, CustomFields, Email, Instagram, Metadata, Name, PhoneNumber, PictureUrl, Portfolio, SequenceIds, Status, Tags, Utm. |
| Name | The contact's full name. |
| Phonenumber | The contact's phone number. |
| The contact's email address. | |
| The contact's Instagram handle or username. | |
| Annotation | Additional notes or comments about the contact. |
| Tag Names or IDs | Tags to assign to the contact. Users can select from a list or specify tag IDs using expressions. |
| Portfolio Names or IDs | Portfolios to associate with the contact. Selectable from a list or specified by IDs. |
| Sequence Names or IDs | Sequences to assign to the contact. Selectable from a list or specified by IDs. |
| Status | The contact's status. Possible values are: Active, Archived, Blocked, Empty (Not Sent). |
| Picture Url | URL pointing to the contact's picture or avatar. |
| Custom Fields | Custom key-value pairs defined by the user to store additional contact information. Multiple custom fields can be added. |
| Metadata | Arbitrary key-value metadata entries for the contact. Multiple metadata entries can be added. |
| Source UTM | UTM source parameter for tracking marketing campaigns. |
| Medium UTM | UTM medium parameter for tracking marketing campaigns. |
| Campaign UTM | UTM campaign parameter for tracking marketing campaigns. |
| Content UTM | UTM content parameter for tracking marketing campaigns. |
| Headline UTM | UTM headline parameter for tracking marketing campaigns. |
| Term UTM | UTM term parameter for tracking marketing campaigns. |
| Referral Url UTM | UTM referral URL parameter for tracking marketing campaigns. |
Output
The output of this operation is a JSON object representing the updated contact record as returned by the WTS API. It typically includes all the contact's fields after the update, reflecting the changes made.
If the update is successful, the node outputs an array with one item containing the updated contact data under the json property.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the WTS API service.
- An API key credential must be configured in n8n to authenticate requests to the WTS API.
- The node uses internal services to communicate with the WTS API endpoints for contact management.
Troubleshooting
- Missing Contact ID: If the Contact ID is empty or not provided, the node throws an error indicating that the ContactID is empty and must be filled in.
- Invalid Field Selection: If no fields are selected to update, or if the fields array is empty, the node may throw an error or perform no action.
- API Errors: Any errors returned by the WTS API during the update process are caught and rethrown as node errors with descriptive messages.
- Invalid Email Format: Although primarily checked during contact creation, ensure email addresses conform to standard formats to avoid issues.
- Metadata and Custom Fields Handling: Metadata and custom fields are expected as arrays of key-value pairs; incorrect formatting may cause errors.
- Status Field: Setting the status field to "Empty" (NOT_SEND) is treated specially and may not update the status on the server.
To resolve errors:
- Ensure all required fields, especially Contact ID, are correctly set.
- Validate input formats for emails and other fields.
- Confirm API credentials are valid and have sufficient permissions.
- Check that any referenced tags, portfolios, or sequences exist and are accessible.
Links and References
- WTS API Documentation (generic link, replace with actual if available)
- n8n Expressions Documentation
- Managing Contacts in WTS (if available)
This summary is based on static analysis of the node's execute method and provided property definitions, focusing exclusively on the "Contact" resource and "Update Contact" operation.