VideoDBInstall

Overview

This node integrates with the VideoDB API to retrieve information about video collections and their contents. Specifically, the "List Scene Indexes" operation fetches scene index data for a specified video within a collection. This is useful for workflows that need to analyze or process video metadata, such as generating video summaries, indexing scenes for search, or automating video content management.

Practical examples include:

• Automatically retrieving scene indexes to create chapter markers in a video player.
• Using scene data to trigger actions at specific points in a video during playback.
• Aggregating scene metadata for video analytics or content tagging.

Properties

The options for these properties are dynamically loaded from the VideoDB API:

• Collections are fetched from the /collection endpoint.
• Videos are fetched based on the selected collection from the /video endpoint.

Output

The node outputs JSON data containing the response from the VideoDB API for the requested scene indexes. The structure of the output JSON corresponds directly to the API's response format for scene indexes, typically including details such as scene timestamps, descriptions, and other metadata relevant to each scene in the video.

No binary data output is produced by this operation.

Example output JSON (simplified):

{
  "data": {
    "sceneIndexes": [
      {
        "startTime": "00:00:10",
        "endTime": "00:00:30",
        "description": "Opening scene"
      },
      {
        "startTime": "00:00:31",
        "endTime": "00:01:00",
        "description": "Introduction"
      }
    ]
  }
}

Dependencies

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

Troubleshooting

• Missing or invalid API key: Ensure that the API key credential is correctly configured and has the necessary permissions.
• Empty collection or video lists: Verify that the specified collection ID exists and contains videos; otherwise, the dropdowns will be empty.
• Network errors or timeouts: Check network connectivity and API availability.
• Invalid IDs: If specifying IDs manually, ensure they are correct and correspond to existing resources in VideoDB.
• Unexpected API responses: Confirm that the VideoDB API version matches the node's expectations and that the API has not changed.

Links and References

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