VidNavigator icon

VidNavigator

VidNavigator integration

Overview

The node integrates with the VidNavigator API to perform various video-related operations. Specifically, for the Search Videos operation, it allows users to search a video database using a query string and optional filters such as start year, end year, focus criteria (relevance, popularity, brevity), and limits the number of results returned.

This node is beneficial in scenarios where you want to programmatically find videos matching specific topics or criteria without manually browsing platforms. For example, content creators can quickly gather relevant videos on a subject, researchers can filter videos by publication years, or marketers can find popular videos for trend analysis.

Properties

Name Meaning
Query The search query string to find relevant videos.
Start Year Optional filter to include only videos published from this year onwards.
End Year Optional filter to include only videos published up to this year.
Focus Criteria to prioritize search results by: Relevance, Popularity, or Brevity (shortness).
Max Results Maximum number of video results to return from the search.

Output

The node outputs an array of JSON objects representing the search results returned by the VidNavigator API. Each item contains the raw response data under the json property. The exact structure depends on the API but typically includes video metadata such as titles, descriptions, URLs, publication dates, and possibly relevance scores.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for VidNavigator API authentication.
  • The node makes HTTP POST requests to the VidNavigator API base URL configured in the credentials.
  • Proper network access to the VidNavigator service endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Network connectivity problems may prevent reaching the VidNavigator API.
    • Providing invalid parameter types (e.g., non-numeric years) might cause request errors.
    • Exceeding maximum allowed results or unsupported focus values could lead to API errors.
  • Error Messages:

    • Authentication errors usually indicate incorrect or expired API keys; verify and update credentials.
    • Request timeouts or connection errors suggest network issues; check firewall and internet access.
    • API response errors with messages about invalid parameters require reviewing input values for correctness.

Links and References

Discussion