Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The "Verify OTP" operation of the Zender node allows users to verify a one-time password (OTP) code that was previously sent via SMS or WhatsApp. This is useful in scenarios where you need to confirm user identity, validate transactions, or secure access by confirming that the user has received and entered the correct OTP.

Typical use cases include:

  • Verifying user login or registration with an OTP.
  • Confirming sensitive actions like password resets or financial transactions.
  • Validating phone numbers during onboarding processes.

For example, after sending an OTP to a user's phone, this node can be used to check if the OTP entered by the user matches the one generated and sent, ensuring secure verification.

Properties

Name Meaning
OTP Code The one-time password code to verify. This is the code the user provides for validation.

Output

The node outputs a JSON object containing the response from the OTP verification API endpoint. This typically includes information about whether the OTP was valid or not, and may contain additional metadata such as expiration status or error messages.

Example output structure (simplified):

{
  "valid": true,
  "message": "OTP verified successfully",
  "details": { /* additional info */ }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Zender WhatsApp API service.
  • The node makes HTTP GET requests to the Zender API endpoint /get/otp with the OTP code as a query parameter.
  • Proper configuration of the API base URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Invalid OTP: If the OTP code is incorrect or expired, the API will return an error or invalid status. Ensure the OTP code is correctly captured and submitted within its validity period.
  • Authentication errors: If the API key credential is missing or invalid, requests will fail. Verify that the API key is correctly configured in n8n credentials.
  • Network issues: Connectivity problems can cause request failures. Check network access and API availability.
  • Error messages: The node throws errors with messages returned from the API. Use these messages to diagnose issues such as invalid parameters or rate limits.

If the node is set to continue on failure, errors will be included in the output JSON for each item.

Links and References

Discussion