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 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 session.
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-related service or API.
- Depends on ffmpeg functionality exposed via an external API or service configured in n8n.
- The node internally uses a routing mechanism (
router.call(this)) to delegate execution based on resource and operation.
Troubleshooting
- Invalid Media Input: Ensure the media input URL is accessible or the binary field name is correct and contains valid media data.
- Invalid RTMP URL: Verify the RTMP URL format and accessibility; incorrect URLs will cause streaming failures.
- Credential Issues: Confirm that the required API authentication token or key is correctly configured in n8n credentials.
- Streaming Failures: Network issues or server-side problems at the RTMP endpoint can interrupt streaming; check connectivity and server status.
- Error Messages: Errors related to ffmpeg processing or API calls may appear; reviewing logs or enabling debug mode can help identify root causes.