Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node interacts with the Evolution API, specifically supporting a "Chat" resource with an operation to send presence status updates. The "Enviar Presença" (Send Presence) operation allows users to notify a contact about their current chat presence state, such as "typing" or "recording". This is useful in chat applications where real-time presence indicators improve communication by showing when someone is actively composing or recording a message.
Practical examples include:
- Indicating to a chat recipient that you are typing a reply.
- Showing that you are recording a voice message before sending it.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to the Evolution API. |
| Contato | The contact number (remote JID) 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 response from the Evolution API after sending the presence update. The exact structure depends on the API's response but generally confirms whether the presence was successfully sent.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the user to configure this credential within n8n.
- No other external dependencies are explicitly required.
Troubleshooting
- Unsupported Operation Error: If the node throws an error stating the operation is not supported, verify that the "resource" and "operation" parameters are correctly set to "chat-api" and "send-presence" respectively.
- Authentication Failures: Ensure the API key credential is valid and properly configured.
- Invalid Contact Number: Sending presence to an incorrectly formatted or non-existent contact number may cause errors; verify the "Contato" field.
- Delay Misconfiguration: Setting an extremely low or high delay might affect presence visibility; use reasonable values (e.g., 1200 ms).
Links and References
- Evolution API official documentation (not provided here, but recommended to consult for detailed API behavior)
- n8n documentation on creating and using credentials and custom nodes