Run FFmpeg on Rendobar, Save to Google Drive & Slack

Run custom FFmpeg renders on Rendobar, then deliver results to Google Drive and Slack

This n8n workflow accepts a video URL and an FFmpeg command from an n8n form, runs the render on Rendobar, uploads the finished output to Google Drive, and posts a shareable link to Slack. If the job fails, it automatically sends the Rendobar runner logs (FFmpeg error output) to Slack for fast troubleshooting.

What this workflow does

• Collect input via n8n Form Trigger: Receives a submission containing a video URL and an FFmpeg command.
• Start an FFmpeg job on Rendobar: Creates a Rendobar job, passing the video URL as the source input and using the workflow resume URL as the Rendobar callback.
• Wait for completion: Uses the workflow wait behavior until Rendobar calls back when the job completes.
• Fetch and download output: Retrieves the finished job and downloads the rendered output file.
• Upload to Google Drive: Uploads the output to your configured Drive and folder.
• Notify Slack (success): Posts a Google Drive link to a configured Slack channel.
• Notify Slack (failure): Separately listens for Rendobar job.failed events, retrieves job logs, and posts the FFmpeg error output to Slack.

Use cases

• On-demand video transcoding: kick off FFmpeg encodes from a simple form.
• Automated clipping/processing pipelines for SaaS media tools.
• Operational visibility: route render success links and failure logs to Slack for the whole team.

Technical details

• Rendobar nodes: Rendobar job creation, callback/resume handling, and handling job.failed events.
• n8n nodes used: form trigger, wait, google drive, slack, and support via sticky note.
• Setup required: Rendobar API key credentials, Google Drive OAuth (target Drive + folder), and Slack credentials (success + error channels).

When submitting your FFmpeg command, ensure it uses source as the input name and produces output.mp4 (as the workflow expects the rendered filename).