Ajax icon

Ajax

Consume Ajax API (v.0.1.2)

Actions242

Overview

The node named "Ajax" is designed to interact with a comprehensive Ajax API, supporting multiple resources and operations. Specifically, for the Resource "Hub" and Operation "Delete Hub Logs," this node allows users to delete logs associated with a particular hub and user. This functionality is useful in scenarios where log data needs to be managed or purged for maintenance, privacy compliance, or troubleshooting purposes.

Practical examples include:

  • Removing outdated or irrelevant logs from a specific hub to free up storage.
  • Deleting logs related to a user’s activity on a hub for privacy reasons.
  • Automating log cleanup as part of a scheduled maintenance workflow.

Properties

Name Meaning
User Id The unique identifier of the user whose hub logs are to be deleted. (Required)
Hub Id The unique identifier of the hub from which the logs will be deleted. (Required)

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. The exact structure depends on the Ajax API response but generally includes status indicators and possibly metadata about the deleted logs.

No binary data output is indicated by the source code.

Dependencies

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

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials can cause authentication failures.
    • Providing incorrect or non-existent User Id or Hub Id may result in errors or no action.
    • Network connectivity issues could prevent communication with the Ajax API.
  • Error Messages:

    • Authentication errors typically indicate problems with the provided API key; verify and update credentials.
    • Validation errors may occur if required properties (User Id, Hub Id) are missing or malformed; ensure these fields are correctly filled.
    • API response errors should be checked for detailed messages indicating the cause, such as permission issues or resource not found.

Links and References

Discussion