VideoDB icon

VideoDB

Interact with the VideoDB API

Overview

This node integrates with the VideoDB API, allowing users to manage video collections and related media. Specifically, the "Delete Collection" operation enables users to delete an existing collection by specifying its name or ID. This is useful for cleaning up unused or obsolete collections in a video management workflow.

Practical examples include:

  • Automatically removing outdated video collections as part of a content lifecycle automation.
  • Managing collections dynamically based on external triggers or conditions in a media processing pipeline.

Properties

Name Meaning
Collection Name or ID Select a collection from a dropdown list populated with existing collections, or specify an ID manually using an expression. This identifies which collection to delete.

Output

The node outputs a JSON object containing the response from the VideoDB API after attempting to delete the specified collection. The exact structure depends on the API's response but typically includes status information about the deletion request.

No binary data output is produced by this operation.

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

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent collection ID will likely result in an error from the API.
    • Missing or incorrect API authentication token will cause authentication failures.
    • Network connectivity problems may prevent successful API calls.
  • Error messages and resolutions:

    • Authentication errors: Ensure that a valid API key credential is configured and linked to the node.
    • Collection not found: Verify that the collection ID or name exists by using the node’s collection listing feature before attempting deletion.
    • HTTP errors (e.g., 4xx or 5xx): Check API endpoint availability and permissions associated with the API key.

Links and References

Discussion