Taximail icon

Taximail

Send Email, SMS, OTP via Taximail API with AI content generation or check status/verify OTP

Actions5

Overview

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

Common scenarios where this node is beneficial include:

  • Verifying user identity during login or registration flows.
  • Confirming sensitive transactions or changes in user settings.
  • Two-factor authentication processes requiring OTP validation.

For example, after sending an OTP SMS to a user's phone, you can use this node to verify the OTP code they provide, ensuring it is valid before proceeding.

Properties

Name Meaning
Message ID The unique message ID received from the OTP sending response; used to identify the OTP session to verify.
OTP Code The actual OTP code input by the user that needs to be verified against the sent OTP.

Output

The node outputs a JSON object containing the response from the Taximail API regarding the OTP verification status. Key fields include:

  • status: Indicates the overall status of the verification request (e.g., "success").
  • code: Numeric code representing the verification result (202 means success).
  • otp_valid: Boolean indicating whether the OTP was valid (true) or invalid (false).
  • message: A human-readable message stating if the OTP verification was successful or failed.
  • operation: Always set to "verify_otp" to indicate the operation performed.

This output allows downstream nodes or workflows to branch logic based on whether the OTP was correctly verified.

Dependencies

  • Requires an API key credential for HTTP Basic Authentication to access the Taximail API.
  • Needs network connectivity to https://api.taximail.com.
  • No additional environment variables are required beyond the API credentials configured in n8n.

Troubleshooting

  • Common Issues:

    • Using an incorrect or expired Message ID will cause verification to fail.
    • Providing an incorrect OTP code will result in a failed verification.
    • Missing or invalid API credentials will prevent communication with the Taximail API.

  • Error Messages:

    • If the operation fails due to API issues or network errors, the node throws an error with a message starting with "Operation failed:" followed by the specific error detail.
    • If an unknown operation is selected (not applicable here since only "verify_otp" is considered), an error "Unknown operation" would be thrown.

  • Resolution Tips:

    • Ensure the Message ID corresponds exactly to the one returned when the OTP was sent.
    • Double-check the OTP code entered by the user.
    • Verify that the API credentials are correctly set up and have necessary permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion