Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The Ler Mensagens operation of the Chat resource in this custom n8n node allows you to read messages from a specific contact using the Evolution API. This is useful for automating workflows that need to fetch and process WhatsApp or chat messages, such as archiving conversations, triggering actions based on received messages, or integrating chat data with other systems.
Practical examples:
- Automatically retrieving unread messages from a customer support chat.
- Fetching message details for audit or compliance purposes.
- Integrating chat history into CRM or ticketing systems.
Properties
Display Name | Type | Meaning |
---|---|---|
Nome Da Instância | String | The name of the instance. Used to identify which Evolution API instance to interact with. (Required) |
Contato | String | The contact number (remoteJid) whose messages you want to read. (Required) |
ID Da Mensagem | String | The unique identifier of the message to be read. (Required) |
Mensagem É Minha | Boolean | Indicates if the message was sent by your own instance. (Required) |
Output
The output will be a JSON array containing the message(s) retrieved from the specified contact. Each item in the array represents a message object as returned by the Evolution API. The structure typically includes fields such as:
[
{
"id": "string", // Unique message ID
"fromMe": true, // Whether the message was sent by your instance
"remoteJid": "string", // Contact number
"body": "string", // Message content
"timestamp": "string", // When the message was sent/received
// ...other fields depending on the API response
}
]
Note: The exact structure depends on the Evolution API's response.
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, the node will fail to authenticate.
- Unsupported Operation Error: If you select an unsupported resource or operation, you may see an error like:
"Operação não suportada."
"A função "read-messages" para o recurso "chat-api" não é suportada!"- Resolution: Ensure you have selected the correct resource and operation as supported by the node.
- Invalid Parameters: Supplying incorrect or missing values for required properties (such as instance name, contact, or message ID) will result in errors.
- API Errors: Any issues from the Evolution API (such as invalid instance name or contact) will be passed through as error messages.