Ajax icon

Ajax

Consume Ajax API (v.0.1.2)
Join our community

Actions242

Overview

This node, named "Ajax," is designed to interact with the Ajax API (version indicated in the bundled source). It supports multiple resources and operations, including the "Pro" resource with the "Contact Info Confirmation" operation. The primary function of this operation is to confirm a user's contact information by validating tokens sent to their phone and email.

Typical use cases include:

  • Verifying user identity during registration or login flows.
  • Confirming updated contact details for security purposes.
  • Automating multi-factor authentication processes that require token confirmation.

For example, after a user receives a phone token via SMS and an email token via email, this node can be used to validate both tokens against the Ajax backend to confirm the user's contact info.

Properties

Name Meaning
Login The username or identifier of the user whose contact information is being confirmed.
Phone Token The token received on the user's phone, used to verify phone number ownership.
Email Token The token received via email, used to verify email address ownership.

Output

The node outputs JSON data representing the result of the contact info confirmation request. This typically includes confirmation status, any error messages if tokens are invalid, and possibly updated user information from the Ajax system.

If the operation succeeds, the output JSON confirms that the contact info has been verified. If it fails, the output will contain error details explaining why the confirmation did not succeed.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Ajax API.
  • Depends on the Ajax backend service being accessible and operational.
  • Uses internal helper classes for HTTP communication, state management, and operation resolution.

Troubleshooting

  • Invalid Tokens: If either the phone token or email token is incorrect or expired, the node will return an error indicating token validation failure. Ensure tokens are current and correctly entered.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is properly configured in n8n.
  • Network Issues: Connectivity problems with the Ajax API endpoint may cause timeouts or request failures. Check network access and API availability.
  • Parameter Validation: All three properties (Login, Phone Token, Email Token) are required. Omitting any will likely cause the node to throw an error before making the API call.

Links and References

Discussion