Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node interacts with the WaAPI API to retrieve chat data. Specifically, the "Get Chats" operation fetches a list of chat instances from the service. This is useful for workflows that need to process or analyze chat conversations, such as customer support automation, chat analytics, or archiving chat histories.
For example, you might use this node to:
- Retrieve recent chat sessions for review.
- Fetch chats in batches for processing or exporting.
- Integrate chat data into other systems like CRMs or reporting tools.
Properties
| Name | Meaning |
|---|---|
| Id | The instance ID identifying the specific chat resource to query. |
| Offset | Number of items to skip before starting to collect the result set (for pagination). |
| Limit | Number of chat items to return in the response (controls page size). |
Output
The node outputs JSON data representing the retrieved chat records. Each item corresponds to a chat instance fetched from the WaAPI service. The structure typically includes chat metadata and content as provided by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the WaAPI API.
- The node sends requests to
https://waapi.app/api/v1. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an invalid or non-existent instance ID may result in empty results or errors.
- Pagination parameters (
offsetandlimit) must be valid numbers; otherwise, the API may reject the request.
Error messages:
- Authentication failures usually indicate problems with the API key setup.
- "Not Found" or similar errors suggest the specified instance ID does not exist.
- Rate limiting errors may occur if too many requests are sent in a short time; consider adding delays or reducing request frequency.
Links and References
- WaAPI Official Documentation (for detailed API usage and chat data structure)
- n8n Documentation (for general guidance on using API nodes and credentials)