AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node interacts with the AvantGuard NinjaOne API to retrieve signed URLs for attachments related to specific knowledge base articles. Specifically, the "Get Related Item Attachments Signed Urls" operation fetches secure, time-limited URLs that allow access to attachments linked to a given entity within the knowledge base system.

This functionality is useful when you want to programmatically access or share attachments associated with various entities such as organizations, documents, locations, nodes, checklists, or knowledge base documents without exposing direct file paths or requiring additional authentication.

Practical examples:

  • Automatically generating download links for attachments related to a particular knowledge base document.
  • Integrating attachment access into custom dashboards or portals where users can view or download files securely.
  • Syncing attachments from the knowledge base to other systems by first obtaining their signed URLs.

Properties

Name Meaning
Entity Type The type of entity whose related item attachments' signed URLs you want to retrieve. Options: ORGANIZATION, DOCUMENT, LOCATION, NODE, CHECKLIST, KB DOCUMENT
Entity Id The unique numeric identifier of the entity specified in "Entity Type" for which to get attachments' signed URLs

Output

The node outputs JSON data containing the signed URLs for the attachments related to the specified entity. Each item in the output typically includes metadata about the attachment along with a signed URL that grants temporary access to the file.

If the node supports binary data output (not explicitly shown here), it would represent the actual attachment content or file streams. However, based on the provided code and operation, the main output is JSON with signed URLs rather than raw binary data.

Dependencies

  • Requires an API key credential for AvantGuard NinjaOne to authenticate requests.
  • Needs the base URL of the AvantGuard NinjaOne API configured in the credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building properties and handling OpenAPI integration.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Providing an incorrect or non-existent Entity Id may result in empty results or errors.
    • Selecting an unsupported Entity Type or mismatching Entity Id and Entity Type could lead to no data returned.
  • Error messages:
    • Authentication errors usually indicate invalid API keys or misconfigured credentials.
    • "Not Found" or similar errors suggest the specified entity does not exist.
    • Network or timeout errors may occur if the API endpoint is unreachable; verify network connectivity and base URL configuration.

Links and References

Discussion