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 redistribute live or prerecorded media content to streaming platforms that accept RTMP input, such as YouTube Live, Twitch, or custom streaming servers.
Practical examples include:
- Restreaming a recorded video file to a live streaming platform.
- Redirecting a live stream from one source to multiple RTMP endpoints.
- Broadcasting media content stored in n8n workflows to external RTMP servers.
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, but this is not confirmed by the static analysis.
Dependencies
- Requires an API key credential for the ffmpeg-related service (referred generically as "an API key credential").
- Depends on ffmpeg functionality exposed via internal routing (
./routerand./action/Restreammodules). - No explicit external environment variables are mentioned, but proper configuration of the RTMP server and network access is necessary.
Troubleshooting
- Invalid Media Input: If the media file input URL or binary field name is incorrect or inaccessible, the node may fail to start streaming. Verify the input media source is valid and reachable.
- Invalid RTMP URL: Providing an incorrect or unreachable RTMP URL will cause connection failures. Ensure the RTMP URL is correct and the target server is accepting connections.
- Credential Issues: Missing or invalid API authentication credentials will prevent the node from functioning. Confirm that the required API key credential is configured properly.
- Network Connectivity: Streaming requires stable network connectivity. Network issues can cause interruptions or failures.
- Error Messages: Errors related to ffmpeg processing or streaming will typically indicate the nature of the failure (e.g., unsupported media format, connection refused). Review error details to adjust inputs or configurations accordingly.