Actions8
Overview
This node integrates with the Nimba SMS API to send SMS messages. It allows users to send SMS messages to multiple recipients by specifying sender names and phone numbers, making it useful for marketing campaigns, notifications, alerts, or any scenario requiring bulk SMS communication.
A practical example: A business wants to notify up to 50 customers simultaneously about a promotion. They select a verified sender name, input the customers' phone numbers, compose the message, and send it in one operation.
Properties
| Name | Meaning |
|---|---|
| Sender Name | Select the sender name from available options (verified sender IDs). |
| Phone Numbers | The recipient phone numbers (up to 50), each specified with country code (e.g., +224...). |
| Message | The SMS message content to send (max 665 characters for concatenated SMS). |
Output
The node outputs an array of JSON objects representing the response(s) from the Nimba SMS API after sending the message(s). Each object contains details about the sent message batch, such as status and metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Nimba SMS API.
- The node uses internal helper functions to validate and format phone numbers and messages before sending.
- The "Sender Name" options are dynamically loaded from the API endpoint that lists accepted sender names.
Troubleshooting
- No valid contacts provided: Occurs if no phone numbers are supplied or all are invalid. Ensure at least one valid phone number with country code is provided.
- Too many contacts: Maximum allowed is 50 phone numbers per execution. Reduce the number of recipients accordingly.
- Invalid phone number: If any phone number fails validation, the node throws an error specifying which number is invalid. Verify the format includes the country code and is correct.
- Message too long: Messages exceeding 665 characters are rejected. Shorten the message to fit within this limit.
- API request errors: Network issues or invalid credentials can cause failures. Check API key validity and network connectivity.
Links and References
- Nimba SMS API Documentation (example placeholder link)
- E.164 Phone Number Format - recommended phone number formatting standard