Overview
This node allows sending WhatsApp messages through the WASolution API. It is designed to facilitate automated communication by sending text messages and optionally attaching files to specified WhatsApp numbers. Common use cases include customer support notifications, marketing campaigns, appointment reminders, or any scenario where automated WhatsApp messaging is beneficial.
For example, a business could use this node to send order confirmations with an attached invoice PDF, or a service provider might send appointment reminders with a link to a calendar invite.
Properties
| Name | Meaning |
|---|---|
| To (WhatsApp Number) | The recipient's WhatsApp number in international format (e.g., 60123456789). |
| Message | The text message content to be sent to the recipient. |
| File (Optional) | An optional URL of a file to send as an attachment along with the message. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each object contains the response from the WASolution API after attempting to send the message. If a file URL was provided, it is included in the request but not separately outputted.
If the node encounters an error for a particular item and "Continue On Fail" is enabled, the output for that item will contain an error field with the error message.
Dependencies
- Requires an API key credential for authenticating with the WASolution API.
- The node sends HTTP POST requests to
https://wasolution.getlifeeasy.com/api/create-message. - No additional environment variables are needed beyond the API credentials configured in n8n.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted WhatsApp numbers may result in message delivery errors.
- Providing an invalid or inaccessible file URL may cause the API to reject the attachment.
- Error messages:
- Errors returned by the WASolution API are captured and thrown as node errors unless "Continue On Fail" is enabled.
- Typical error messages might relate to authentication failure, invalid parameters, or network issues.
- Resolution tips:
- Verify API credentials are correctly set up.
- Ensure phone numbers follow the required format without extra characters.
- Confirm that file URLs are publicly accessible and valid.
Links and References
- WASolution API Documentation (assumed, please verify)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/