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 for scenarios where you want to broadcast or restream video content to live streaming platforms or servers that accept RTMP streams.
Practical examples include:
- Restreaming a prerecorded video file to a live streaming service.
- Broadcasting a media file stored in n8n’s binary data to an RTMP server.
- Automating live stream startups by triggering this node with dynamic inputs.
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, and possibly metadata about the stream.
If the node handles binary data input, it means it can accept media files directly from previous nodes in binary form, but the output is focused on JSON status/result rather than streaming binary data out.
Dependencies
- Requires an API key credential for ffmpeg-related operations (referred generically as "an API key credential").
- Depends on internal modules handling routing and actions related to RTMP restreaming.
- No external environment variables are explicitly mentioned, but proper configuration of the RTMP destination and media input is necessary.
Troubleshooting
- Invalid Media Input: If the media file input is neither a valid URL nor a correctly named binary field, the node may fail to start streaming. Ensure the input is correct and accessible.
- 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 invalid API authentication tokens will prevent the node from executing properly.
- Streaming Failures: Network issues or server-side problems at the RTMP destination can interrupt streaming. Check connectivity and server logs.
- Common error messages likely relate to input validation, connection errors, or ffmpeg processing failures. Reviewing these messages and verifying inputs usually resolves issues.