Overview
This node integrates with the Taximail API to send SMS One-Time Passwords (OTPs). It is designed to facilitate secure user verification workflows by sending OTP codes via SMS using predefined templates. Typical use cases include two-factor authentication, password resets, and transaction verifications where a temporary code must be sent to a user's phone number.
For example, when a user requests a login verification code, this node sends an SMS OTP to their phone number using a specified template key. The message ID returned can later be used to verify the OTP or check its delivery status.
Properties
| Name | Meaning |
|---|---|
| To Phone (MSISDN) | Recipient phone number including country code (e.g., 66812345678). Required for sending. |
| OTP SMS Template Key | Template key identifying the SMS template used for the OTP message. Required for sending. |
Output
The node outputs a JSON object containing:
- The response from the Taximail API related to the OTP sending request.
- An
operationfield set to"sms_otp"indicating the performed action. - A
noteadvising to save the returnedmessage_idfor later OTP verification. - The
message_iditself is included in the API response and should be stored externally if verification or status checking is needed later.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for HTTP Basic Authentication to access the Taximail API.
- The node uses the Taximail API endpoints for transactional messaging and OTP management.
- Proper configuration of credentials within n8n is necessary before use.
Troubleshooting
- Missing OTP Template Key: If the "OTP SMS Template Key" property is empty or missing, the node will throw an error stating that the OTP template key is required. Ensure this field is filled with a valid template key.
- Invalid Phone Number Format: The phone number must include the country code without spaces or special characters. Incorrect formatting may cause API errors.
- API Authentication Errors: If the provided API credentials are invalid or missing, the node will fail to authenticate with the Taximail service.
- Operation Failures: Any unexpected failure during the API call will result in an error with a message prefixed by "Operation failed". Check network connectivity and API quota limits.
- Saving Message ID: Always save the returned
message_idafter sending an OTP, as it is required for subsequent OTP verification or status checks.
Links and References
- Taximail Official API Documentation (for detailed API usage and template management)
- n8n Documentation on HTTP Basic Authentication Credentials