VidNavigator icon

VidNavigator

VidNavigator integration

Overview

This node integrates with the VidNavigator API to perform various video-related operations. Specifically, the "Transcribe Video (Non-YouTube)" operation allows users to transcribe videos from any non-YouTube URL into text in a specified language. This is useful for extracting spoken content from videos hosted on other platforms or private servers.

Common scenarios include:

  • Generating subtitles or captions for training videos, webinars, or presentations.
  • Creating searchable text transcripts for video archives.
  • Enabling accessibility by providing text alternatives for video content.

Example: Transcribing a corporate training video hosted on a private server to generate a transcript in English for documentation purposes.

Properties

Name Meaning
Video URL The URL of the non-YouTube video to transcribe. Must be a direct link accessible by the API.
Language ISO2 code of the language spoken in the video (e.g., "en" for English, "fr" for French). Defaults to "en".

Output

The node outputs a JSON object containing the transcription result returned by the VidNavigator API. The structure typically includes fields such as the transcribed text and possibly metadata about the transcription process.

If the transcription is successful, the output JSON will contain the transcription data under the json property of the output item.

The node does not output binary data.

Dependencies

  • Requires an API key credential for the VidNavigator service configured in n8n.
  • The node makes authenticated HTTP POST requests to the VidNavigator API base URL provided in the credentials.
  • The API expects JSON-RPC 2.0 formatted requests.

Troubleshooting

  • Invalid or inaccessible video URL: Ensure the provided video URL is correct, publicly accessible, or accessible by the VidNavigator API backend. Private or restricted URLs may cause errors.
  • Unsupported video format: The API might not support all video formats; verify compatibility.
  • Incorrect language code: Use valid ISO2 language codes to avoid transcription errors or fallback to default language.
  • Authentication errors: Confirm that the API key credential is correctly set up and has necessary permissions.
  • API request failures: Network issues or incorrect base URL configuration can cause request failures. Check connectivity and credential settings.

Common error messages usually come from the API response and should be reviewed in the node's output for details.

Links and References

Discussion