Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides functionality related to media file processing using ffmpeg. Specifically, for the "Metadata" resource and the "Extract Metadata" operation, it extracts metadata information from a given media file. This can be useful in scenarios where you need to analyze or retrieve details about media files such as videos or audio clips, including codec information, duration, resolution, bitrate, and other embedded metadata.
Practical examples include:
- Automatically extracting video properties before further processing.
- Retrieving audio track details for cataloging or validation.
- Getting metadata to conditionally branch workflows based on media attributes.
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 from the provided media file. This typically includes detailed technical information about the media such as format, streams, codecs, duration, bitrates, and other relevant metadata fields.
If the input is provided as binary data, the node processes that media content directly. The output does not include binary data but rather structured metadata information in JSON format.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on the external ffmpeg processing backend accessible via the configured API.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid media input: If the media URL or binary field name is incorrect or inaccessible, the node will fail to extract metadata. Ensure the input points to a valid media file.
- Authentication errors: Missing or invalid API credentials will prevent the node from communicating with the ffmpeg service.
- Unsupported media formats: Some media types might not be supported by the ffmpeg backend, resulting in incomplete or failed metadata extraction.
- Timeouts or network issues: Since the node relies on an external service, network problems can cause execution failures.
To resolve these issues:
- Verify the media input is correct and accessible.
- Confirm API credentials are properly set up in n8n.
- Check the media format compatibility with ffmpeg.
- Ensure stable network connectivity.