Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
This node, named "Evolution API," allows interaction with the Evolution API service. Specifically for the resource Chat and operation Marcar Como No Leído (Mark as Unread), it marks a specific chat message as unread. This is useful in scenarios where users want to flag messages they have already seen but wish to revisit later, or to reset the read status of messages programmatically.
Practical examples include:
- Automatically marking important messages as unread after processing them.
- Managing message states in customer support workflows to ensure follow-up.
- Synchronizing message read statuses between different platforms.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the instance to connect to the Evolution API. |
| Contacto | The contact number associated with the chat where the message exists. |
| ID Del Mensaje | The unique identifier of the last message to be marked as unread. |
| El Mensaje Es Mío | Boolean indicating if the message was sent by the instance itself (true/false). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to mark the message as unread. The exact structure depends on the API response but typically includes confirmation of the action or error details.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credentials within n8n is necessary.
Troubleshooting
Common Issues:
- Incorrect or missing instance name, contact number, or message ID will cause the operation to fail.
- Authentication errors if the API key credential is invalid or expired.
- Network connectivity issues preventing access to the Evolution API endpoint.
Error Messages:
"Operação não suportada."indicates that the requested operation is not supported for the given resource.- API errors returned from the Evolution API will be passed through; check the message for details such as invalid parameters or permission issues.
Resolutions:
- Verify all required properties are correctly set.
- Ensure the API key credential is valid and has necessary permissions.
- Confirm network connectivity and API endpoint availability.
Links and References
- Evolution API Documentation (official API reference)