Actions18
- Contact Actions
- Message Actions
- Conversation Actions
- Note Actions
- File Actions
Overview
This node integrates with the Superchat API to update the assigned users of a specific conversation. It allows you to modify which users are responsible for handling or monitoring a conversation within the Superchat platform. This is useful in scenarios such as customer support workflows where conversations need to be reassigned to different team members based on workload, expertise, or availability.
Practical examples:
- Automatically reassigning conversations to available agents when the current assignees go offline.
- Updating assigned users based on conversation priority or topic.
- Batch updating multiple conversations' assignees as part of a workflow automation.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the conversation to update. |
| Assigned Users | A collection of user IDs to assign to the conversation. You can add multiple users by specifying their IDs either directly or by searching from a list of users. |
Output
The node outputs an array of JSON objects representing the result of the update operation for each input item. Each object corresponds to the updated conversation data returned by the Superchat API after modifying its assigned users.
No binary data output is involved.
Dependencies
- Requires an active connection to the Superchat API using an API key credential configured in n8n.
- The node depends on the Superchat API endpoint that handles updating conversation assignees.
- Proper permissions on the API key are necessary to modify conversation assignments.
Troubleshooting
- Invalid Conversation ID: If the provided conversation ID does not exist or is malformed, the API will return an error. Verify the ID is correct and exists in your Superchat account.
- User IDs Not Found: If any assigned user ID does not correspond to a valid user, the update may fail or ignore those users. Ensure all user IDs are valid and accessible.
- Insufficient Permissions: The API key used must have permission to update conversations. Lack of permissions will cause authorization errors.
- Empty Assigned Users List: Providing an empty list might unassign all users or cause an error depending on API behavior. Confirm intended behavior before sending empty values.
- API Rate Limits: Frequent updates may hit rate limits imposed by Superchat. Implement retry logic or reduce request frequency if encountering rate limit errors.
Links and References
- Superchat API Documentation
- Superchat Conversations Guide (hypothetical link for further reading)