Taximail

Overview

This node integrates with the Taximail API to verify a One-Time Password (OTP) previously sent via SMS. It is designed to confirm whether the OTP code entered by a user matches the one generated and sent by the system, ensuring secure verification for authentication or transaction confirmation processes.

Common scenarios where this node is beneficial include:

• User login or registration flows requiring OTP verification.
• Transaction confirmations that require an additional security step.
• Any workflow needing validation of a time-sensitive code sent to a user's phone.

For example, after sending an OTP SMS to a user’s phone, you can use this node to verify the code they enter, allowing your automation to proceed only if the OTP is valid.

Properties

Output

The node outputs a JSON object containing the result of the OTP verification:

• operation: Always "verify_otp" indicating the operation performed.
• message_id: The Message ID used for verification.
• otp_code: The OTP code submitted for verification.
• otp_valid: Boolean indicating if the OTP was valid (true) or not (false).
• verification_result: A string either "VALID", "INVALID", or "ERROR" describing the verification outcome.
• message: A human-readable message about the verification status, e.g., "OTP verification successful - code is valid" or "OTP verification failed - code is invalid or expired".
• timestamp: ISO timestamp of when the verification was performed.
• If an error occurs during verification, additional fields are included:
  • status: "error"
  • error_details: Description of the error encountered.

No binary data output is produced by this node.

Dependencies

• Requires an active connection to the Taximail API using an API key credential configured in n8n.
• The node depends on the Taximail OTP verification endpoint.
• Proper network access to https://api.taximail.com is necessary.
• The Message ID must be obtained from a prior OTP sending operation through this or another node interacting with Taximail.

Troubleshooting

• Missing Message ID or OTP Code: The node will throw errors if either the Message ID or OTP code is empty or missing. Ensure these inputs are correctly provided.
• Invalid or Expired OTP: If the OTP code does not match or has expired, the node returns a verification result of "INVALID". Users should prompt for re-sending the OTP.
• API Errors: Network issues or incorrect API credentials may cause verification failures. Check API key validity and network connectivity.
• Error Messages:
  • "Message ID is required for OTP verification": Provide a valid Message ID from the OTP send response.
  • "OTP code is required for verification": Provide the OTP code entered by the user.
  • "OTP verification failed - invalid code or expired": The OTP code did not pass validation; it may be wrong or expired.
  • "OTP verification failed - invalid code or expired" may also appear as a generic failure message if the API call fails.

Links and References

• Taximail Official API Documentation (for detailed API usage and parameters)
• n8n Documentation on Creating Custom Nodes