IVRAPI SMS Send icon

IVRAPI SMS Send

Send SMS message via IVRAPI
Join our community

Overview

This node sends SMS messages via the IVRAPI service. It is useful for automating text message notifications, alerts, or marketing campaigns directly from n8n workflows. For example, you can use it to notify customers about order status updates, send appointment reminders, or deliver verification codes.

The node requires a registered sender ID (an alphanumeric header or phone number) and validates recipient phone numbers to ensure they meet specific format rules before sending the SMS through the IVRAPI HTTP API.

Properties

Name Meaning
Sender (From, Virtual Number) Name or ID The sender ID used as the SMS originator. Must be a registered alphanumeric header or phone number (up to 11 characters) allowed by IVRAPI. You can select from a loaded list of senders or specify an ID using an expression.
Recipient Phone Number The destination phone number in a strict 9-digit format. Numbers starting with prefixes 30, 40, 70, or 80 are not allowed.
Message The text content of the SMS message. Depending on character encoding, the message may be split into multiple SMS parts (160 characters max for GSM 7-bit encoding, or 67 characters if extended characters like Polish letters are included).

Output

The node outputs JSON data containing the response from the IVRAPI SMS sending endpoint for each input item. This typically includes details about the sent message such as status, message ID, or error information if the request failed.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for IVRAPI to authenticate requests.
  • Makes HTTP POST requests to https://api.ivrapi.com/api/smses to send SMS messages.
  • Uses an HTTP GET request to https://api.ivrapi.com/api/smses/senders to load available sender IDs for selection.

Troubleshooting

  • Missing or invalid API key: The node will throw an error if the API key credential is missing or invalid. Ensure the API key is correctly configured in the node credentials.
  • Invalid sender ID length: Sender ID must be between 1 and 11 characters. If outside this range, the node throws an error.
  • Invalid recipient phone number format: The recipient number must be exactly 9 digits and cannot start with 30, 40, 70, or 80. Violations cause errors.
  • Empty message: Sending an empty message is not allowed and results in an error.
  • Failed to load senders: If the node cannot retrieve the list of registered senders due to network or authentication issues, it will throw an error indicating failure to load SMS senders.
  • API request failures: Any HTTP errors during sending will be surfaced as node operation errors with relevant messages.

Links and References

Discussion