Actions37
- Index Spoken Words
- Get Transcript
- Search in a Video
- Generate Stream
- Index Scenes
- List Scene Indexes
- Get Scene Index
- Delete Scene Index
- Add Subtitle
- Generate Audio URL
- Generate Image URL
- Create Collection
- Download
- Get Collection
- Update Collection
- YouTube Search
- Delete Audio
- Delete Image
- Delete Video
- Delete Collection
- Dub Video
- Generate Image
- Generate Music
- Generate Sound Effect
- Generate Voice
- Generate Video
- Generate Text
- Get Audio
- Get Audios
- Get Image
- Get Images
- Get Video
- Get Videos
- Search in a Collection
- Upload
- Record Meeting
- Get Meeting
Overview
This node integrates with the VideoDB API to perform various operations related to video, audio, image, and collection management. Specifically, the "Generate Audio URL" operation allows users to generate a direct URL for an audio file stored within a specified collection in VideoDB. This is useful when you want to retrieve or share audio content programmatically without manually navigating the VideoDB interface.
Common scenarios include:
- Automating retrieval of audio URLs for use in multimedia projects.
- Integrating audio assets into workflows that require direct access links.
- Managing large collections of audio files by dynamically fetching their URLs.
Example: You have a collection of podcast episodes stored in VideoDB. Using this node, you can automatically generate URLs for each episode's audio file to embed them in a website or send them via email.
Properties
| Name | Meaning |
|---|---|
| Collection Name or ID | Select or specify the collection containing the audio files. Options are loaded dynamically from your VideoDB account. |
| Audio Name or ID | Select or specify the specific audio file within the chosen collection. Options depend on the selected collection. |
Output
The node outputs an array with one item per input item processed. Each output item contains a json field holding the response from the VideoDB API for the requested operation.
For the "Generate Audio URL" operation, the json output includes the generated audio URL and any associated metadata returned by the API. The exact structure depends on the API response but typically includes fields such as the audio URL string and possibly additional details like expiration time or format.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the VideoDB API.
- The base URL for the API defaults to
https://api.videodb.iobut can be customized via credentials. - Uses HTTP requests with authentication to communicate with the VideoDB service.
Troubleshooting
- Missing or invalid API key: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Invalid collection or audio ID: Verify that the selected collection and audio IDs exist and belong to your VideoDB account.
- Network issues or API downtime: Check your network connection and VideoDB service status if requests fail.
- Empty options lists: If the dropdowns for collections or audios do not populate, confirm that your API key is valid and that you have collections/audios available in your account.
Common error messages usually come from the API and may indicate unauthorized access, resource not found, or bad request. Resolving these typically involves checking credentials, input parameters, and API usage limits.
Links and References
- VideoDB API Documentation (assumed official docs)
- n8n Expressions Documentation - for using expressions in property fields