Actions12
Overview
The node "Wazzap API" allows interaction with the Wazzap messaging API. Specifically, for the resource Mensagem and operation Enviar Audio, it enables sending an audio message to a specified recipient via the Wazzap platform. This is useful in scenarios where automated audio notifications, voice messages, or alerts need to be sent programmatically.
Practical examples include:
- Sending a voice alert to a customer when their order status changes.
- Broadcasting audio announcements to a group of users.
- Delivering personalized audio greetings or reminders.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Wazzap instance that will send the audio message. |
| Número Do Destinatário | The recipient's phone number or identifier to whom the audio will be sent. |
| Audio | The audio content to send, provided as a URL or base64 encoded string. |
| Opções (Delay) | Optional delay in milliseconds before the message is sent (default is 1200 ms). |
Output
The node outputs a JSON array containing the response from the Wazzap API after attempting to send the audio message. The exact structure depends on the API response but typically includes confirmation details such as message ID, status, timestamps, or error information if the sending failed.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Wazzap API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node uses the base URL
https://doc.wazzap.mx/api-referencefor API calls.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure you use valid combinations of resource and operation.
- Invalid or missing parameters: Required fields like instance name, recipient number, or audio must be correctly filled; otherwise, the API call may fail.
- API authentication errors: Make sure the API key or token credential is properly set up and has sufficient permissions.
- Network or timeout issues: Delays or connectivity problems can cause failures; verify network access to the Wazzap API endpoint.
- Audio format issues: The audio must be a valid URL or base64 string representing an audio file supported by the API.
Links and References
- Wazzap API Documentation (official API reference)
- n8n documentation on creating custom nodes