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 obtain the extracted audio stream in a specified format and quality.
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) — specify the codec for audio encoding. • Audio Bitrate (number) — set the bitrate for the audio stream (default 128 kbps). • Audio Channels (number) — number of audio channels (default 1). |
Output
The node outputs the extracted audio as binary data under the specified output field name. The json output contains metadata about the processed file, while the binary output holds the actual audio file extracted from the input video. This allows downstream nodes to access the audio content 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 within n8n.
- No additional environment variables are explicitly required beyond the API authentication.
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: Specifying an unsupported audio codec might cause errors. Use common codecs supported by ffmpeg.
- Insufficient Permissions: The API key credential must have permissions to perform video processing operations.
- 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.