Overview
This node sends voice notifications via the IVRAPI service. It allows users to create a notification action that plays a text-to-speech (TTS) message during a call to specified recipients in Poland. The node supports retry attempts with configurable delays and lets users select the outbound caller ID (virtual number) and TTS voice.
Common scenarios include:
- Automated alerts or reminders sent by phone.
- Notifications for appointments, deliveries, or emergencies.
- Customer engagement through personalized voice messages.
Example: Sending a reminder call to multiple Polish phone numbers with a custom message and a selected TTS voice.
Properties
| Name | Meaning |
|---|---|
| Notification Name | Name of the notification action; must be at least 4 characters long. |
| Prompt Text | The text content that will be converted to speech and played during the call. |
| Outbound Caller ID / Virtual Number | The Polish 9-digit caller ID number used as the outbound number for the call. Must not start with 30, 40, 70, or 80. Can be selected from available virtual numbers or specified via expression. |
| Retries | Number of retry attempts if the call fails; integer between 0 and 10. |
| Retries Delay (minutes) | Delay between retry attempts in minutes; integer between 1 and 60. |
| TTS Voice | Selects the voice model for text-to-speech synthesis. Options include various Polish, English, and German voices with different characteristics (e.g., natural, expressive, warm). "None" disables TTS voice selection. |
| Recipients | List of recipients to call. Each recipient requires a Polish 9-digit phone number (without country code), which cannot start with 30, 40, 70, or 80. Multiple recipients can be added. |
Output
The node outputs a JSON array containing the response from the IVRAPI announcements API after sending the voice notification request. The structure includes details about the created announcement but is not explicitly detailed in the source code.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for the IVRAPI service.
- Uses the IVRAPI REST API endpoints:
GET https://api.ivrapi.com/api/vnumbersto load available virtual numbers.POST https://api.ivrapi.com/api/announcementsto send the voice notification.
- The node expects valid credentials configured in n8n for authentication.
Troubleshooting
- Invalid Notification Name: If the name is shorter than 4 characters, the node throws an error. Ensure the name meets the minimum length requirement.
- Invalid Caller ID (CLIP): The outbound caller ID must be exactly 9 digits and cannot start with 30, 40, 70, or 80. Check the number format and restrictions.
- Invalid Phone Numbers: Recipient phone numbers must be 9 digits and follow the same prefix restrictions as the caller ID.
- Retries and Delay Limits: Retries must be between 0 and 10; delay must be between 1 and 60 minutes. Values outside these ranges cause errors.
- TTS Voice Format: The selected TTS voice must match allowed patterns (Wavenet, Chirp, Chirp3 models). Invalid formats cause errors.
- Missing API Key: If the IVRAPI API key is missing or invalid, loading virtual numbers or sending notifications will fail.
- No Virtual Numbers Available: If no virtual numbers are registered for the account, the node will throw an error when trying to load them.
To resolve errors, verify all input fields against the above constraints and ensure proper API credentials are set up.
Links and References
- IVRAPI Voice Notification Documentation
- n8n Expressions Documentation (for specifying dynamic values)