OVH SMS

Node catalog Actions

On this page

Send an SMS through an OVHcloud SMS service.

Usage and specifics

Configure the recipient, channel or topic and message for the provider. Ntfy and Apprise allow optional credentials depending on the server. Other services need dedicated access. Permissions, SMS charges and delivery limits remain service-specific.

Technical type : ovh_sms. Runtime : nodulz.

Credentials and prerequisites

OVH SMS (integration / ovh_sms). OVHcloud API application keys and consumer key

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`from`	`string`	`""`	-
`to`	`string`	`""`	-
`message`	`string`	`""`	-
`endpoint`	`enum`	`"eu"`	`eu`, `ca`, `us`
`serviceName`	`string`	`""`	-

Configuration help

endpoint API region: OVHcloud region where the SMS service and API keys were created.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "from": "",
  "to": "",
  "message": "",
  "endpoint": "eu",
  "serviceName": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.