Actions18
- Contact Actions
- Message Actions
- Conversation Actions
- Note Actions
- File Actions
Overview
This node updates an existing contact in the Superchat system. It allows users to modify various details of a contact such as their name, gender, email addresses, phone numbers, and custom attributes. This is useful for keeping contact information current and accurate within workflows that manage customer or user data.
Practical examples include:
- Automatically updating contact details when receiving new information from a form submission.
- Synchronizing contact records with external CRM systems.
- Enriching contact profiles with additional custom attributes based on business logic.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the contact to update (required). |
| First Name | The first name of the contact. |
| Last Name | The last name of the contact. |
| Gender | The gender of the contact. Options: Do Not Update, Female, Male, Diverse. |
| Email Addresses | A list of email addresses associated with the contact. Each entry is a string value. |
| Phone Numbers | A list of phone numbers associated with the contact. Each entry is a string value. |
| Custom Attributes | Custom fields defined by the user to store additional contact information. |
Output
The node outputs an array of JSON objects representing the updated contact(s). Each object contains the contact's properties after the update operation, reflecting any changes made.
If binary data were involved (not applicable here), it would typically represent files or attachments related to the contact.
Dependencies
- Requires an API key credential for authenticating with the Superchat API.
- The node depends on the Superchat API being accessible and properly configured.
- No other external dependencies are indicated.
Troubleshooting
- Common issues:
- Providing an invalid or non-existent contact ID will likely result in an error indicating the contact could not be found.
- Omitting required parameters such as the contact ID will cause validation errors.
- Incorrectly formatted email addresses or phone numbers might be rejected by the API.
- Error messages:
- "Contact not found" — Verify the contact ID is correct and exists.
- "Authentication failed" — Check that the API key credential is valid and has necessary permissions.
- "Invalid input" — Ensure all provided fields conform to expected formats and types.