Ajax icon

Ajax

Consume Ajax API (v.0.1.2)
Join our community

Actions242

Overview

The node named "Ajax" is designed to interact with the Ajax API (version indicated in the code). Specifically, for the User resource and the Confirm Password Reset operation, it facilitates confirming a user's password reset request. This typically involves verifying a token sent via phone or email and setting a new password.

Common scenarios where this node is beneficial include:

  • Completing a password reset flow initiated by a user who requested to reset their password.
  • Automating user account recovery processes in applications integrated with the Ajax system.
  • Validating tokens received through different channels (phone or email) before allowing password changes.

For example, after a user requests a password reset, they receive a token on their phone or email. Using this node, you can confirm the token and set a new password programmatically within an n8n workflow.

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 including:
• Phone Token — token received via phone
• Mail Token — token received via email
• New Password — the new password to set for the user

Output

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

If the operation supports binary data output (not evident from the provided code), it would represent associated files or attachments, but here the focus is on JSON response data.

Dependencies

  • Requires an API key credential for authenticating with the Ajax API.
  • Depends on the external Ajax API service being available and reachable.
  • Uses internal helper classes for HTTP communication, state management, and operation resolution bundled within the node's implementation.

Troubleshooting

  • Invalid or missing tokens: If the phone or mail token is incorrect or expired, the API will likely return an error. Ensure tokens are correctly captured and passed.
  • Incorrect phone or email: Providing an unregistered phone number or email will cause the operation to fail. Verify user identifiers before execution.
  • Missing new password: If the new password field is not provided when required, the operation may not complete successfully.
  • API authentication errors: Ensure the API key credential is valid and has necessary permissions.
  • Network issues: Connectivity problems with the Ajax API endpoint will cause failures; check network access and endpoint availability.

Links and References

Discussion