Send transactional SMS with the OVHcloud SMS API
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 5 nodes and runs manually, when you click “Execute workflow”. It uses only n8n's built-in nodes.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Set OVH API Credentials (Edit Fields (Set)): sets 6 fields: APPLICATION_KEY, APPLICATION_SECRET, CONSUMER_KEY…
- Prepare SMS Payload (Edit Fields (Set)): sets 2 fields: receiver, message
- Build OVH SMS API Request (Code): runs custom JavaScript code
- Post to OVH SMS API (HTTP Request): calls an HTTP API (POST)
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest
From the author
Quick overview This workflow manually triggers an HTTP request to the OVHcloud SMS API, signing it with your OVH application credentials to send a transactional SMS to a specified phone number. How it works 1. Runs when you manually execute the workflow. 2.…