CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API
Join our community

Actions22

Overview

This node interacts with the CrunchzApp API to validate OTP (One-Time Password) codes for specific contacts. It is useful in scenarios where you need to verify that a user or contact has provided a correct OTP code, such as during two-factor authentication, account verification, or secure transaction confirmation.

For example, after sending an OTP code to a user's phone number, this node can be used to confirm that the code entered by the user matches the one generated and sent by the system.

Properties

Name Meaning
Contact Id The unique identifier of the contact for which the OTP code is being validated (e.g., 6281357541790@c.us). This typically represents the recipient's phone number or contact handle.
Code The OTP code string that needs to be validated against the stored/generated code for the contact.

Output

The node outputs JSON data representing the result of the OTP validation request. Typically, this will include information indicating whether the OTP code was valid or not, and may contain additional metadata such as timestamps or status messages.

If the node supports binary data output, it would generally relate to any files or media returned by the API, but based on the provided code and context, the output is primarily JSON confirming OTP validation results.

Dependencies

  • Requires an active CrunchzApp API key credential configured in n8n.
  • The node sends requests to the CrunchzApp API endpoint at https://api.crunchz.app/api.
  • Proper network connectivity to the CrunchzApp service is necessary.

Troubleshooting

  • Invalid OTP Code: If the OTP code does not match or has expired, the API will likely return an error or a validation failure response. Ensure the code is correctly entered and still valid.
  • Incorrect Contact Id: Using an incorrect or malformed contact ID may cause the validation to fail. Verify the contact ID format matches expected patterns.
  • Authentication Errors: Missing or invalid API credentials will prevent the node from communicating with the CrunchzApp API. Confirm that the API key credential is properly set up.
  • Network Issues: Connectivity problems or API downtime can cause request failures. Check your internet connection and CrunchzApp service status.
  • Error Messages: The node may throw errors related to HTTP status codes or JSON parsing if the API response is unexpected. Review the error details and ensure the input parameters are correct.

Links and References

Discussion