Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
The node provides functionality related to FFmpeg operations, including RTMP restreaming. Specifically, the "Start Restream" operation under the "RTMP Restreaming" resource allows users to stream a media file to a specified RTMP URL. This is useful for live broadcasting scenarios where you want to take an existing media source (either from a URL or binary input) and push it to a streaming server or platform that accepts RTMP streams.
Practical examples include:
- Streaming a prerecorded video file to a live streaming service.
- Restreaming content from one RTMP source to another destination.
- Broadcasting media files stored in n8n workflows to platforms like YouTube Live, Twitch, 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. While the exact structure is not detailed in the provided code, typically this would include status information such as success confirmation, error messages if any, and possibly metadata about the streaming session.
If the node supports binary data output (e.g., processed media files), it would be included in the output's binary fields, but this is not explicitly shown here.
Dependencies
- Requires an API key credential for FFmpeg-related services (referred generically as an API authentication token).
- The node depends on internal modules handling routing and specific actions like restreaming, transcoding, filtering, etc.
- No external environment variables are explicitly mentioned, but proper configuration of the FFmpeg API credentials within n8n 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 malformed RTMP URL will cause connection failures. Verify the RTMP endpoint format and credentials if required by the streaming server.
- Credential Issues: Missing or invalid API authentication tokens will prevent the node from executing FFmpeg operations. Confirm that the API key credential is correctly set up in n8n.
- Timeouts or Network Errors: Streaming requires stable network connectivity. Network interruptions can cause errors during restreaming.
- Error Messages: The node may throw errors related to FFmpeg processing or connection issues. Review error details in the execution logs to identify the root cause.
Links and References
- FFmpeg Official Documentation
- RTMP Protocol Overview
- n8n Documentation (for general node usage and credential setup)