How to send SMS with Make.com

In today's fast-paced digital environment, receiving critical alerts instantly can be the difference between a minor hiccup and a major business disruption. Whether it's a server going down, a new high-priority lead, or a suspicious logi

Contact Us
How to send SMS with Make.com

Oct-20-25 18:13

By using Make.com (formerly Integromat), you can create powerful, custom workflows that monitor your systems and send SMS alerts automatically the moment a specific event occurs.

Why Use Make.com for SMS Alerts?

  • No-Code Simplicity: Build complex automations with a visual, drag-and-drop interface—no programming skills required.

  • Real-Time Triggers: Make.com can poll your apps (like monitoring tools, databases, or forms) every few minutes, or receive instant webhooks for true real-time alerts.

  • Massive App Ecosystem: Connect to hundreds of popular services like Google Sheets, Datadog, monitoring tools, CRMs, and of course, SMS gateways like Furay Telecom.

  • Flexibility & Logic: Add filters, routers, and data transformers to ensure you only get notified for the most important events, reducing alert fatigue.


Building Your Automated SMS Alert System

Let's walk through the process of creating a scenario in Make.com. We'll use a generic "Monitoring App" as our trigger and connect it to an SMS module.

Scenario 1: Server Downtime Alert

This is a classic use case. You want an SMS the moment your website or server monitoring service detects an outage.

Step 1: Set Up the Trigger

The trigger is the event that starts your automation.

  1. Create a new scenario in Make.com.

  2. Click the first module and select your monitoring service (e.g., UptimeRobotDatadogPingdom). If your service isn't listed, you can often use a Webhook or HTTP module to receive alerts.

  3. Authenticate your account.

  4. Choose the triggering event, such as "Watch Alert" or "New Incident."

  5. Configure the module to watch for the specific alert type, like a "Down" event.

Step 2: Add an SMS Action Module

This is the action that sends the SMS.

  1. Add your next module. Search for and select your preferred SMS service provider. For this example, we'll use a generic HTTP or Webhook module to connect to the Furay Telecom SMS API.

  2. Set the method to POST.

  3. Enter the Furay Telecom API endpoint URL (e.g., https://api.furaytele.com/v1/sms/send).

  4. In the Headers section, add:

    • Content-Type: application/json

    • Authorization: Bearer YOUR_FURAY_API_KEY

  5. In the Body section, map the data from your trigger to construct a clear, concise alert message.

Example Body Structure:

json
{
  "to": "+1234567890",
  "message": "🚨 ALERT: Server '{{1.name}}' is DOWN! (Status: {{1.status}}). Time: {{1.timestamp}}. Please check immediately."
}
  • {{1.name}} and {{1.status}} are data placeholders that will be pulled directly from the monitoring app's alert, making the message dynamic and informative.

Step 3: Activate Your Scenario

Save and run your scenario once to ensure it works. Then, turn on the scheduler to let it run continuously, checking for new alerts every few minutes or listening for incoming webhooks.

Your final scenario flow will look like this:
[Monitoring App] → (Trigger: New Alert) → [HTTP/SMS App] → (Action: Send SMS)


Scenario 2: Critical Error Log Alert

You can also monitor application error logs and get notified only for severe errors.

The Flow:
[Google Sheets/Database] → (Watch for new rows with "CRITICAL" status) → [SMS App] → (Send SMS)

  1. Trigger: Use a Google Sheets module to "Watch Rows." Set up a filter so that it only proceeds if the Error Level column contains "CRITICAL."

  2. Action: Connect to your SMS module (e.g., Furay Telecom via HTTP) and map the error details into the message body.

Example SMS Message:
⚠️ APP ERROR: A critical error occurred in payment module. User: {{2.userID}}. Error: {{2.message}}. [Link to Logs]


Best Practices for Effective Alert SMS

To ensure your alerts are useful and not just noise, follow these guidelines:

  1. Keep it Short and Critical: SMS is for urgent, time-sensitive information. Get straight to the point.

  2. Use Clear Language: Avoid technical jargon. The message should be understandable at a glance.

    • Bad: HTTP 500 on /api/v1/process

    • Good: 🚨 WEBSITE ERROR: Checkout page is failing (500 Error).

  3. Include a Call to Action: Tell the recipient what to do.

    • Example: ...Please check the dashboard.

  4. Use Emojis Sparingly: A single, relevant emoji (like 🚨, ⚠️, ✅) can draw immediate attention.

  5. Filter Aggressively: Use Make.com's Router and Filter tools to send different levels of alerts to different people or channels. Only send an SMS for "Critical" issues, and route "Warning" level alerts to a Slack channel or email.

  6. Handle Failures: Consider adding an additional step to log sent alerts to another sheet or app. This creates an audit trail in case an SMS fails to deliver.

Conclusion

Automating SMS alerts with Make.com transforms your operational resilience. It empowers you and your team to respond to critical issues with unprecedented speed, minimizing downtime and its associated costs. By connecting the tools you already use to a reliable SMS gateway like Furay Telecom, you build a robust, real-time notification system that keeps you informed and in control, no matter where you are.

Stop manually checking logs and dashboards. Set up your first Make.com SMS alert scenario today and experience the peace of mind that comes with proactive, automated monitoring.

Get Support

The product you were looking for was not found

Contact US

Submit order

If you have any questions, you are welcome to submit a ticket to us

Get a Touch