Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
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 pre-recorded 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 data output, it would likely represent processed media files or streaming logs, but this is not explicitly shown in the source.
Dependencies
- Requires an API key credential for ffmpeg-related operations (referred generically as "an API key credential").
- Depends on ffmpeg functionality exposed via bundled actions (e.g.,
./action/Restream). - The node internally uses a router mechanism (
router.call(this)) to delegate execution based on resource and operation.
Troubleshooting
- Invalid Media Input: If the media file input URL or binary field name is incorrect or inaccessible, the restreaming will fail. Ensure the media source is valid and reachable.
- Invalid RTMP URL: Providing an incorrect or malformed RTMP URL will cause connection failures. Verify the RTMP endpoint format and credentials if required.
- Credential Issues: Missing or invalid API authentication tokens can prevent the node from executing ffmpeg commands properly.
- Streaming Failures: Network issues or server-side restrictions on the RTMP endpoint may interrupt streaming. Check network connectivity and RTMP server status.
- Common error messages might relate to inability to open input, failure to connect to RTMP server, or unsupported media formats. Resolving these involves validating inputs and ensuring compatibility.