Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the Chat resource and the Gerenciar Arquivo (Manage Archive) operation, it enables archiving or unarchiving a chat conversation associated with a specific contact. This is useful in scenarios where users want to organize their chat history by moving conversations into or out of an archive state programmatically.
Practical examples include:
- Automatically archiving chats after a certain period of inactivity.
- Unarchiving conversations when new messages arrive or upon user request.
- Managing chat states in bulk as part of workflow automation.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to be used for the operation. |
| Contato | The contact number whose chat conversation will be archived or unarchived. |
| Ação | Action to perform: either "Arquivar" (archive) or "Desarquivar" (unarchive) the chat. |
| ID Da Mensagem | The ID of the last message in the conversation, used to identify the message context. |
| Mensagem É Minha | Boolean indicating if the message was sent by the instance (true) or not (false). |
Output
The node outputs a JSON array containing the result of the archive management operation. The exact structure depends on the Evolution API response but generally includes confirmation of the archive/unarchive action performed on the specified chat.
If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API service to be accessible and properly configured.
- No additional environment variables or external dependencies are explicitly required beyond the API authentication.
Troubleshooting
- Unsupported Operation Error: If the selected operation is not supported for the chosen resource, the node throws an error stating the operation is not supported. Ensure that the resource and operation names match exactly those implemented.
- Missing Required Parameters: All input properties marked as required must be provided; otherwise, the node will fail.
- API Authentication Issues: Failure to authenticate with the Evolution API due to invalid or missing credentials will cause errors. Verify that the API key credential is correctly set up.
- Invalid Contact or Message ID: Providing incorrect contact numbers or message IDs may lead to failed archive operations. Double-check these inputs.
- Network or Service Errors: Connectivity issues or Evolution API downtime can cause execution failures.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
- General best practices for managing chat archives in automated workflows