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
The node interacts with the Evolution API, specifically supporting a "Chat" resource operation called "Enviar Presencia" (Send Presence). This operation allows sending a presence status such as "typing" or "recording" to a specified contact in a chat instance. It is useful in scenarios where you want to indicate to another user that you are actively typing or recording a message, enhancing real-time communication feedback.
Practical examples include:
- Showing a "typing..." indicator while composing a message in a chat application.
- Indicating "recording..." when capturing a voice note before sending.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the chat instance where the presence will be sent. |
| Contacto | The contact's number or identifier to whom the presence status will be sent. |
| Presencia | The type of presence to send; options are: "Escribiendo..." (composing) or "Grabando..." (recording). |
| Retraso | The delay time in milliseconds for how long the presence status remains active. |
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 confirms whether the presence was successfully sent or if there was an error.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor requests. - Proper configuration of the API authentication within n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials can cause authentication failures.
- Incorrect contact identifiers may lead to errors or no presence being sent.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Operação não suportada."indicates that the requested operation is not supported by the node, possibly due to a typo or unsupported combination of resource and operation.- API errors returned from the Evolution API should be checked for details on invalid parameters or rate limits.
Resolutions:
- Verify API credentials and permissions.
- Ensure the contact number format matches expected standards.
- Check network access and retry if transient errors occur.
Links and References
- Evolution API Documentation (official API reference)