NinjaOneInstall

Overview

This node interacts with the NinjaOne API to retrieve signed URLs for client documents within an organization. Specifically, the "Get Client Document Signed Urls" operation fetches secure, time-limited URLs that allow access to specific client documents without exposing direct file storage paths or requiring additional authentication.

This functionality is useful in scenarios where you need to securely share or display client documents (such as contracts, reports, or invoices) in external systems, emails, or dashboards while maintaining controlled access. For example, a support system could use this node to generate links for clients to view their documents securely.

Properties

Output

The node outputs an array of JSON objects, each containing the response from the NinjaOne API for the requested client document signed URLs. The exact structure depends on the API response but typically includes one or more signed URLs that provide temporary access to the document.

No binary data output is indicated for this operation.

Example output snippet (conceptual):

{
  "signedUrls": [
    "https://signed-url-1",
    "https://signed-url-2"
  ],
  "expiresAt": "2024-12-31T23:59:59Z"
}

Dependencies

• Requires an active NinjaOne API OAuth2 credential configured in n8n.
• The node uses the NinjaOne API endpoint corresponding to organization documents.
• Network connectivity to the NinjaOne API service is necessary.

Troubleshooting

• Missing or invalid Client Document Id: Ensure the provided document ID exists and is correct; otherwise, the API may return errors or empty results.
• Authentication errors: If the OAuth2 credential is missing, expired, or misconfigured, the node will fail to authenticate with the NinjaOne API.
• API rate limits or downtime: Temporary failures might occur if the NinjaOne API enforces rate limits or experiences outages.
• No binary data error: Not applicable here since this operation does not handle binary input.

Common error messages:

• "Unauthorized" or "Invalid credentials": Check and refresh the API authentication token.
• "Not Found" or "Document does not exist": Verify the Client Document Id is valid.
• "Request failed": Inspect network connectivity and NinjaOne API status.

Links and References

• NinjaOne API Documentation (general reference for endpoints and authentication)
• n8n OAuth2 Credential Setup (for configuring API authentication)