Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Chat resource and the Send Presence operation, it sends a presence status (such as "typing" or "recording") to a specified contact in a chat instance. This is useful in scenarios where you want to simulate or indicate user activity in a chat application, such as showing that a user is currently typing a message or recording audio.
Practical examples include:
- Indicating to a chat recipient that you are composing a message.
- Showing that you are recording a voice note before sending it.
- Temporarily displaying presence status for a defined delay period.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the chat instance where the presence will be sent. |
| Contato | The contact number (chat ID) to whom the presence status will be sent. |
| Presença | The type of presence to send. Options: "Escrevendo..." (composing), "Gravando..." (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 sending operation. The exact structure depends on the Evolution API response but generally includes confirmation or status information about the presence update.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate with the Evolution API.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor API requests. - Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
- Operation not supported error: If the selected operation or resource is not implemented, the node throws an error indicating unsupported operation. Ensure the correct resource ("chat-api") and operation ("send-presence") are selected.
- Invalid or missing parameters: Required fields like instance name, contact number, presence type, and delay must be provided; otherwise, the API call may fail.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or API errors: Check network connectivity and API availability if requests fail.
Links and References
- Evolution API Documentation (official API reference)