Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the Chat resource and the Procurar Mensagens (Find Messages) operation, it enables searching or retrieving chat messages from a specified contact within an instance. This is useful in scenarios where you want to programmatically access message history for analysis, monitoring, or integration with other systems.
For example, you could use this node to:
- Retrieve recent messages exchanged with a particular contact.
- Paginate through chat history by specifying page number and messages per page.
- Automate message audits or backups by fetching messages regularly.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance where the chat data resides. Required to identify the source. |
| Contato | The contact's phone number or identifier whose messages you want to find. |
| Página | The page number of the results to retrieve, enabling pagination through messages. |
| Quantidade Por Página | Number of messages to return per page, controlling the batch size of each query. |
Output
The node outputs a JSON array containing the retrieved messages matching the search criteria. Each item in the array represents a message object with details such as sender, content, timestamp, and possibly message metadata depending on the Evolution API response structure.
If the API supports binary data (e.g., media attachments), those would be included in the output accordingly, but based on the provided code and properties, the primary output is JSON-formatted message data.
Dependencies
- Requires an API key credential for authenticating with the Evolution API service.
- The node expects the Evolution API base URL
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credential in n8n is necessary for successful requests.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource combination, the node throws an error indicating the function is not supported. Ensure you choose valid resource-operation pairs.
- Missing required parameters: The node requires "Nome Da Instância" and "Contato" to be set. Omitting these will likely cause errors or empty results.
- API authentication failures: Incorrect or missing API credentials will prevent the node from connecting to the Evolution API.
- Pagination issues: Requesting pages beyond available data may return empty arrays; verify page numbers and offsets.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes for further customization guidance