Overview
This node allows sending messages via the SmsManager.com service using WhatsApp (either plain text or template messages) or SMS channels. It supports specifying a callback URL for delivery status or replies, either manually or by linking to an existing trigger node in the workflow.
Common scenarios include:
- Sending WhatsApp notifications or alerts with custom text.
- Using WhatsApp message templates with parameters for standardized communication.
- Sending SMS messages with configurable sender ID and gateway priority.
- Handling asynchronous callbacks for message status updates or replies.
Practical example:
- A business sends appointment reminders via WhatsApp text messages.
- A marketing campaign uses WhatsApp templates with dynamic parameters.
- An alert system sends SMS messages with high priority through a preferred gateway.
Properties
| Name | Meaning |
|---|---|
| Callback Strategy | How to provide the callback URL: "Manual URL" or "Use 'SmsMngr Trigger'" |
| Callback URL | The manual callback URL to receive message status or replies (shown if Callback Strategy is Manual) |
| Trigger Node Name | Name of an existing SmsMngr Trigger node in the workflow to use as callback URL (if strategy is Trigger) |
| Recipient (phone #) | Phone number of the message recipient (required) |
| Delivery Channel | Message channel: "WhatsApp Text", "WhatsApp Template", or "SMS" (required) |
| WA Sender ID | WhatsApp sender identifier (required for WhatsApp Text and Template) |
| Message Body | Text content of the WhatsApp message (required for WhatsApp Text) |
| Template Name | Name of the WhatsApp message template (required for WhatsApp Template) |
| Language Code | Language code for the WhatsApp template (default "en") |
| Template Parameters | Comma-separated list of parameters for the WhatsApp template |
| SMS Sender (alpha / #) | Sender ID for SMS messages (optional) |
| Gateway Priority | SMS gateway priority: "High" or "Low" (default "High") |
| Message Body | Text content of the SMS message (required for SMS) |
Output
The node outputs an array of JSON objects, each representing the response from the SmsManager API for each input item processed. Each response contains details about the sent message, including status and any identifiers returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to SmsManager.com.
- The node makes HTTP POST requests to
https://api.smsmngr.com/v2/message. - If using the "Trigger" callback strategy, a corresponding SmsMngr Trigger node must exist and be connected in the workflow to provide a valid webhook URL.
Troubleshooting
- Callback not found error: Occurs if the callback strategy is set to "trigger" but the specified trigger node name does not exist or is not connected. Ensure the trigger node exists and is properly named.
- API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Invalid phone numbers or sender IDs: Confirm that phone numbers are in the correct international format and sender IDs comply with SmsManager requirements.
- Missing required properties: Make sure all required fields for the selected channel (WhatsApp Text, WhatsApp Template, or SMS) are filled.
Links and References
- SmsManager API Documentation (for detailed API usage and message formats)
- n8n documentation on Creating Custom Nodes