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.
- Redirecting a media stream from one source to multiple RTMP endpoints.
- Broadcasting media content stored in n8n workflows to social media platforms supporting RTMP ingestion.
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), it would likely represent processed media files or streaming logs.
Dependencies
- Requires an API key credential for the underlying ffmpeg-related service (referred generically as "an API key credential").
- Depends on ffmpeg functionality exposed via internal actions and routing modules.
- 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 is neither a valid URL nor a correctly named binary field, the node may fail to start streaming.
- Incorrect RTMP URL: Providing an invalid or unreachable RTMP URL will cause connection errors.
- Credential Issues: Missing or incorrect API authentication credentials will prevent the node from executing.
- Network Connectivity: Ensure the n8n instance has network access to the RTMP server.
- Error Messages: Errors related to ffmpeg processing or streaming failures should be checked in the node execution logs for details.