VideoDB icon

VideoDB

Interact with the VideoDB API

Overview

This node integrates with the VideoDB API, allowing users to retrieve detailed information about video-related data stored in collections. Specifically, the "Get Meeting" operation fetches details of a particular meeting by its ID within a specified collection. This is useful for workflows that need to access or process metadata about meetings stored in VideoDB collections, such as generating reports, syncing meeting data with other systems, or triggering actions based on meeting details.

Practical examples:

  • Automatically retrieving meeting details after a recording is uploaded.
  • Syncing meeting metadata into a CRM or calendar system.
  • Triggering notifications or follow-up tasks based on meeting content.

Properties

Name Meaning
Collection Name or ID Select a collection from the list or specify its ID. The collection groups related videos and meetings.
Meeting ID The unique identifier of the meeting to retrieve details for.

Output

The node outputs JSON data representing the full response from the VideoDB API for the requested meeting. This typically includes all metadata and properties associated with the meeting, such as its name, timestamps, participants, and any other relevant attributes defined by the API.

No binary data output is indicated by the source code.

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

  • Missing or invalid API key: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Invalid Collection or Meeting ID: Verify that the provided IDs exist in the VideoDB account; otherwise, the API will return errors or empty results.
  • Network issues: Check connectivity to the VideoDB API endpoint.
  • Unexpected API responses: Confirm that the API version and endpoint URLs have not changed; update credentials or node configuration accordingly.

Common error messages usually relate to authentication failures or resource not found errors. Resolving these involves checking credentials and input parameters.

Links and References

Discussion