Actions48
- Chat Actions
- Mensagem Actions
- Grupo Actions
- Perfil Actions
Overview
This node integrates with the Zappfy API to manage chat conversations, specifically allowing users to archive or unarchive chat conversations. It is useful in scenarios where users want to organize their chat history by moving conversations into an archive state or restoring them back to active status. For example, a customer support team might archive resolved chats to keep their workspace clean, or unarchive chats when needing to revisit past conversations.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to be used for the operation. |
| Contato | The contact number associated with the chat conversation to be archived or unarchived. |
| Ação | Action to perform on the chat: either "Arquivar" (archive) or "Desarquivar" (unarchive). |
| ID Da Mensagem | The ID of the last message in the conversation, used to identify the specific chat. |
| Mensagem É Minha | Boolean indicating if the last message was sent by the instance (true) or not (false). |
Output
The node outputs a JSON array containing the result of the archive/unarchive operation performed on the specified chat conversation. The exact structure depends on the API response but generally includes confirmation of the action taken and any relevant metadata about the chat's new state.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Zappfy API.
- The node uses the base URL
https://docs.zappfy.io/api-referencefor API requests. - Proper configuration of the API authentication within n8n is necessary.
Troubleshooting
- Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the resource is set to "Chat" and the operation to "Gerenciar Arquivo" (manage archive). This error indicates a mismatch or unsupported combination.
- Missing Required Parameters: Ensure all required properties (instance name, contact number, message ID, action, and fromMe flag) are provided; missing these will cause errors.
- API Authentication Issues: Confirm that the API key or authentication token is correctly configured and valid.
- Invalid Contact or Message ID: Using incorrect or non-existent contact numbers or message IDs may lead to failed operations or no effect.
Links and References
- Zappfy API Documentation – Official API reference for detailed endpoint information and usage guidelines.