Kavenegar SMS

Send an SMS through Kavenegar API

Actions3

Overview

This node integrates with the Kavenegar API to send SMS messages, verify OTP tokens, or perform Text-to-Speech (TTS) calls. It is useful in scenarios where automated communication via SMS or voice calls is needed, such as sending notifications, verifying user identity through OTPs, or delivering voice messages.

For the TTS operation specifically, the node converts a text message into a voice call sent to a specified phone number (the receptor). This can be used for alerting users with spoken messages, reminders, or any scenario where a voice call is preferred over text.

Properties

Name	Meaning
Receptor	The phone number that will receive the TTS voice call.
TTS Message	The text content that will be converted into speech and delivered via the voice call.

Output

The output JSON contains the following fields:

response: The raw response from the Kavenegar API for the TTS request.
tts: A boolean flag set to true indicating the TTS operation was performed.
receptor: The phone number that received the TTS call.
ttsMessage: The original text message sent for TTS conversion.

No binary data is output by this node.

Dependencies

Requires an API key credential for the Kavenegar service.
The node makes HTTP GET requests to the Kavenegar API endpoints.
Proper network access to the Kavenegar API is necessary.
The API key must have permissions to use the TTS call feature.

Troubleshooting

Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect receptor phone number format may result in API errors or failed calls.
- Network connectivity problems can prevent successful API requests.
Error messages:
- "No credentials got returned!": Indicates the API key credential is not configured or accessible.
- API error responses from Kavenegar will be included in the response field; check these for details.
Resolutions:
- Ensure the API key credential is correctly set up in n8n.
- Validate the receptor phone number format according to Kavenegar's requirements.
- Verify network connectivity and firewall settings allow outbound requests to the Kavenegar API.