Learn how to build a reliable SMS notification system using Textbelt and this customizable n8n workflow. Perfect for technical users needing instant message delivery.
Download this n8n workflow template and start using it instantly.
Developers or technical staff needing to integrate simple, transactional SMS notifications into applications.
Business users looking for a repeatable n8n templates solution for testing SMS integration.
Instant communication is critical, and integrating SMS functionality often requires technical skill and dedicated API configuration. This n8n workflow simplifies the process dramatically by providing a ready-to-use structure for sending text messages via the reliable Textbelt API.
This specific n8n templates solution is designed for simplicity and immediate execution. Instead of embedding API keys directly into complex functions, the structure ensures that your phone number, message content, and API key are clearly defined in an initial data node before being securely passed to the Textbelt endpoint using the HTTP Request n8n node. This makes the entire n8n workflow easy to debug and maintain, offering a powerful, automated communication channel directly from your n8n instance.
This n8n workflow is initiated manually, making it ideal for testing or for scenarios where you integrate it as a sub-workflow triggered by another event (like a webhook or database update).
phone (the recipient's number), message (the content of the SMS), and key (your Textbelt API key). This standardizes the required input structure for the remainder of the n8n workflow.https://textbelt.com/tex).phone, message, and key values defined in the 'Set Data' node directly into the request body, executing the SMS send command. The response from the Textbelt API confirms the success or failure of the message delivery, concluding the n8n workflow execution.To utilize this n8n templates workflow effectively, follow these steps:
value fields for phone, message, and key with your desired target phone number, message content, and Textbelt API key, respectively. (Note: In a production n8n workflow, the key should ideally be stored as an n8n credential or environment variable, rather than directly in the Set node). When clicking ‘Execute workflow’ (Manual Trigger n8n node):
Function: Serves as the starting point for this specific n8n templates solution. It is a simple n8n trigger used for manual testing and development, allowing you to run the process immediately.
Key Configuration: Standard manual execution setup.
Set Data (n8n node):
Function: Defines the three essential variables (phone, message, key) that Textbelt requires. This ensures the necessary data structure is available before the API call.
Key Configuration: Assignments are set as strings, designed to be populated before execution.
HTTP Request (n8n node):
Function: Handles the communication with the external Textbelt API. It sends the payload required to dispatch the SMS.
Key Configuration:
Method: POST
URL: https://textbelt.com/tex
Body Parameters: Uses expressions to dynamically inject input data from the previous node: ={{ $json.phone }}, ={{ $json.message }}, and ={{ $json.key }}. This is a crucial element of the n8n workflow data flow.
Automate lead qualification using the n8n multi-step form feature. This n8n workflow captures initial signups, sends Slack alerts, and collects rich user data via chained n8n nodes, saving all info to Google Sheets.

Use this efficient n8n workflow template to automatically scrape your XML sitemap and submit every URL to the Google Indexing API. This n8n automation ensures fast indexing.

Automate expense logging using an n8n AI agent. This powerful n8n workflow parses unstructured chat messages and logs structured data directly into Google Sheets, leveraging advanced n8n node configurations.

Deploy a comprehensive n8n workflow to create a Telegram customer service bot. This powerful n8n template handles scheduling via Google Calendar, pricing checks using Google Sheets, and internal knowledge base lookups using AI Agents and the MCP protocol.









































