Actions18
- Contact Actions
- Message Actions
- Conversation Actions
- Note Actions
- File Actions
Overview
The node integrates with the Superchat API to update labels on a specific conversation. It allows users to assign one or more label IDs to a conversation identified by its unique ID. This operation is useful for categorizing, organizing, or tagging conversations within Superchat to improve workflow management and filtering.
Common scenarios:
- Automatically tagging conversations based on certain triggers or criteria.
- Updating conversation labels in bulk during data synchronization.
- Managing conversation states or categories dynamically in customer support workflows.
Practical example:
A support team wants to mark a conversation as "Urgent" and "Billing" by applying corresponding labels after detecting keywords in the conversation content. This node can be used to update those labels programmatically.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the conversation to update. |
| Labels | One or more label IDs to assign to the conversation. Each label can be selected by ID or searched from existing labels. |
Output
The node outputs an array of JSON objects representing the result of the label update operation for each input item. Each object typically contains details about the updated conversation, including confirmation of the applied labels.
If the node supports binary data output (not indicated here), it would represent any files or attachments related to the conversation update, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the Superchat API via an API key credential configured in n8n.
- The node depends on the Superchat API's permissions to update conversation labels.
- No additional external services are required beyond the Superchat API.
Troubleshooting
- Missing or invalid conversation ID: Ensure the provided conversation ID exists and is correctly formatted.
- Invalid label IDs: Verify that the label IDs exist in Superchat; otherwise, the API may reject the update.
- API authentication errors: Confirm that the API key credential is valid and has sufficient permissions.
- Network issues: Check connectivity to the Superchat API endpoint.
- Empty label list: Providing no labels might result in no changes or errors depending on API behavior.
Common error messages might include:
- "Conversation not found" — check the conversation ID.
- "Unauthorized" or "Authentication failed" — verify API credentials.
- "Invalid label ID" — confirm label IDs are correct and accessible.
Links and References
- Superchat API Documentation
- n8n documentation on creating custom nodes