Ajax icon

Ajax

Consume Ajax API (v.0.1.2)
Join our community

Actions242

Overview

This node, named "Ajax," is designed to interact with a specific Ajax API (version indicated in the code). It supports multiple resources and operations, including the "Pro" resource with the "Confirm Password Reset" operation. The primary function of this operation is to confirm a password reset request by verifying either a phone or email identifier along with optional tokens and a new password.

Common scenarios for this node include:

  • Confirming a user's password reset process after they have requested it.
  • Validating tokens sent via phone or email to ensure secure password changes.
  • Updating the user's password securely once verification is complete.

Practical example: A user initiates a password reset on a platform; this node can be used to confirm the reset by providing the user's phone number or email, along with the token received via SMS or email, and optionally setting a new password.

Properties

Name Meaning
Phone Or Email The user's phone number or email address used to identify the account for password reset.
Additional Fields Optional fields that can include:
- Phone Token Token received via phone/SMS to verify identity.
- Mail Token Token received via email to verify identity.
- New Password The new password to set for the user after confirmation.

Output

The node outputs JSON data representing the result of the password reset confirmation operation. This typically includes success status, any messages from the API, and possibly updated user information related to the password reset.

If the node supports binary data output, it would generally relate to attachments or files returned by the API, but based on the provided code and properties, this operation focuses on JSON responses only.

Dependencies

  • Requires an API key credential for authenticating requests to the Ajax API.
  • Depends on internal modules for HTTP communication, state management, and operation resolution/execution.
  • No additional external services are explicitly required beyond the Ajax API itself.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key credential is correctly configured in n8n.
  • Invalid or missing tokens: If the phone or mail token is incorrect or expired, the API will likely reject the confirmation. Verify tokens before submission.
  • Incorrect phone or email input: The identifier must match the one used during the password reset request.
  • New password requirements: If a new password is provided, it must meet the API's password policy; otherwise, the operation may fail.
  • Network issues: Connectivity problems with the Ajax API endpoint can cause failures; check network access and API availability.

Common error messages might include authentication errors, token validation failures, or missing required parameters. Resolving these involves checking credentials, input correctness, and ensuring all required fields are provided.

Links and References

Discussion