Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node provides an interface to interact with the Evolution API, specifically supporting chat-related operations. The "Send Presence" operation under the "Chat" resource allows users to send presence updates such as "typing" or "recording" status to a specified contact in a chat application. This is useful for real-time communication scenarios where indicating user activity (like typing or recording a voice message) enhances the conversational experience.
Practical examples include:
- Indicating to a chat recipient that you are currently typing a message.
- Showing that you are recording a voice note before sending it.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The contact number or identifier to whom the presence update will be sent. |
| Presence | The type of presence status to send. Options: "Typing..." (composing), "Recording..." (recording). |
| Delay | Duration in milliseconds for which the presence status remains active before clearing. |
Output
The node outputs a JSON array containing the result of the presence update operation. The exact structure depends on the Evolution API response but generally confirms whether the presence was successfully sent. There is no indication of binary data output.
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 beyond the Evolution API service.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the "resource" is set to "chat-api" and the "operation" is "send-presence".
- Invalid contact or instance name: Ensure the contact identifier and instance name are correctly provided and correspond to valid entries in the Evolution API.
- Presence not updating: Check network connectivity and API credentials; also confirm the delay value is reasonable (e.g., not zero).
- API authentication errors: Verify that the API key or authentication token is correctly configured in n8n credentials.
Links and References
- Evolution API Documentation: https://doc.evolution-api.com/api-reference
- n8n Node Development Guide: https://docs.n8n.io/integrations/creating-nodes/