Ajax icon

Ajax

Consume Ajax API (v.0.1.2)

Actions242

Overview

This node, named "Ajax," is designed to interact with a comprehensive Ajax API (version indicated in the code). It supports multiple resources and operations, including the "Hub" resource with an operation to "Mute Fire Detectors." The node facilitates sending commands or queries to the Ajax backend system, which manages various smart security devices and configurations.

A practical use case for the "Mute Fire Detectors" operation under the "Hub" resource is to temporarily silence fire alarms across a specified hub. This can be useful during maintenance, false alarm situations, or testing scenarios where muting detectors prevents unnecessary alerts.

Properties

Name Meaning
User Id Identifier of the user performing the mute action; required to authenticate or authorize.
Hub Id Identifier of the specific hub where fire detectors will be muted; required to target the hub.
Mute Type Specifies which fire detectors to mute:
- ALL_FIRE_DETECTORS: Mute all fire detectors in the hub.
- ALL_FIRE_DETECTORS_EXCEPT_TRIGGERED: Mute all except those currently triggered.

Output

The node outputs JSON data representing the result of the mute operation. This typically includes confirmation of success or failure, status messages, and possibly updated states of the affected fire detectors within the hub.

If the node supports binary data output, it would relate to any raw response or logs from the Ajax API, but this is not explicitly shown in the provided code.

Dependencies

  • Requires an API key credential for authenticating with the Ajax API.
  • Depends on internal modules handling HTTP requests, state management, and operation resolution/execution.
  • No additional external services beyond the Ajax API are indicated.
  • Proper configuration of the API credential in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:
    • Missing or invalid API credentials leading to authentication failures.
    • Incorrect or non-existent User Id or Hub Id causing resource not found errors.
    • Invalid "Mute Type" option resulting in rejected requests.
  • Error Messages:
    • Authentication errors suggest checking the API key setup.
    • Resource-related errors indicate verifying that the User Id and Hub Id exist and are correct.
    • Validation errors on input properties require ensuring all required fields are filled with valid values.
  • To resolve issues, verify credentials, confirm input parameters, and consult the Ajax API documentation for permission scopes and endpoint availability.

Links and References


Note: The summary is based solely on static analysis of the provided source code and property definitions without runtime behavior inference.

Discussion