Actions22
- Channel Actions
- Chat Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
This node interacts with the CrunchzApp API to validate a One-Time Password (OTP) code for a specified contact. It is useful in scenarios where you need to verify that a user or contact has provided a correct OTP, such as during two-factor authentication, account verification, or secure transaction confirmation.
For example, when a user receives an OTP on their device, this node can be used to confirm that the entered code matches the one generated and sent by the system, ensuring secure access or action authorization.
Properties
| Name | Meaning |
|---|---|
| Contact Id | The unique identifier of the contact for whom the OTP code is being validated (e.g., 6281357541790@c.us). |
| Code | The OTP code string that needs to be validated against the stored/generated code. |
Output
The node outputs JSON data representing the result of the OTP validation request. This typically includes whether the OTP was valid or not, and may contain additional metadata such as timestamps or status messages returned from the CrunchzApp API.
No binary data output is indicated.
Dependencies
- Requires an active connection to the CrunchzApp API.
- Needs an API key credential configured in n8n to authenticate requests to the CrunchzApp service.
- The base URL for API requests is
https://api.crunchz.app/api. - Requests are made with JSON content type headers.
Troubleshooting
- Invalid or expired OTP code: If the OTP code is incorrect or expired, the API will likely return an error or a validation failure response. Ensure the code is current and correctly entered.
- Incorrect Contact Id format: The contact ID must follow the expected format (e.g., including country code and domain like
@c.us). Invalid formats may cause the API to reject the request. - Authentication errors: Missing or invalid API credentials will prevent successful communication with the CrunchzApp API. Verify that the API key is correctly set up in n8n.
- Network issues: Connectivity problems or API downtime can cause request failures. Check network status and API availability.
- Unexpected API responses: If the API changes or returns unexpected data, the node might fail or produce errors. Review API documentation and update the node configuration accordingly.
Links and References
- CrunchzApp API Documentation (assumed typical location; replace with actual if known)
- n8n Documentation on Creating Custom Nodes