Send
AI-generatedOverview
This node allows you to send WhatsApp messages to your own WhatsApp account using the Whin API. It is designed for scenarios where you want to automate sending messages to yourself, such as reminders, notifications, or testing message formats before sending them to others.
Practical examples include:
- Sending automated alerts or status updates directly to your WhatsApp.
- Testing WhatsApp message payloads without involving other recipients.
- Quickly sending notes or information from workflows to your personal WhatsApp.
Properties
| Name | Meaning |
|---|---|
| Token Override | A string token that overrides the default API authentication token for this specific item. |
| Content Payload | The WhatsApp message content as a JSON object (e.g., {"type":"text","text":{"body":"hi"}}). Do not include envelope fields like messaging product, recipient, or context. Supported types: text, template, image, audio, video, document, sticker, contacts, location, interactive, reaction. |
| Request Timeout (ms) | Maximum time in milliseconds to wait for the API request before aborting it. Minimum allowed is 1000 ms. |
Output
The node outputs an array of JSON objects corresponding to each input item. Each output JSON contains the response from the Whin API after attempting to send the WhatsApp message. If the request fails and "Continue On Fail" is enabled, the output will contain an error object with fields such as message, statusCode, and code.
The node does not output binary data.
Dependencies
- Requires an API key credential for the Whin service to authenticate requests.
- The node sends HTTP POST requests to the Whin API endpoint at
https://api.whin.app/n8n. - Proper network access to the Whin API is necessary.
- The user can override the token per item if needed.
Troubleshooting
- Missing token error: If neither credentials nor a token override is provided, the node throws "Missing token. Provide credentials or a Token Override." Ensure you have configured the API key credential or provide a token override.
- Invalid JSON in Content Payload: If the payload is provided as a string but is not valid JSON, the node throws "Content Payload must be valid JSON when provided as a string." Make sure the JSON syntax is correct.
- Incorrect payload structure: The payload must be a JSON object and include a valid
typefield matching one of the supported message types. Otherwise, the node throws an error indicating the missing or invalid type. - Timeouts: If the request takes longer than the specified timeout, it will abort. Increase the "Request Timeout (ms)" value if you experience frequent timeouts.
- API errors: Errors returned by the Whin API are captured and included in the output if "Continue On Fail" is enabled; otherwise, they cause the node to fail.
Links and References
- Whin API Documentation (for detailed message payload formats and API usage)
- WhatsApp Business API Message Types (to understand supported message types and structures)
