Actions18
- Contact Actions
- Message Actions
- Conversation Actions
- Note Actions
- File Actions
Overview
This node integrates with the Superchat API to update the status of a conversation. It allows users to change the state of a conversation, such as marking it as open, done, spam, archived, or snoozed. This is useful in customer support or communication workflows where managing conversation lifecycle and prioritization is important.
Practical examples include:
- Marking a conversation as "done" after resolving a customer's issue.
- Snoozing a conversation until a later date/time when follow-up is needed.
- Archiving conversations that are no longer active but need to be retained for records.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the conversation to update. |
| Status | The new status to assign to the conversation. Options: Open, Done, Spam, Archived, Snoozed. |
| Snoozed Until | The date and time until which the conversation is snoozed. Required only if status is "Snoozed". |
Output
The node outputs an array of JSON objects representing the updated conversation(s). Each object contains the details of the conversation after the status update, reflecting the new status and any related metadata.
No binary data output is produced by this operation.
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 additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Missing or invalid conversation ID: Ensure the "ID" property is correctly set to a valid conversation identifier; otherwise, the API call will fail.
- Invalid status value: The status must be one of the predefined options. Setting an unsupported status will cause errors.
- Snoozed status without "Snoozed Until" date: When setting status to "Snoozed," the "Snoozed Until" property must be provided; omitting it may result in an error.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Temporary connectivity issues or Superchat API outages can cause failures; retrying later may help.