Ajax icon

Ajax

Consume Ajax API (v.0.1.2)

Actions242

Overview

This node, named "Ajax," is designed to interact with the Ajax API (version indicated in the code). It supports multiple resources and operations, including the "Installation" resource with the operation "Invite Installation Company To Hub." The primary function of this operation is to send an invitation to a specified installation company to join a particular hub within the Ajax system.

Common scenarios for using this node include automating the management of installation companies by inviting them programmatically to hubs, which can be useful in large-scale deployments or integrations where manual invitations would be inefficient. For example, a security service provider could automate onboarding new installation partners into their monitoring hubs.

Properties

Name Meaning
User Id The identifier of the user initiating or associated with the invitation.
Hub Id The identifier of the hub to which the installation company is being invited.
Company Hex Id The unique hexadecimal identifier of the installation company to invite to the hub.

These properties are required inputs when performing the "Invite Installation Company To Hub" operation under the "Installation" resource.

Output

The node outputs JSON data representing the result of the invitation operation. This typically includes confirmation details such as success status, any returned identifiers, or error messages if the invitation failed. The exact structure depends on the Ajax API response but generally confirms whether the invitation was successfully sent.

If the node handles binary data, it would relate to attachments or media associated with the invitation, but based on the provided code and operation, no binary output is expected.

Dependencies

  • Requires an API key credential for authenticating with the Ajax API.
  • Depends on the external Ajax API service to perform operations.
  • Uses internal helper classes for HTTP requests, state management, and operation resolution.
  • The node expects proper configuration of the API credentials within n8n.

Troubleshooting

  • Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
  • Invalid IDs: Errors may occur if userId, hubId, or companyHexId are incorrect or do not exist in the Ajax system.
  • Network issues: Connectivity problems with the Ajax API endpoint can cause failures; verify network access.
  • API limits or restrictions: The Ajax API might enforce rate limits or require specific roles; check API documentation and account settings.
  • Error messages from API: The node will relay error messages from the Ajax API; review these messages to understand issues like invalid parameters or unauthorized access.

Links and References

Discussion