Actions76
- Message Actions
- Chat Actions
- Contact 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
- Profile Actions
- LID Actions
- File Actions
Overview
The node enables sending audio messages through WhatsApp using the Wappfy API. It supports sending audio files either by providing a direct URL or base64-encoded data, along with specifying the MIME type and optional captions. This 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 a recorded podcast episode link or a voice note directly to a WhatsApp chat by specifying the chat ID and the audio file source.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The identifier of the WhatsApp chat to send the audio to (e.g., 123456789@c.us for direct or 123456789@g.us for group). |
| 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 (used when Media Source is Base64, default is "file"). |
| MIME Type | The MIME type of the audio file (e.g., audio/mpeg, required). |
| Caption | Optional caption text to accompany the audio message. |
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, or error information if the request failed.
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 sends audio media via the API.
Dependencies
- Requires access to the Wappfy API service.
- Requires configuration of credentials containing:
- The base URL of the Wappfy API.
- An instance name identifying the WhatsApp session.
- An API key credential for authentication.
- The node makes HTTP requests to the Wappfy API endpoints.
Troubleshooting
- Invalid Chat ID: Ensure the chat ID is correctly formatted (e.g., ends with
@c.usfor individual chats or@g.usfor groups). - Incorrect MIME Type: The MIME type must match the actual audio file format; otherwise, the API may reject the file.
- Missing Required Fields: If
Media SourceisURL,File URLmust be provided; ifBase64, thenBase64 Dataand optionallyFile Namemust be set. - API Authentication Errors: Verify that the API key credential is valid and has proper permissions.
- Network Issues: Check connectivity to the Wappfy API base URL.
- Large Files: Sending very large audio files might cause timeouts or failures; consider hosting files on reliable servers or compressing them.
Common error messages usually come from the API and indicate missing parameters, invalid formats, or authentication failures. Review the error message returned in the node's output JSON for guidance.
Links and References
- Wappfy API Documentation (general reference for API endpoints)
- WhatsApp chat ID format conventions: Use
<number>@c.usfor individuals and<number>@g.usfor groups. - MIME types for audio files: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types