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 transactions or sensitive actions requiring an additional security step.
  • Validating OTPs in multi-factor authentication systems.

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 correct before proceeding.

Properties

Name Meaning
Message ID The unique message ID received from the OTP sending response. Used to identify the OTP 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: The status of the verification request (e.g., "success").
  • code: Numeric code indicating the result (202 means valid OTP).
  • otp_valid: Boolean indicating if the OTP was successfully verified (true if valid, false otherwise).
  • message: A human-readable message stating whether 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 valid.

Dependencies

  • Requires an API key credential for authenticating with the Taximail API using HTTP Basic Authentication.
  • Needs network access to the Taximail API endpoint at https://api.taximail.com/v2/otp/verify.
  • No additional environment variables are required beyond the API credentials configured in n8n.

Troubleshooting

  • Common issues:

    • Invalid or expired Message ID: Ensure you use the exact message ID returned when the OTP was originally sent.
    • Incorrect OTP code: Verify the user inputs the correct OTP without extra spaces or characters.
    • Network or authentication errors: Check that the API credentials are correctly configured and have sufficient permissions.

  • Error messages:

    • If the operation fails due to unknown reasons, the node throws a generic "Operation failed" error with details.
    • If the Message ID or OTP Code is missing or invalid, the API may return an error which will be propagated by the node.

To resolve errors, verify all input parameters, ensure valid credentials, and check the Taximail API status.

Links and References

Discussion