ffmpeg Node

n8n Node for some Ffmpeg functionality

Actions11

Filters and Effect Actions
- Add Filters
Metadata Actions
- Extract Metadata
RTMP Restreaming Actions
- Start Restream
Transcoding Actions
- Video Transcode
- Audio Transcode
Video Processing Actions

Overview

The node provides functionality related to FFmpeg operations, including RTMP restreaming. Specifically, the "Start Restream" operation under the "RTMP Restreaming" resource allows users to stream a media file or binary media input to a specified RTMP URL. This is useful for live broadcasting scenarios where you want to restream existing media content to an RTMP server, such as streaming a recorded video to platforms like YouTube Live, Twitch, or custom RTMP endpoints.

Practical examples:

Streaming a pre-recorded video file to a live RTMP server.
Restreaming a media file stored in n8n’s binary data to multiple RTMP destinations.
Automating live broadcasts by triggering restreams from workflows.

Properties

Name	Meaning
Media File Input	A valid media URL or the name of the input binary field containing the media file to stream.
RTMP Url	A valid RTMP URL where the media file will be streamed to.

Output

The node outputs JSON data representing the result of the restreaming operation. The exact structure is not detailed in the provided source, but typically it would include status information about the streaming process (e.g., success confirmation, error messages, streaming session details).

If the node supports binary data input for the media file, it likely processes that binary data internally to stream it to the RTMP URL, but no binary output is explicitly described.

Dependencies

Requires an API key credential for FFmpeg-related services (referred generically as "an API key credential").
Depends on FFmpeg functionality accessible via the configured API.
Needs a valid RTMP server URL to stream the media.
The node relies on internal routing logic (router.call(this)) to handle execution, which delegates to specific action modules for each resource and operation.

Troubleshooting

Invalid Media Input: If the media file input is neither a valid URL nor a recognized binary field, the node may fail to start streaming. Ensure the input is correctly specified.
Invalid RTMP URL: Providing an incorrect or unreachable RTMP URL will cause connection failures. Verify the RTMP endpoint is correct and accessible.
Credential Issues: Missing or invalid API credentials for FFmpeg services will prevent the node from functioning.
Streaming Failures: Network issues or server-side problems at the RTMP destination can interrupt streaming. Check network connectivity and RTMP server health.
Error Messages: Errors related to media processing or streaming will typically indicate whether the problem lies with input media, RTMP connection, or API authentication. Review error details to identify the root cause.