VideoDB icon

VideoDB

Interact with the VideoDB API
Join our community

Actions37

Overview

This node integrates with the VideoDB API to retrieve video-related data from specified collections. The "Get Videos" operation fetches all videos within a chosen collection by its name or ID. This is useful for workflows that need to process, analyze, or display video metadata stored in VideoDB collections.

Practical examples include:

  • Automatically retrieving and listing videos from a curated collection for further processing.
  • Integrating video metadata into content management systems or dashboards.
  • Triggering downstream actions based on video data updates in a specific collection.

Properties

Name Meaning
Collection Name or ID Select a collection from a dropdown list or specify its ID via an expression. The node will fetch videos from this collection.

Output

The node outputs an array of JSON objects where each object contains the raw response from the VideoDB API for the requested videos. The structure corresponds directly to the API's response under the data.videos field, typically including video metadata such as video IDs, names, and other attributes provided by VideoDB.

No binary data output is produced by this operation.

Example output snippet (simplified):

[
  {
    "json": {
      "videos": [
        {
          "id": "video1",
          "name": "Sample Video 1",
          ...
        },
        {
          "id": "video2",
          "name": "Sample Video 2",
          ...
        }
      ]
    }
  }
]

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 HTTP requests authenticated with the provided API key to interact with VideoDB endpoints.

Troubleshooting

  • Missing or invalid API key: The node requires a valid API key credential. Ensure the API key is correctly configured in n8n credentials.
  • Invalid collection ID or name: If the specified collection does not exist or is mistyped, the API may return an error or empty results. Verify the collection exists using the dropdown or correct expression.
  • Network or API errors: Connectivity issues or API downtime can cause request failures. Check network access and VideoDB service status.
  • Empty results: If no videos are returned, confirm that the collection actually contains videos.

Common error messages might include authentication failures or 404 not found errors related to collections. Resolving these usually involves verifying credentials and collection identifiers.

Links and References

Discussion