Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node interacts with the Evolution API to manage chat conversations by archiving or unarchiving them. 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 user might archive old customer support chats to keep their active chat list clean, or unarchive a conversation to continue a previous discussion.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance managing the chat (required). |
| Contato | The contact number associated with the chat conversation to be archived/unarchived (required). |
| Ação | Action to perform: "Arquivar" (archive) or "Desarquivar" (unarchive) (required). |
| ID Da Mensagem | The ID of the last message in the conversation (required). |
| Mensagem É Minha | Boolean indicating if the last message was sent by the instance (true/false) (required). |
Output
The node outputs a JSON array containing the result of the archive management operation. Each item in the output corresponds to the response from the Evolution API after attempting to archive or unarchive 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 state.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor API requests. - Proper configuration of the API authentication within n8n is necessary.
Troubleshooting
- Unsupported Operation Error: If the node throws an error stating the operation is not supported, verify that the "Gerenciar Arquivo" operation is correctly selected under the "Chat" resource.
- Missing Required Parameters: Ensure all required properties (instance name, contact number, message ID, etc.) are provided; missing these will cause errors.
- API Authentication Issues: Confirm that the API key credential is valid and has the necessary permissions.
- Invalid Contact or Message ID: Providing incorrect contact numbers or message IDs may lead to failed API calls or no changes in archive status.
Links and References
- Evolution API Documentation (official API reference)