Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" provides integration with the Evolution API service, allowing users to interact programmatically with various resources and operations exposed by this API. Specifically, for the Chat resource and the Procurar Mensagens (Find Messages) operation, the node enables searching or retrieving chat messages from a specified contact within an instance of the Evolution API environment.
This node is beneficial in scenarios where automated retrieval of chat history is needed, such as:
- Customer support systems fetching past conversations.
- Analytics platforms analyzing message content or frequency.
- Archiving tools that periodically back up chat data.
For example, a user can configure the node to fetch the first 10 messages from a particular contact's chat history on a given instance, facilitating downstream processing or reporting.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Evolution API instance to connect to. |
| Contato | The contact number (remote JID) whose messages are to be searched or retrieved. |
| Página | The page number of the results to retrieve (for pagination). |
| Quantidade Por Página | The number of messages to return per page (page size). |
Output
The node outputs a JSON array containing the retrieved chat messages matching the search criteria. Each item in the array represents a message object with details as returned by the Evolution API. The exact structure depends on the API response but typically includes message content, timestamps, sender/receiver information, and message metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for the API is
https://doc.evolution-api.com/api-reference. - Proper network access to the Evolution API endpoint is necessary.
Troubleshooting
- Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the selected resource and operation names match those implemented in the node.
- Authentication Failures: Ensure the API key or authentication token is correctly set up in the node credentials.
- Pagination Issues: If no messages are returned, check if the page number and offset values are within valid ranges and that the contact has messages.
- Invalid Contact Number: Confirm the contact number format matches what the Evolution API expects.
- Network Errors: Verify internet connectivity and that the Evolution API endpoint is reachable.
Links and References
- Evolution API Documentation (official API reference)
- n8n Documentation on Creating Custom Nodes