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 managing groups. Specifically, for the "Group" resource and the "Delete Group" operation, the node allows users to delete a specified group within a given hub and user context.

Common scenarios where this node is beneficial include:

  • Automating the removal of groups from an Ajax security system.
  • Integrating group management into broader workflows, such as user or hub maintenance.
  • Cleaning up unused or obsolete groups programmatically.

For example, a security administrator could use this node to automatically delete groups that are no longer needed when a user leaves an organization or when a hub is decommissioned.

Properties

Name Meaning
User Id The identifier of the user who owns or manages the group.
Hub Id The identifier of the hub where the group exists.
Group Id The identifier of the group to be deleted.

All three properties are required to perform the deletion operation.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of successful deletion or details about any errors encountered.

If the node supports binary data output, it is not evident from the provided code snippet; thus, the output is primarily JSON-based.

Dependencies

  • Requires an API key credential for authenticating with the Ajax API.
  • Depends on internal backend modules for HTTP communication, state management, and operation execution.
  • The node uses external packages related to response-operation resolution and execution patterns.
  • No additional environment variables or configurations are explicitly required beyond providing valid credentials.

Troubleshooting

  • Common Issues:

    • Missing or invalid User Id, Hub Id, or Group Id will prevent successful deletion.
    • Invalid or expired API credentials will cause authentication failures.
    • Network connectivity issues may lead to request timeouts or failures.
  • Error Messages:

    • Authentication errors typically indicate problems with the provided API key credential.
    • Resource not found errors suggest that the specified group, hub, or user does not exist.
    • Permission denied errors imply insufficient rights to delete the group.
  • Resolutions:

    • Verify all input IDs are correct and correspond to existing entities.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network connectivity and retry if transient errors occur.

Links and References

Discussion