Actions5
- Message Actions
- Chat Actions
Overview
This node operation retrieves all messages from a specified group chat in WhatsApp Outreach by Boost.space. It is useful for scenarios where you want to analyze, archive, or process the conversation history of a particular group chat. For example, you might use it to monitor customer support group chats, extract discussion logs for compliance, or aggregate messages for sentiment analysis.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the group chat from which to fetch messages. |
| Limit | Maximum number of messages to return in one execution (minimum 1). |
| After | Filter to include only messages created after this datetime (exclusive). |
| Before | Filter to include only messages created before this datetime (exclusive). |
Output
The output is a JSON array where each element represents a message retrieved from the specified group chat. Each message object typically contains details such as message content, sender information, timestamps, and any metadata provided by the WhatsApp Outreach API.
If the node supports binary data output (not explicitly shown here), it would represent attachments or media within messages, but this operation primarily returns JSON message data.
Dependencies
- Requires an API key credential for authenticating requests to the WhatsApp Outreach by Boost.space service.
- The node makes HTTP POST requests to the service's endpoint at
https://rnmqfhwsqojadktbxnrf.supabase.co/functions/v1/getAllMessagesInAGroup. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Chat ID will result in no messages returned or an error.
- Exceeding the limit parameter or providing invalid date filters may cause unexpected results or errors.
- Network or authentication failures can prevent successful API calls.
Error messages:
- Authentication errors indicate problems with the API key credential; verify and update credentials.
- "Chat not found" or similar errors suggest the Chat ID does not exist or is inaccessible.
- Rate limiting or quota exceeded errors require checking API usage limits.
Links and References
- WhatsApp Outreach by Boost.space Documentation (example placeholder link)
- n8n HTTP Request Node Documentation (for understanding requestWithAuthentication helper)