Overview
This node integrates with the OVH SMS API to send SMS messages. It is designed to facilitate sending text messages programmatically through OVH's SMS service, which can be useful for notifications, alerts, marketing campaigns, or any scenario requiring automated SMS delivery.
A typical use case would be sending a custom message to one or multiple phone numbers directly from an n8n workflow, such as alerting users about system status changes or sending appointment reminders.
Properties
| Name | Meaning |
|---|---|
| Service Name | The identifier of the OVH SMS service to use for sending the message (required). |
| Phone Number | The recipient's phone number in international format (e.g., +33111111111). |
| Message | The text content of the SMS message to be sent. |
Output
The node outputs the response from the OVH SMS API after attempting to send the message. The output JSON structure typically contains details about the SMS job created by OVH, such as job identifiers and status information.
If multiple items are processed, each item's output corresponds to the respective input.
No binary data is produced by this node.
Dependencies
Requires an active OVH SMS API account with valid credentials including:
- API endpoint URL
- Application key
- Application secret
- Consumer key (API authentication token)
These credentials must be configured in n8n prior to using the node.
The node uses the OVH REST API and requires network access to OVH's SMS service endpoints.
Troubleshooting
Missing Service Name: The node throws an error if the "Service Name" property is empty or missing. Ensure this field is correctly filled with your OVH SMS service identifier.
Invalid Phone Number Format: If the phone number is not in the correct international format, the API may reject the request. Use the E.164 format (e.g., +33123456789).
Authentication Errors: Incorrect or expired API credentials will cause authentication failures. Verify that all API keys and tokens are valid and have the necessary permissions.
API Rate Limits or Quotas: Sending too many messages in a short period might trigger rate limits. Check OVH account limits and adjust usage accordingly.
Network Issues: Connectivity problems to OVH endpoints will cause request failures. Ensure stable internet connection and no firewall blocking.
Error Handling: If the node is set to continue on failure, errors for individual items will be included in the output JSON under an
errorfield.