Ajax icon

Ajax

Consume Ajax API (v.0.1.2)

Actions242

Overview

This node, named "Ajax," is designed to interact with a specific Ajax API (version indicated in the code). It provides a flexible interface to perform various operations on multiple resources within the Ajax ecosystem. In particular, for the User resource and the Unbind Company Form Hub operation, the node allows you to unbind or disconnect a company from a hub for a specified user.

Common scenarios where this node is beneficial include:

  • Managing relationships between companies and hubs programmatically.
  • Automating administrative tasks related to user-company-hub associations.
  • Integrating Ajax system management into broader workflows without manual intervention.

For example, if a company no longer needs to be linked to a particular hub for a user, this node can automate the unbinding process as part of a larger workflow.

Properties

Name Meaning
Company Id The unique identifier of the company to be unbound from the hub.
Hub Id The unique identifier of the hub from which the company will be unbound.
Bound User Id The unique identifier of the user whose company-hub binding is to be removed.

Output

The node outputs JSON data representing the result of the unbind operation. This typically includes confirmation of success or failure, and may contain details about the updated state of the user, company, or hub bindings.

If the node supports binary data output, it would generally relate to any files or media returned by the Ajax API, but based on the provided code and operation, the output is primarily JSON structured data reflecting the operation's outcome.

Dependencies

  • Requires an API key credential for authenticating with the Ajax API.
  • Depends on the @digital-boss/n8n-designpatterns package for response-operation resolution and execution logic.
  • Uses internal backend modules for HTTP client communication and state management.
  • The node expects proper configuration of the Ajax API credentials within n8n.

Troubleshooting

  • Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions to perform unbind operations.
  • Invalid IDs: Errors may occur if the provided Company Id, Hub Id, or Bound User Id do not exist or are malformed. Double-check these values before execution.
  • Network issues: Failures in HTTP communication with the Ajax API could cause timeouts or connection errors. Verify network connectivity and API endpoint availability.
  • Operation not supported: If the operation or resource parameters are incorrect or unsupported, the node may throw errors indicating invalid operation/resource combinations.

Links and References

  • Ajax API Documentation (general reference for Ajax API)
  • n8n documentation on Creating Custom Nodes
  • @digital-boss/n8n-designpatterns package repository (if publicly available) for understanding response-operation patterns used in this node.

Discussion