Actions8
Overview
This node enables sending and managing SMS messages through the Nimba SMS API. Specifically, for the Verification OTP operation under the Message resource, it sends a one-time password (OTP) verification code via SMS to a specified phone number. This is useful in scenarios requiring user identity verification, such as two-factor authentication, account recovery, or transaction confirmation.
Practical examples include:
- Sending an OTP to users during login to verify their identity.
- Delivering a temporary code for password reset processes.
- Confirming transactions or sensitive actions with a time-limited code.
The node ensures the OTP message contains a placeholder for the code, validates phone numbers, and allows customization of OTP expiry, attempts, and code length.
Properties
| Name | Meaning |
|---|---|
| Sender Name | Select the sender name from available options (approved sender IDs). |
| Phone Number | The recipient's phone number to which the OTP will be sent. Must be a valid phone number. |
| Message | Message template containing the <1234> placeholder where the OTP code will be inserted. |
| Additional Fields | Optional settings including: • Expiry Time (minutes): Duration before OTP expires (5-30). • Attempts: Number of allowed verification attempts (3-10). • Code Length: Length of the OTP code in digits (4-8). |
Output
The node outputs a JSON object representing the response from the Nimba SMS API after requesting OTP verification. This typically includes details about the verification request such as status, reference ID, and metadata related to the OTP process.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Nimba SMS API using an API key credential configured in n8n.
- The node dynamically loads available sender names from the API to populate the "Sender Name" property.
- Proper phone number formatting and validation are enforced internally.
Troubleshooting
- Invalid phone number error: If the provided phone number is not valid, the node throws an error prompting to provide a valid phone number. Ensure the number includes country code and is correctly formatted.
- Missing
<1234>placeholder: The message must contain the exact<1234>placeholder; otherwise, an error is thrown. Make sure to include this placeholder in your message template. - Message too long: OTP messages have a maximum length of 153 characters. Exceeding this limit results in an error. Shorten your message accordingly.
- API errors: Network issues or invalid API credentials can cause failures. Verify API key validity and network connectivity.
- Exceeding limits: The node enforces limits on expiry time, attempts, and code length. Values outside allowed ranges will cause errors.
Links and References
- Nimba SMS API Documentation (for detailed API usage and parameters)
- n8n Documentation (for general node usage and credential setup)