Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node integrates with the Evolution API to perform various chat-related operations. Specifically, for the "Chat" resource and the "Mark as Unread" operation, it allows users to mark a specific message in a chat as unread. This can be useful in scenarios where you want to flag messages for follow-up or indicate that a message requires attention later.
Practical examples include:
- Automatically marking incoming messages as unread if they meet certain criteria.
- Managing message states programmatically within workflows to improve team collaboration.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to the Evolution API. |
| Contato | The contact number associated with the chat where the message is located. |
| ID Da Mensagem | The unique identifier of the last message to be marked as unread. |
| Mensagem É Minha | Boolean indicating whether the message was sent by the instance (true) or received (false). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to mark the specified message as unread. The exact structure depends on the API's response but typically includes confirmation of the action or details about the updated message state.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API base URL and headers to be configured internally.
- No additional external dependencies are required beyond the API access.
Troubleshooting
Common Issues:
- Incorrect or missing instance name, contact number, or message ID will cause the operation to fail.
- If the message ID does not exist or does not belong to the specified contact, the API may return an error.
- Network or authentication errors if the API key is invalid or expired.
Error Messages:
"Operação não suportada."indicates that the requested operation is not supported for the given resource.- API errors related to invalid parameters should be resolved by verifying input values.
- Authentication errors require checking the API key credentials.
Links and References
- Evolution API Documentation (official API reference)