Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video processing capabilities using ffmpeg, specifically supporting an operation to extract audio from a video file ("Video To Audio"). It is useful when you want to convert video content into audio format for purposes such as podcast creation, transcription, or audio analysis. For example, you can input a video URL or binary video data and get back an audio file extracted from that video.
Properties
| Name | Meaning |
|---|---|
| Video Input | A valid video URL or the name of the input binary field containing the video to process. |
| Audio Output Name | The name of the output binary field where the extracted audio file will be stored. |
| Video Processing Options | Collection of optional settings: • Audio Codec (string) • Audio Bitrate (number, default 128 kbps) • Audio Channels (number, default 1) |
Output
The node outputs the extracted audio as binary data in the specified output binary field. The json output field typically contains metadata about the processed file or operation status, while the actual audio content is available in the binary property named by the user (default "data"). This allows downstream nodes to access the audio file directly for further processing or storage.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Relies on ffmpeg functionality exposed via an external API or service configured in n8n.
- No additional environment variables are explicitly required based on the static code.
Troubleshooting
- Invalid Video Input: If the video input URL or binary field is incorrect or inaccessible, the node may fail to retrieve or process the video. Ensure the input is valid and accessible.
- Unsupported Audio Codec or Parameters: Providing unsupported audio codec names or invalid bitrate/channel values might cause errors. Use standard codec names and reasonable numeric values.
- Missing API Credential: The node requires a valid API authentication token; missing or invalid credentials will prevent execution.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow data to avoid overwriting important data.