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
This node enables sending audio messages through WhatsApp using the Wappfy API. It supports sending audio files either by providing a direct URL or by supplying Base64-encoded data. This functionality is useful for automating voice message delivery in customer support, marketing campaigns, or personal communication workflows.
For example, you can use this node to send recorded audio announcements to a group chat or deliver personalized voice notes to individual contacts automatically.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The identifier of the chat where the audio will be sent (e.g., 123456789@c.us for direct chats or 123456789@g.us for groups). |
| Media Source | The source type of the audio file: either a direct URL (URL) or Base64 encoded data (Base64). |
| File URL | The URL of the audio file to send (required if Media Source is URL). |
| Base64 Data | The Base64 encoded string of the audio file (required if Media Source is Base64). |
| File Name | The name of the audio file when sending Base64 data (default is "file"). |
| MIME Type | The MIME type of the audio file (e.g., audio/mpeg, audio/ogg). |
| Caption | Optional caption text to accompany the audio message (only applicable when sending via URL or Base64). |
Output
The node outputs JSON data representing the response from the Wappfy API after attempting to send the audio message. The structure typically includes details about the sent message such as message ID, status, and any metadata returned by the API.
If multiple items are processed, the output is an array of such JSON objects, one per input item.
The node does not output binary data directly; it only handles sending audio media via the API.
Dependencies
Requires an active Wappfy API account with 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 audio messages.
Proper configuration of these credentials in n8n is necessary for successful operation.
Troubleshooting
Common Issues:
- Incorrect or missing Chat ID format may cause message sending failures.
- Providing an invalid or inaccessible File URL will result in errors.
- Incorrect MIME type may cause the media to be rejected or not played properly.
- If using Base64 data, ensure the encoding is correct and complete.
Error Messages:
- Authentication errors indicate issues with the API key or instance name.
- HTTP 400 errors often mean required parameters are missing or malformed.
- Network errors suggest connectivity problems to the Wappfy API endpoint.
Resolutions:
- Verify that the Chat ID matches the expected WhatsApp format.
- Confirm the media URL is publicly accessible or the Base64 data is valid.
- Double-check MIME type correctness according to the audio file format.
- Ensure API credentials are correctly set up and have sufficient permissions.
Links and References
- Wappfy API Documentation (for detailed API usage and media requirements)
- WhatsApp Chat ID Format Explanation
- MIME Types Reference