This article provides a complete, practical walkthrough of the Manual Msg91 Send Triggered n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Automate SMS Notifications with n8n and MSG91: A Simple Workflow
   
   Meta Description:
   Learn how to automate SMS messaging using n8n and MSG91 with a simple no-code workflow. Trigger messages on demand with just one click.
   
   Keywords:
   n8n, MSG91, SMS automation, no-code SMS, n8n workflow, send SMS n8n, MSG91 API, automated text messaging, trigger-based SMS, workflow automation
   
   Third-Party APIs Used:
   
   - MSG91 API
   
   Article:
   
   Automate SMS Notifications with n8n and MSG91: A Simple Workflow
   
   In the era of digital communication, SMS remains one of the most effective and direct ways to reach users, customers, or team members. Whether you're a small business owner trying to send appointment reminders or a developer integrating SMS alerts into your automated routines, having a reliable method to dispatch messages is essential. 
   
   In this article, we’ll explore how to set up a basic n8n workflow to send SMS messages using MSG91, a leading cloud communication platform. This guide will walk you through a minimal example where a message is sent at the click of a button using n8n’s Manual Trigger and MSG91 node.
   
   What is n8n?
   
   n8n (short for “nodemation”) is an open-source, fair-code workflow automation tool that allows users to connect various applications, APIs, and services without writing custom backend code. Its node-based interface makes automation accessible for both technical and non-technical users.
   
   What is MSG91?
   
   MSG91 is a popular cloud communication API platform that allows businesses to send SMS, voice, email, and other messaging through programmatic interfaces. Their SMS API is widely used for OTPs, promotional messages, updates, and transactional alerts.
   
   Use Case Overview
   
   In this example, we’re creating a simple n8n workflow that sends an SMS message via MSG91 when a button is manually triggered inside n8n’s interface. This setup is perfect for testing or one-time notifications during demos, internal communications, or administrative purposes.
   
   Workflow Breakdown
   
   The workflow, titled "Send an SMS using MSG91", consists of two main components:
   
   1. Manual Trigger Node
   2. MSG91 Node
   
   Let’s dive into each of them.
   
   1. Manual Trigger Node: "On clicking 'execute'"
   
   The Manual Trigger node allows the user to manually trigger the workflow inside the n8n editor. This is useful for workflows that you want to run on demand instead of triggering them based on a schedule or incoming webhook.
   
   In this workflow, the trigger is labeled "On clicking 'execute'", meaning the workflow will start when the user manually clicks the "Execute Workflow" button in the n8n interface.
   
   2. MSG91 Node
   
   This is where the actual SMS sending magic happens.
   
   Here’s what the configuration looks like (based on the provided JSON):
   
   - to: (recipient’s phone number)
   - from: (sender ID or name assigned by MSG91)
   - message: (the content of the message you want to send)
   
   These fields are placeholders in the raw JSON and should be populated with your actual data when you customize the workflow.
   
   Additionally, the MSG91 node uses "msg91Api" credentials, which you need to configure within n8n. This means obtaining an API key from your MSG91 account and adding it to the credentials section in n8n.
   
   How it Works
   
   The logic of the workflow is straightforward:
   
   - Step 1: You open the n8n editor and click "Execute Workflow."
   - Step 2: The Manual Trigger node initiates the flow.
   - Step 3: This immediately passes control to the MSG91 node, sending the predefined SMS message to the desired recipient.
   
   The current configuration is minimal and ideal for learning and testing. You can extend this workflow by:
   
   - Fetching phone numbers or messages dynamically from a Google Sheet, Airtable, or database.
   - Triggering SMS alerts based on other events (e.g., form submissions, website user signups).
   - Adding error handling or logs using additional n8n nodes.
   
   Why Use This Setup?
   
   There are several compelling reasons to consider integrating MSG91 SMS functionality into your automated processes:
   
   - No-Code Development: No need for traditional coding or backend development to send texts.
   - On-Demand Alerts: Use the Manual Trigger to test or send messages when needed—perfect for demos or temporary use cases.
   - Scalable: Once you’ve validated this basic setup, it’s easy to scale and integrate with CRMs, chatbots, or marketing workflows.
   
   Security Note
   
   This setup requires you to authenticate with MSG91’s API. Be sure to keep your credentials secure within n8n and never expose sensitive keys in public workflows. Use environment variables or encrypted credential storage provided by n8n.
   
   Conclusion
   
   Sending SMS messages is a powerful way to keep your users informed and engaged. Thanks to tools like n8n and services like MSG91, building this capability into your workflows doesn’t have to be complicated. By following this simple example, you can set up a functional SMS sender in minutes and later customize it to suit your business or application needs.
   
   Whether you're sending transactional notifications, daily updates, or marketing promos, this no-code automation puts messaging control right at your fingertips.
   
   Happy automating!
   
   — End of Article —

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.