Send transactional SMS with the OVHcloud SMS API

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

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...

Best for

Miscellaneous automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.httprequest

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Thibaut TRESSE.

Original n8n.io source

1.1 Workflow description

Title: Send transactional SMS with the OVHcloud SMS API
Workflow name: Send transactional SMS with the OVHcloud SMS API

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

Runs when you manually execute the workflow.
Sets the OVHcloud API credentials, SMS service name, sender, and target API region.
Defines the SMS recipient number and message text to send.
Generates the OVHcloud request URL, JSON body, timestamp, and SHA1-based X-Ovh-Signature headers.
Sends a POST request to the OVHcloud endpoint /sms/{serviceName}/jobs to create an SMS sending job.

Setup

Create OVHcloud API application credentials (Application Key and Application Secret) and a Consumer Key with SMS permissions.
Replace the placeholder values for APPLICATION_KEY, APPLICATION_SECRET, CONSUMER_KEY, SMS_SERVICE_NAME, SMS_SENDER, and OVH_REGION.
Update the receiver (E.164 format) and message fields with the SMS details you want to send, and ensure your OVHcloud SMS account has available credits.

Requirements

OVH account
SMS credits (API account)

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 2 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 3 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 4 - Manual Execution Trigger

Type / Role: n8n-nodes-base.manualTrigger - manualTrigger
Config choices: Version 1

Block 5 - Set OVH API Credentials

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 6 - Prepare SMS Payload

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 7 - Build OVH SMS API Request

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 8 - Post to OVH SMS API

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

3. Summary Table

Workflow	Send transactional SMS with the OVHcloud SMS API
Complexity	intermediate
Nodes	8
Categories	Miscellaneous
Author	Thibaut TRESSE
Published	04 Jun 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/16124/16124.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Miscellaneous workflows

Frequently asked questions

What does Send transactional SMS with the OVHcloud SMS API do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Miscellaneous use case.

Thibaut TRESSE

2 workflows

Nodes

n8n-nodes-base.stickynote n8n-nodes-base.manualtrigger n8n-nodes-base.set n8n-nodes-base.code n8n-nodes-base.httprequest

Complexity

intermediate

Published 04 Jun 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/16124/16124.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Predict airport queue wait times and email alerts with OpenAI and SendGrid

## Quick Overview This workflow accepts traveler flight details via webhook or runs every 5 minutes, predicts airport queue wait times with a custom JavaScript model, generates an alert message using OpenAI, emails the traveler via SendGrid, and logs the prediction to Google Sheets. ## How it works 1. Receives a POST request to a webhook with traveler/flight details or runs on a 5-minute schedule. 2. Normalizes the incoming data into a consistent context (flight, airport/terminal, traveler contact details, and live queue inputs). 3. Waits briefly to throttle processing, then calculates predicted security, immigration, and boarding wait times plus risk flags and an optimal arrival time. 4. Sends the prediction to OpenAI to generate a short, traveler-friendly alert message. 5. Formats the final alert payload (alert level, email subject/body) and prepares a row for tracking. 6. Sends the alert email through the SendGrid Mail Send API and appends the prediction record to a Google Sheets tab. ## Setup 1. Configure the webhook URL in the system that submits traveler requests (POST to `/airport-queue-check`) or enable the schedule trigger for proactive runs. 2. Add OpenAI credentials and select the chat model used to generate the traveler message. 3. Add Google Sheets OAuth2 credentials and replace `YOUR_SHEET_ID` and the target range (for example, `Predictions!A1:append`) in the Google Sheets request URL. 4. Add your SendGrid API key by replacing `YOUR_SENDGRID_API_KEY` in the Authorization header, and update the sender/recipient fields (including ensuring `travelerEmail` is provided by the trigger payload).

View

Tutor English chat messages using OpenRouter with Postgres memory and log to Supabase

## Quick overview This workflow receives English practice messages via a webhook, uses an OpenRouter chat model with Postgres-backed conversation memory to generate tutoring feedback, logs the exchange to Supabase, and returns the tutor’s reply as a JSON response. ## How it works 1. Receives a POST webhook request containing a `user_id` and `message`. 2. Extracts and standardizes the incoming fields so the workflow has clean `user_id` and `message` values. 3. Sends the message to an AI English tutor powered by OpenRouter, using Postgres chat memory keyed by `user_id` to maintain per-student context. 4. Logs the tutor output to a Supabase `conversations` table along with the user identifier and original message. 5. Returns a JSON response to the caller containing the tutor’s reply. ## Setup 1. Add an OpenRouter API credential and (optionally) choose a different model in the OpenRouter chat model configuration. 2. Add Postgres credentials and ensure the database is reachable from n8n so chat memory can persist sessions by `user_id`. 3. Add Supabase credentials and create a `conversations` table, then confirm the mapped columns (`user_id`, `role`, `message`) match your schema. 4. Copy the webhook URL from n8n and configure your app to POST a JSON body with `user_id` and `message` to that endpoint.

View

Send smart lock PINs for Apaleo reservations with Seam, Gmail, and Twilio

## Quick overview Youtube video explanation Link: https://youtu.be/3ukKYmCF5XY?si=-iRKpBUIGzhnczMk This workflow reacts to Apaleo reservation unit assignments, generates a time-bound smart lock access code via Seam, saves it back to the Apaleo reservation comment, and notifies guest using Gmail and Twilio, while also rotating an Apaleo bearer token on a 58‐minute schedule. ## How it works 1. Triggers when Apaleo emits a reservation/unit-assigned event. 2. Retrieves the full reservation details from Apaleo using the reservation ID from the event. 3. Maps the reservation’s unit identifier to a Seam device ID and prepares the access window from the arrival and departure dates. 4. Creates an access code in Seam for the mapped device and reservation time window. 5. Updates the Apaleo reservation comment to store the generated PIN. 6. Fetches the reservation again via the Apaleo Booking API to get primary guest and booker contact details and sends the PIN via Gmail email and Twilio SMS. 7. Separately, runs every 58 minutes to request an Apaleo OAuth access token and PATCH an n8n credential so the Apaleo bearer token used for customer lookups stays current. ## Setup 1. Configure Apaleo OAuth2 credentials for the Apaleo trigger and reservation read/update actions, and ensure your Apaleo app has permission to read and patch reservations. 2. Add a Seam API credential (HTTP header auth) and replace the sample room-to-device mapping list with your real Apaleo unit IDs and Seam device IDs. 3. Add Gmail OAuth2 credentials and update the email sender details, subject, and template placeholders as needed. 4. Add Twilio credentials, set a valid Twilio “from” number, and confirm the workflow uses the correct guest phone field for your Apaleo data. 5. For token rotation, set the Apaleo client credentials Basic auth header, your n8n instance URL, and the credential ID to patch, and add an n8n API credential with permission to update credentials.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Send transactional SMS with the OVHcloud SMS API

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Quick overview

How it works

Setup

Requirements

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Sticky Note

Block 2 - Sticky Note1

Block 3 - Sticky Note2

Block 4 - Manual Execution Trigger

Block 5 - Set OVH API Credentials

Block 6 - Prepare SMS Payload

Block 7 - Build OVH SMS API Request

Block 8 - Post to OVH SMS API

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions