ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality

Actions11

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 as output, optionally customizing audio codec, bitrate, and channels.

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 in a binary field named as specified by the "Audio Output Name" property. The json output contains metadata about the processed file, while the binary data 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.
  • The node depends on ffmpeg functionality exposed via an external API or service configured in n8n.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Invalid Video Input: If the video URL is invalid or the binary input field does not contain proper video data, the node may fail to extract audio. Ensure the input is correctly specified 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.
  • API Authentication Errors: Missing or incorrect API credentials will prevent the node from functioning. Verify that the API key credential is properly configured.
  • Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting data unintentionally.

Links and References

Discussion