Actions12
- Sesiones Actions
- Mensajería Actions
- Chats y Mensajes Actions
Overview
This node, named "Expertos en IA," provides integration with the secure API of Expertos en IA to interact with messaging, chats, and session resources. Specifically, for the "Chats y Mensajes" resource and the "Obtener Mensajes de Chat" operation, it allows users to retrieve messages from a specified chat.
Typical use cases include:
- Fetching recent messages from a chat for analysis or processing.
- Archiving chat conversations.
- Triggering workflows based on chat message content.
- Monitoring chat activity in real-time or periodically.
For example, you could use this node to get the last 100 messages from a customer support chat to analyze customer inquiries or automate responses.
Properties
| Name | Meaning |
|---|---|
| ID del Chat | The unique identifier of the chat from which to retrieve messages (e.g., NUMERO@c.us). |
| Límite de Mensajes | Maximum number of messages to fetch from the chat (default is 100). |
Output
The node outputs an array of JSON objects, each representing a message retrieved from the specified chat. Each item in the output corresponds to one message returned by the API.
The exact structure of each message object depends on the API response but typically includes details such as message ID, sender, timestamp, message content, and any metadata related to the message.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Expertos en IA service to authenticate requests.
- Needs network access to
https://api.expertosenia.com. - The node expects the user to configure the API key credential within n8n before execution.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect chat ID format may result in no messages being returned or errors.
- Requesting too many messages (exceeding API limits) might lead to partial results or errors.
Error messages:
"Operación no válida."indicates that the requested operation is not supported or incorrectly specified.- HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) usually relate to credential issues or invalid chat IDs.
Resolutions:
- Verify that the API key credential is correctly set up and active.
- Confirm the chat ID matches the expected format used by the service.
- Adjust the message limit to a reasonable number if encountering rate limits or timeouts.