Actions59
- 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
- Entrar en El Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
Overview
This node, named "Wazend API," is designed to interact with the Wazend API, a service likely related to messaging or chat functionalities. Specifically, for the Resource "Chat" and Operation "Leer Mensajes" (Read Messages), it allows users to retrieve specific messages from a chat instance by specifying details such as the instance name, contact number, message ID, and whether the message was sent by the instance itself.
Common scenarios where this node would be beneficial include:
- Fetching historical chat messages for auditing or record-keeping.
- Retrieving message details for customer support follow-up.
- Integrating chat data into other workflows or databases for analysis.
Practical example: A user wants to fetch a particular message sent or received in a WhatsApp-like chat system by providing the instance name, the contact's phone number, and the unique message ID.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the chat instance to connect to. This identifies which chat environment to use. |
| Contacto | The contact's phone number involved in the chat conversation. |
| ID Del Mensaje | The unique identifier of the message to be read. |
| El Mensaje Es Mío | Boolean flag indicating if the message was sent by the instance itself (true) or not (false). |
Output
The node outputs an array of JSON objects representing the retrieved message(s). Each object contains the message details fetched from the Wazend API based on the input parameters.
If the node supports binary data output (not explicitly shown in the provided code), it would typically represent media attachments or files associated with the message. However, no explicit binary output handling is visible in the given source.
Dependencies
- Requires an active connection to the Wazend API endpoint at
https://docs.wazend.net/wazend. - Needs an API authentication token or key configured in the node credentials (referred generically as "an API key credential").
- Relies on n8n's internal helper methods for parameter retrieval and returning JSON arrays.
Troubleshooting
- Unsupported Operation Error: If the operation specified is not supported for the chosen resource, the node throws an error stating the operation is not supported. Ensure that the operation name matches exactly one of the implemented operations.
- Missing Required Parameters: Since all properties are required, missing any of them will likely cause the node to fail or return incomplete data. Double-check that all required fields are filled.
- API Connectivity Issues: Network problems or incorrect API credentials can prevent successful communication with the Wazend API. Verify network access and credential validity.
- Incorrect Message ID or Contact Number: Providing invalid or non-existent message IDs or contact numbers may result in empty responses or errors. Confirm these values before execution.
Links and References
- Wazend API Documentation (official API docs URL as per baseURL)
- n8n Documentation on Creating Custom Nodes