Actions76
- Chat Actions
- Contact Actions
- Profile Actions
- LID Actions
- File Actions
- Message Actions
- Group Actions
- Create
- List
- Get
- Delete
- Join
- Get Join Info
- Leave
- Get Picture
- Set Picture
- Delete Picture
- Update Subject
- Update Description
- Get Security Info Admin Only
- Set Security Info Admin Only
- Get Security Messages Admin Only
- Set Security Messages Admin Only
- Get Participants
- Add Participant
- Remove Participant
- Promote Admin
- Demote Admin
- Status Actions
- Channel Actions
- Poll Actions
Overview
The node enables sending voice messages through the Wappfy API, which interacts with WhatsApp. It allows users to send voice media files either by providing a URL or base64-encoded data. This is useful for automating voice message delivery in WhatsApp chats, such as sending recorded announcements, reminders, or personalized audio messages.
Practical examples:
- Sending a voice reminder to a customer about an appointment.
- Broadcasting a voice announcement to a group chat.
- Delivering personalized voice greetings automatically.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The identifier of the WhatsApp chat to send the voice message to (e.g., 123456789@c.us). |
| Media Source | The source type of the voice file: either a direct URL (URL) or base64 encoded data (Base64). |
| File URL | The URL of the voice file to send (required if Media Source is URL). |
| Base64 Data | The base64 encoded string of the voice file (required if Media Source is Base64). |
| File Name | The name of the voice file (used when Media Source is Base64, default is "file"). |
| MIME Type | The MIME type of the voice file (e.g., audio/mpeg, required). |
Output
The node outputs JSON data representing the response from the Wappfy API after attempting to send the voice message. The structure typically includes details about the sent message or any error information.
If multiple input items are processed, the output is an array of JSON objects corresponding to each item.
No binary data output is produced by this operation.
Dependencies
Requires an active Wappfy API account and valid credentials including:
- Base URL of the Wappfy API.
- Instance name identifying the WhatsApp session.
- An API key credential for authentication.
The node makes HTTP POST requests to the Wappfy API endpoints to send voice messages.
Proper configuration of the Wappfy API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Chat ID will cause the API to reject the request.
- Incorrect MIME type or unsupported audio format may result in failure to send the voice message.
- Providing both URL and base64 data incorrectly or omitting required fields leads to errors.
- Network or authentication failures due to invalid API key or instance name.
Error messages:
- Errors returned from the API will be included in the node output under an
errorfield if "Continue On Fail" is enabled. - Typical errors include "Invalid chat ID", "Unsupported media type", or "Authentication failed".
- Errors returned from the API will be included in the node output under an
Resolution tips:
- Verify the chat ID format matches WhatsApp requirements.
- Ensure the MIME type corresponds exactly to the audio file format.
- Confirm that the API key and instance name are correctly set in credentials.
- Check network connectivity and API endpoint accessibility.
Links and References
- Wappfy API Documentation (for detailed API usage and supported media types)
- WhatsApp chat ID formats: direct chats end with
@c.us, groups with@g.us. - MIME Types reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types