VideoDB icon

VideoDB

Interact with the VideoDB API
Join our community

Actions37

Overview

This node integrates with the VideoDB API to manage media assets such as videos, audios, and images within collections. The "Upload" operation allows users to upload a media file by specifying its URL along with metadata like name, description, and media type. This is useful for automating media management workflows, such as adding new content to a video library or syncing media assets from external sources.

Practical examples include:

  • Automatically uploading newly created videos from a content creation platform into a VideoDB collection.
  • Adding audio files from an external source URL to a specific audio collection.
  • Uploading images to a gallery collection for further processing or sharing.

Properties

Name Meaning
Collection Name or ID Select or specify the target collection where the media will be uploaded.
URL The direct URL of the media file to upload.
Media Type The type of media being uploaded. Options: Video, Audio, Image.
Name Optional name to assign to the uploaded media.
Description Optional description providing details about the media.
Callback URL Optional URL to receive callbacks or notifications related to the upload process.

Output

The node outputs JSON data representing the response from the VideoDB API after the upload operation. This typically includes details about the uploaded media item such as its ID, status, and metadata. The output does not include binary data; it only contains structured JSON information returned by the API.

Example output structure (simplified):

{
  "data": {
    "id": "media-id",
    "name": "Media Name",
    "description": "Description text",
    "media_type": "video",
    "url": "https://...",
    "status": "uploaded"
  }
}

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 Collection ID: If the specified collection does not exist or is invalid, the API may return an error. Verify the collection ID or select from the dynamically loaded list.
  • Authentication Errors: Missing or incorrect API key will cause authentication failures. Ensure the API key credential is correctly configured.
  • Invalid Media URL: The URL must point directly to a valid media file accessible by the VideoDB API. Check that the URL is correct and publicly reachable.
  • Unsupported Media Type: Only "video", "audio", and "image" are supported media types. Using other values will result in errors.
  • Callback URL Issues: If provided, ensure the callback URL is valid and able to receive incoming requests.

Common error messages usually originate from the API and indicate issues such as unauthorized access, resource not found, or validation errors on input parameters.

Links and References

Discussion