VideoDBInstall

Overview

This node integrates with the VideoDB API to retrieve information about video collections and their contents. Specifically, the "Get Collection" operation fetches details of a specified collection by its name or ID. This is useful for workflows that need to access metadata or organize media assets stored in VideoDB.

Practical examples include:

• Automatically retrieving a video collection's metadata to display or process in downstream nodes.
• Using the collection data to trigger further actions like downloading videos or generating reports.
• Integrating VideoDB collections into content management or publishing pipelines.

Properties

Output

The node outputs JSON data representing the response from the VideoDB API for the requested collection. The structure typically includes collection metadata such as its ID, name, description, and possibly other related attributes depending on the API response.

No binary data output is produced by this operation.

Example output JSON (simplified):

{
  "data": {
    "collections": [
      {
        "id": "collection123",
        "name": "My Video Collection",
        "description": "A sample collection of videos"
        // ... other collection fields
      }
    ]
  }
}

Dependencies

• Requires an API key credential for authenticating with the VideoDB API.
• The base URL for the API defaults to https://api.videodb.io but can be customized via credentials.
• The node uses HTTP requests with authentication to communicate with the VideoDB service.

Troubleshooting

• Invalid or missing API key: Ensure that the API key credential is correctly configured and has sufficient permissions.
• Collection not found: Verify that the collection ID or name provided exists in your VideoDB account.
• Network issues: Check connectivity to the VideoDB API endpoint; firewall or proxy settings might block requests.
• Empty dropdown list for collections: This may indicate authentication failure or no collections available in the account.

Common error messages usually come from the API and might include unauthorized access, resource not found, or bad request errors. Resolving these typically involves checking credentials, input parameters, and network access.

Links and References

• VideoDB API Documentation (hypothetical link)
• n8n Expressions Documentation - for using expressions in property values