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. 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 gathering media file properties before processing or transcoding.
- Extracting technical details for cataloging or reporting purposes.
- Validating media files by checking their metadata before further workflow steps.
Example: You provide a URL or binary input of a video file, and the node outputs detailed metadata about that video, which can then be used downstream in your workflow.
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 fields such as format, streams (video/audio), codec information, duration, bitrate, resolution, and other relevant technical details.
If the input was provided as binary data, the node processes this binary content to extract metadata without needing an external URL.
No binary output is produced by this operation; the output is purely JSON metadata describing the media file.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an internal routing mechanism that delegates execution to appropriate handlers based on the selected resource and operation.
- No additional environment variables are explicitly required beyond the API authentication.
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 will prevent the node from functioning. Verify that the API key credential is properly configured.
- Unsupported Media Format: Some rare or proprietary media formats might not be supported by the underlying ffmpeg service, resulting in incomplete or failed metadata extraction.
- Timeouts or Network Issues: When providing URLs, network connectivity problems can cause failures. Check URL accessibility and network status.
Links and References
- FFmpeg Official Documentation – For understanding media metadata and ffmpeg capabilities.
- n8n Documentation – General guidance on using custom nodes and handling binary data in workflows.