ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality

Actions11

Overview

The node provides functionality to start RTMP restreaming of a media file. It takes an input media source (either a URL or a binary media file) and streams it to a specified RTMP URL. This is useful in scenarios where you want to broadcast or redistribute live or prerecorded media content to streaming platforms that accept RTMP input, such as YouTube Live, Twitch, or custom streaming servers.

Practical examples:

  • Restream a recorded video file to a live streaming platform.
  • Redirect a live stream from one source to multiple RTMP endpoints.
  • Automate streaming workflows by integrating with other n8n nodes for media processing before restreaming.

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 code, but typically it would include status information about the streaming process, such as success confirmation, error messages if any, or metadata about the stream.

If the node supports binary output (not explicitly shown here), it would likely represent processed media files or streaming logs.

Dependencies

  • Requires an API key credential for the underlying ffmpeg service or API to perform the restreaming.
  • The node depends on an external ffmpeg-based service or library capable of handling RTMP streaming.
  • Proper network access to the RTMP destination URL is necessary.
  • No explicit environment variables are mentioned, but typical usage requires configuring credentials securely within n8n.

Troubleshooting

  • Invalid Media Input: If the media input URL or binary field is invalid or inaccessible, the node will fail to start streaming. Ensure the media source is reachable and correctly specified.
  • Invalid RTMP URL: Providing an incorrect or unreachable RTMP URL will cause connection failures. Verify the RTMP endpoint and credentials if required.
  • Credential Issues: Missing or incorrect API authentication tokens will prevent the node from executing. Confirm that the API key credential is properly configured.
  • Network Restrictions: Firewalls or network policies blocking outbound RTMP connections can cause errors.
  • Error Messages: Common errors might include connection timeouts, unsupported media formats, or permission denied errors on the RTMP server. Review logs or output messages for details.

Links and References

Discussion