Actions29
- Sessions Actions
- Chats Actions
- Contacts Actions
- Groups Actions
- Messages Actions
Overview
This node integrates with a WhatsApp HTTP API to send messages programmatically. It is designed for scenarios where automated WhatsApp messaging is needed, such as customer support notifications, marketing campaigns, or alert systems. For example, a business can use this node to send order confirmations or appointment reminders directly to customers' WhatsApp accounts.
Properties
| Name | Meaning |
|---|---|
| Phone | The session ID representing the WhatsApp phone number or account used to send the message. |
| To | The recipient's WhatsApp ID (JID) to whom the message will be sent. |
| Type | The type of the recipient identifier; typically "number". |
| Message | The content of the message in JSON format, supporting text and mentions (e.g., tagged users). |
Output
The node outputs JSON data representing the response from the WhatsApp HTTP API after sending the message. This typically includes confirmation details such as message status, IDs, timestamps, or error information if the message failed to send. The node does not output binary data.
Dependencies
- Requires connection to a WhatsApp HTTP API service.
- Needs an API URL and authentication credentials configured in n8n (such as an API key or token).
- The node uses standard HTTP headers for JSON communication (
Accept: application/json,Content-Type: application/json).
Troubleshooting
Common issues:
- Invalid or missing session ID ("Phone") may cause authentication failures.
- Incorrect recipient JID format can result in message delivery errors.
- Malformed JSON in the "Message" property can cause request parsing errors.
- Network or API endpoint misconfiguration leads to connection errors.
Error messages:
- Authentication errors usually indicate invalid or expired credentials; verify API keys and session IDs.
- Validation errors on the message payload suggest checking the JSON structure and required fields.
- Timeout or connection refused errors imply network issues or incorrect API base URL configuration.
Links and References
- WhatsApp Business API Documentation
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)