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 update an existing quick reply message associated with a WhatsApp number. Quick replies are predefined shortcut messages that can be sent quickly in conversations, improving response efficiency and consistency.
Typical use cases include:
- Customer support teams updating canned responses for common questions.
- Marketing teams managing standardized promotional messages.
- Automating updates of quick replies when content or permissions change.
For example, you might update a quick reply shortcut "hours" to send the latest business hours message or attach a new media file like a product brochure.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) where the quick reply belongs. |
| Shortcut | Shortcut keyword for the quick reply (2-25 characters). |
| Message | Message content for the quick reply (4-6000 characters). |
| Permission | Access permission for the quick reply. Options: Public, Read-only, Private. |
| Include Media File | Whether to include a media file with the quick reply (boolean). |
| File ID | ID of the previously uploaded media file to attach (required if including a media file). |
| Keywords | Optional keywords for the quick reply (up to 3, alphanumeric only). |
| Quick Reply ID | ID of the quick reply to update (24 character hex value). |
Output
The node outputs JSON data representing the updated quick reply object as returned by the Wassenger API. This typically includes fields such as the quick reply's ID, shortcut, message content, permissions, attached media file info (if any), and keywords.
If a media file is included, the output reflects the association but does not output binary data directly.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and properly configured.
- The WhatsApp number (device) and media files must already exist in the Wassenger system.
- The node uses internal methods to load options for devices and files dynamically.
Troubleshooting
Common issues:
- Invalid or missing Quick Reply ID will cause update failure.
- Including a media file without specifying a valid File ID will result in errors.
- Permissions set incorrectly may restrict access unexpectedly.
- Shortcut length outside 2-25 characters or message length outside 4-6000 characters will likely cause validation errors.
Error messages:
- "Quick Reply ID is required" — Ensure the ID field is filled with a valid 24-character hex string.
- "File ID is required when including media" — Provide a valid file ID if the media inclusion option is enabled.
- API authentication errors — Verify the API key credential is correctly configured.
- Validation errors from the API about shortcut or message length — Adjust input values accordingly.
Links and References
- Wassenger Official API Documentation
- WhatsApp Quick Replies Concept
- n8n Documentation on Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/