Ajax icon

Ajax

Consume Ajax API (v.0.1.2)

Actions242

Overview

The node named "Ajax" is designed to interact with the Ajax API (version indicated by the bundled version import). It supports multiple resources and operations, including the "User" resource with the "Get Bound Users List" operation. This operation retrieves a list of users bound to a specific hub for a given user ID.

This node is beneficial in scenarios where you need to programmatically access user-hub relationships within the Ajax system, such as managing user permissions, monitoring user activity across hubs, or integrating Ajax user data into other workflows.

Practical example:
You have a security management workflow that needs to fetch all users associated with a particular hub to verify access rights before triggering an alert or logging an event.

Properties

Name Meaning
User Id The unique identifier of the user for whom the bound users list will be retrieved.
Hub Id The unique identifier of the hub from which to get the list of bound users.
Additional Fields Optional additional parameters; currently supports: Enrich (boolean) to enrich output.
  • Enrich: When set to true, the response may include more detailed information about each bound user.

Output

The node outputs JSON data representing the list of users bound to the specified hub for the given user ID. The structure typically includes user details such as identifiers and possibly enriched metadata if requested.

If binary data were involved, it would represent attachments or files related to users, but this node focuses on JSON user data only.

Dependencies

  • Requires an API key credential for authenticating with the Ajax API.
  • The node depends on internal backend modules for HTTP communication, state management, and operation resolution.
  • No additional external services beyond the Ajax API are required.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Invalid User Id or Hub Id: Verify that the provided IDs exist and are correctly formatted.
  • Network issues: Check connectivity to the Ajax API endpoint.
  • Empty results: If no bound users are returned, confirm that the user is actually bound to the specified hub.
  • Enrich option not working: Confirm that the API supports enrichment for this operation and that the parameter is correctly set.

Links and References

Discussion