Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node interacts with the Wassenger WhatsApp API to retrieve quick replies associated with a specified WhatsApp number. Quick replies are predefined message templates that can be used to respond rapidly in WhatsApp conversations, improving efficiency and consistency in customer communication.
Common scenarios for this node include:
- Fetching available quick replies to display or manage them within an automation workflow.
- Filtering quick replies based on scope, permissions, or creator agents to tailor responses according to business needs.
- Paginating through large sets of quick replies when managing extensive catalogs.
Practical example:
- A customer support automation fetches all public quick replies synced with the WhatsApp Business account to present options to agents or trigger automated responses.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number from which to retrieve quick replies. |
| Filters | Collection of filters to narrow down the quick replies returned: |
| - Scope | Filter quick replies by definition scope; options: "WhatsApp Business Synced" or "Chat Created". |
| - Permissions | Filter quick replies by permission level; options: "Public", "Read-only", "Private". |
| - Agents | Filter quick replies created by specific agent IDs (multiple values allowed). |
| - Results Page Size | Maximum number of results per page (pagination control). |
| - Page Number | Page number to retrieve, starting from 0 (pagination control). |
Output
The node outputs an array of JSON objects representing the quick replies retrieved from the Wassenger API. Each object contains details about a quick reply such as its content, scope, permissions, creator information, and other metadata defined by the API.
If binary data were involved (e.g., media attachments), it would be included in the binary output field, but this operation focuses on retrieving textual quick replies only.
Dependencies
- Requires an active connection to the Wassenger WhatsApp API via an API key credential configured in n8n.
- The node depends on the Wassenger API's availability and correct configuration of the WhatsApp number (device) to access quick replies.
- Pagination parameters require proper handling to navigate through multiple pages of results.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp number ID will result in errors or empty results.
- Incorrect API key or expired credentials will cause authentication failures.
- Using unsupported filter values may lead to no results or API errors.
- Pagination parameters out of range might return empty pages.
Error messages and resolutions:
- Authentication failed: Verify the API key credential is correctly set up and has necessary permissions.
- Resource not found or invalid device ID: Confirm the WhatsApp number ID exists and is accessible.
- Invalid filter parameter: Check filter values against allowed options and ensure correct formatting.
- API rate limits exceeded: Implement retry logic or reduce request frequency.
Links and References
- Wassenger API Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general node usage and credential setup)