Evolution API

Interact with Evolution API

Actions64

Overview

The "Procurar Mensagens" (Search Messages) operation of the Chat resource in this custom n8n node allows users to search for messages within a specific chat contact using the Evolution API. This is useful for retrieving historical conversations, filtering messages by contact, and paginating through large sets of chat data. Typical scenarios include customer support workflows, chat analytics, or automated message retrieval for reporting.

Example use cases:

Fetching all messages exchanged with a particular customer.
Building dashboards that display recent chat activity.
Automating follow-up actions based on retrieved messages.

Properties

Display Name	Type	Description
Nome Da Instância	String	Digite o nome da instância (Instance name). Required. Identifies which Evolution API instance to use.
Contato	String	Número do contato (Contact number). Required. The identifier (e.g., phone number) of the chat contact whose messages you want to search.
Página	Number	Número da página (Page number). Optional. Specifies which page of results to retrieve; used for pagination. Default is 1.
Quantidade Por Página	Number	Quantidade de mensagens por página (Messages per page). Optional. Sets how many messages are returned per page. Default is 10.

Output

The output is a JSON array where each item represents a message found for the specified contact. While the exact structure depends on the Evolution API's response, typical fields may include:

[
  {
    "id": "string",           // Unique message identifier
    "timestamp": "string",    // When the message was sent/received
    "from": "string",         // Sender identifier
    "to": "string",           // Recipient identifier
    "body": "string",         // Message content
    // ...other message metadata
  }
]

Note: The actual fields may vary depending on the Evolution API.

Dependencies

External Service: Requires access to the Evolution API.
API Key/Credentials: You must configure valid Evolution API credentials in n8n under the credential type evolutionApi.
n8n Configuration: No additional environment variables are required beyond standard credential setup.

Troubleshooting

Common Issues:
- Missing or Invalid Credentials: If the Evolution API credentials are not set up correctly, authentication errors will occur.
- Unsupported Operation: If an invalid combination of resource or operation is selected, the node will throw an error indicating the operation is not supported.
- Invalid Contact Number: Providing an incorrect or non-existent contact number will result in empty results or API errors.
- Pagination Errors: Requesting a page number that does not exist may return an empty array.
Error Messages:
- "Operação não suportada."
  Meaning: The selected operation is not available for the chosen resource.
  Resolution: Double-check the resource and operation selection.
- API-specific errors (e.g., authentication failure, rate limits) will be passed through from the Evolution API and should be resolved according to their documentation.