Overview
This node sends voice notifications via the IVRAPI service. It allows users to create and dispatch automated voice messages to multiple phone numbers, specifying details such as the message content, caller ID, retry attempts, and text-to-speech (TTS) voice. This is useful for scenarios like alerting customers or employees, delivering reminders, or broadcasting announcements.
Practical examples:
- Sending appointment reminders to clients with a personalized voice message.
- Broadcasting emergency alerts to a list of phone numbers.
- Notifying team members about system outages or important updates.
Properties
| Name | Meaning |
|---|---|
| Notification Name | The name assigned to this voice notification for identification purposes. |
| Prompt Text | The text message that will be converted to speech and played in the voice notification. |
| CLIP (Caller ID) | The phone number displayed as the caller ID when the notification call is received. |
| Retries | Number of times the system will retry calling if the initial attempt fails. |
| Retries Delay/ | Delay in minutes between retry attempts. |
| TTS Voice | Google Text-to-Speech voice used to read the prompt text. Options include: |
| - Polish - Male (Wavenet-B) | |
| - Polish - Female (Wavenet-A) | |
| - English - Male (Wavenet-D) | |
| - English - Female (Wavenet-C) | |
| Recipients | List of recipients to receive the voice notification. Each recipient requires a phone number. |
Output
The node outputs a JSON array containing the response from the IVRAPI service after sending the voice notification request. The structure reflects the API's response, typically including details about the created announcement or any errors encountered.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for the IVRAPI service to authenticate requests.
- Makes HTTP POST requests to
https://api.ivrapi.com/api/announcements. - The node expects proper configuration of the API key credential within n8n.
Troubleshooting
- Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect phone number formats may result in failed calls.
- Exceeding rate limits or quota on the IVRAPI service can cause request rejections.
- Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify credential setup.
- Validation errors from the API may point to missing required fields or improperly formatted input.
- Network or timeout errors suggest connectivity issues; check network access and API availability.