VideoDB icon

VideoDB

Interact with the VideoDB API

Overview

This node integrates with the VideoDB API to perform various video-related operations. Specifically, the "YouTube Search" operation allows users to search for YouTube videos within a specified collection by providing a search query and filtering options such as video duration and result count.

Common scenarios where this node is beneficial include:

  • Automating video content curation by searching and retrieving relevant YouTube videos from predefined collections.
  • Building workflows that require fetching video metadata based on user queries.
  • Integrating video search capabilities into larger automation pipelines for content management or marketing.

For example, a user can specify a collection of educational videos and search for "JavaScript tutorials" limited to short videos, retrieving up to 5 results automatically.

Properties

Name Meaning
Collection Name or ID Choose a video collection from a list or specify its ID. This defines the scope of the search.
Query The search term or phrase used to find matching YouTube videos within the selected collection.
Result Threshold The maximum number of search results to return (e.g., 5).
Duration Filter videos by length: Short, Medium, or Long.

Output

The node outputs an array of JSON objects, each representing the response from the VideoDB API for the YouTube search request. Each item in the output contains the full JSON response data returned by the API, which typically includes details about the matched videos such as titles, IDs, durations, and other metadata.

No binary data output is produced by this node.

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 the necessary permissions.
  • Collection not found or empty: Verify that the specified collection ID or name exists and contains videos.
  • Network issues or API downtime: Check network connectivity and the status of the VideoDB API service.
  • Incorrect property values: Make sure required properties like "Query" and "Collection Name or ID" are provided and valid.
  • Unexpected API responses: Review the API documentation and ensure the node's parameters align with expected API inputs.

Links and References

Discussion