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 collections, and specifically for the "Generate Voice" operation, it converts text into speech using a selected voice from a collection. It is useful in scenarios where automated voice generation is needed, such as creating voiceovers for videos, generating audio content from text, or adding narration to multimedia projects.
For example, you can input a text string and select a voice to generate an audio file of that text spoken aloud, which can then be used in video editing workflows or accessibility features.
Properties
| Name | Meaning |
|---|---|
| Collection Name or ID | Select or specify the ID of the collection containing the voice resources to use for generation. |
| Text | The text string that will be converted into speech. |
| Voice Name | Choose the voice style for speech synthesis. Options include various American, British, Australian voices with different tones and ages (e.g., Aria, Alice, Bill, Charlotte, etc.). |
| Callback URL | Optional URL to receive asynchronous notifications or callbacks related to the voice generation process. |
Output
The node outputs JSON data representing the response from the VideoDB API after requesting voice generation. This typically includes metadata about the generated audio, such as URLs to access the audio file, status information, or identifiers.
If the node supports binary output (not explicitly shown in the code), it would represent the generated audio file itself, but based on the static analysis, the output is JSON containing the API response.
Dependencies
- Requires an API key credential for authenticating with the VideoDB API.
- The base URL defaults to
https://api.videodb.iobut 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:
- Invalid or missing API key: Ensure the API key credential is correctly configured.
- Incorrect collection ID: Verify the collection exists and the ID is correct.
- Network errors: Check connectivity to the VideoDB API endpoint.
- Unsupported voice name: Use one of the predefined voice options.
Error messages:
- Authentication failures usually indicate invalid or expired API keys.
- 404 errors may mean the specified collection or resource does not exist.
- Validation errors if required parameters like text or collection ID are missing.
Resolving these typically involves verifying credentials, input parameters, and network access.
Links and References
- VideoDB API Documentation (assumed base URL)
- n8n Expressions Documentation: https://docs.n8n.io/code/expressions/ (for dynamic parameter expressions)