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 exposed by the API. In the context of the provided Resource "Object" and Operation "Get Object Media By Id," the node retrieves media data associated with a particular object identified by its ID.

Typical use cases include:

  • Fetching media files (such as images or videos) linked to objects within a company's system.
  • Integrating media retrieval into automated workflows for monitoring, reporting, or further processing.
  • Accessing specific media content by specifying company, object, and media identifiers.

For example, a user might want to automatically download a security camera snapshot (media) related to a monitored object in their facility by providing the relevant IDs.

Properties

Name Meaning
Company Id The unique identifier of the company owning the object.
Object Id The unique identifier of the object from which media is to be retrieved.
Media Id The unique identifier of the specific media item associated with the object to fetch.

These properties are all required inputs when performing the "Get Object Media By Id" operation.

Output

The node outputs JSON data representing the requested media information. While the exact structure is not detailed in the source, it typically includes metadata about the media and possibly a URL or binary reference to the media content itself.

If the media content is returned as binary data, it would be accessible through the node's binary output field, allowing subsequent nodes to process or store the media file directly.

Dependencies

  • Requires an API key credential for authenticating with the Ajax API service.
  • Depends on internal modules handling HTTP requests, state management, and operation resolution/execution.
  • No additional external services beyond the Ajax API are indicated.

Troubleshooting

  • Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
  • Invalid IDs: Providing incorrect or non-existent Company Id, Object Id, or Media Id will likely result in errors or empty responses.
  • Network issues: Connectivity problems with the Ajax API endpoint can cause request failures.
  • Operation unsupported: If the specified resource-operation combination is not implemented, the node may throw an error indicating fallback or missing method.

To resolve these issues:

  • Double-check input parameters for correctness.
  • Verify API credentials and network connectivity.
  • Consult API documentation for valid resource and operation combinations.

Links and References

Discussion