Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides functionality related to media files using ffmpeg capabilities. Specifically, for the "Metadata" resource with the "Extract Metadata" operation, it extracts metadata information from a given media file input. This is useful when you want to analyze or retrieve details such as codec, duration, format, resolution, or other embedded metadata from audio or video files.
Common scenarios include:
- Automatically extracting media metadata for cataloging or indexing.
- Validating media properties before processing or transcoding.
- Gathering technical details for reporting or quality control.
Example: You provide a URL or binary field containing a video file, and the node outputs detailed metadata about that video.
Properties
| Name | Meaning |
|---|---|
| Media File Input | A valid media URL or the name of the input binary field containing the media file to analyze |
Output
The node outputs JSON data containing the extracted metadata of the provided media file. This typically includes technical details such as codec information, duration, bit rate, format, streams info (audio/video), resolution, and other relevant metadata fields.
If the input was provided as binary data, the output will still be JSON metadata describing that media content. The node does not output binary media data itself in this operation.
Dependencies
- Requires an API key credential for accessing ffmpeg-related services.
- Depends on ffmpeg functionality exposed via an external service or integration configured within n8n.
- The node expects either a URL or binary data input representing the media file.
Troubleshooting
- Invalid media input: If the media URL is invalid or the binary field does not contain a proper media file, the node may fail to extract metadata. Ensure the input is correct and accessible.
- Authentication errors: Missing or incorrect API credentials can cause failures. Verify that the required API key or authentication token is properly configured.
- Unsupported media formats: Some media types might not be supported by the underlying ffmpeg service, leading to incomplete or failed metadata extraction.
- Timeouts or network issues: When providing URLs, ensure the media source is reachable and responsive.