Actions11
- Message Actions
- Group Actions
- Contact Group Actions
- Instance Actions
Overview
This node allows sending WhatsApp messages through the Waapify API. It supports various message types including text, media (images, documents, videos), location, contact cards, and template messages. The node is useful for automating WhatsApp communications in workflows such as customer support, marketing campaigns, notifications, or alerts.
For the Send Media operation under the Message resource, the node sends a media file to a specified phone number with an optional caption. This is beneficial when you want to share images, videos, documents, or other media files directly via WhatsApp within an automated process.
Example use cases:
- Sending product images or brochures to customers automatically.
- Sharing event photos or videos with participants.
- Delivering invoices or receipts as PDF documents.
Properties
| Name | Meaning |
|---|---|
| Phone Number | Phone number to send the message to, including country code but without the "+" sign. |
| Message | Caption text accompanying the media file (optional). |
| Media URL | URL of the media file to be sent. |
| Filename | Filename for the document, used when sending document-type media (optional). |
Output
The node outputs JSON data representing the response from the Waapify API after attempting to send the media message. Each item corresponds to one input item processed and includes the API's response details.
If an error occurs and "Continue On Fail" is enabled, the output will include an error object with:
error: Error message string.statusCode: HTTP status code returned by the API.timestamp: ISO timestamp of the error occurrence.
The node does not output binary data; all responses are JSON objects describing the result of the API call.
Dependencies
Requires an active Waapify API account with valid credentials including:
- Base URL of the Waapify API.
- Instance ID.
- Access token for authentication.
The node uses these credentials to authenticate requests to the Waapify API endpoints.
No additional external dependencies beyond the Waapify API and n8n's HTTP request helper.
Troubleshooting
Common issues:
- Invalid or missing phone number format (must include country code, no "+" sign).
- Incorrect or expired API credentials causing authentication failures.
- Invalid media URL or inaccessible media file leading to failed uploads.
- Missing required parameters like
mediaUrlorphoneNumber.
Error messages:
- Errors returned from the Waapify API are prefixed with
Waapify API Error:followed by the API's message. - HTTP status codes indicate the type of failure (e.g., 400 for bad request, 401 for unauthorized).
- Errors returned from the Waapify API are prefixed with
Resolutions:
- Verify phone numbers follow the correct format.
- Check and update API credentials if authentication errors occur.
- Ensure media URLs are publicly accessible and correctly formatted.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.
Links and References
- Waapify API Documentation (for detailed API usage and message types)
- WhatsApp Business API Overview (general background on WhatsApp messaging)
- n8n Documentation on HTTP Request Node (underlying mechanism for API calls)