IVRAPI SMS Send (BETA) icon

IVRAPI SMS Send (BETA)

Send SMS message via IVRAPI
Join our community

Overview

This node sends SMS messages via the IVRAPI service. It is designed to allow users to send text messages programmatically by specifying a registered sender ID, recipient phone number, and message content. This node is useful in scenarios such as automated notifications, alerts, marketing campaigns, or any workflow requiring SMS communication.

For example, you could use this node to:

  • Notify customers about order status updates.
  • Send appointment reminders.
  • Deliver verification codes for two-factor authentication.

Properties

Name Meaning
Sender (From, Virtual Number) Name or ID The sender identifier used for the SMS. It must be a registered alphanumeric header or phone number (up to 11 characters) allowed by IVRAPI. You can select from a list of registered senders or specify an ID using an expression. To register new sender names, contact the service provider.
Recipient Phone Number The recipient's 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 the characters used, the message may be split into multiple SMS parts (160 characters per SMS in GSM 7-bit encoding, or 67 characters if extended characters like Polish letters are included).

Output

The node outputs an array of JSON objects, each representing the response from the IVRAPI SMS sending endpoint for each input item processed. The JSON output contains details returned by the API about the sent SMS message, such as status or message ID.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for IVRAPI to authenticate requests.
  • Makes HTTP requests to the IVRAPI endpoints:
    • To fetch available SMS senders: GET https://api.ivrapi.com/api/smses/senders
    • To send SMS messages: POST https://api.ivrapi.com/api/smses
  • The node expects the IVRAPI API key to be configured in n8n credentials.

Troubleshooting

  • Missing API Key: If the API key is not set or invalid, the node will throw an error indicating missing credentials. Ensure the API key is correctly configured in n8n.
  • Invalid Sender ID: The sender ID must be between 1 and 11 characters and registered with IVRAPI. Using an unregistered or incorrectly formatted sender will cause errors.
  • Invalid Recipient Number: The recipient phone number must be exactly 9 digits and cannot start with 30, 40, 70, or 80. Violating these rules results in validation errors.
  • Empty Message: Sending an empty message is not allowed and will cause an error.
  • HTTP Request Failures: Network issues or incorrect API keys can cause HTTP request failures when fetching senders or sending messages. Check network connectivity and API key validity.

Links and References

Discussion