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 existing media 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 another RTMP endpoint.
- Broadcasting media content stored in n8n workflows to social media platforms or custom 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.
Dependencies
- Requires an API key credential for ffmpeg-related operations (generic API authentication token).
- Depends on ffmpeg functionality exposed via an internal router and action modules for restreaming.
- No external environment variables are explicitly 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 restreaming will fail. Ensure the media source is valid and reachable.
- Invalid RTMP URL: Providing an incorrect or unreachable RTMP URL will cause connection errors. Verify the RTMP endpoint and credentials if required.
- API Authentication Errors: Missing or invalid API key credentials will prevent the node from executing ffmpeg operations.
- Network Issues: Network connectivity problems between n8n and the RTMP server can cause streaming failures.
- Error Messages: Common errors might include connection timeouts, unsupported media formats, or permission denied errors on the RTMP server. Check logs and verify all inputs.