← Blog · Guide · 7 min read

How to Automate Video Processing in n8n (No Code Required)

A step-by-step guide to building automated video conversion workflows in n8n using ffpipe — no servers, no FFmpeg knowledge needed.

fT
ffpipe Team
· Updated Apr 14, 2026

Automated video processing in n8n means using the n8n workflow automation platform to convert, compress, resize, or transform video files automatically — without writing code or managing FFmpeg servers. With ffpipe’s native n8n community node, a Google Drive file trigger, and a Slack notification, you can build a fully hands-off video conversion pipeline in under 15 minutes.

Key Takeaways

  • Convert MOV/AVI/WebM to MP4 automatically when files land in Google Drive
  • No FFmpeg installation or command-line knowledge required
  • Free tier: 100 processing minutes/month covers most small teams
  • Setup time: ~15 minutes for the complete workflow

What you’ll build

By the end of this guide, you’ll have an n8n workflow that:

  1. Triggers when a new video is uploaded to Google Drive
  2. Automatically converts it to MP4 (H.264)
  3. Saves the converted file back to a specified folder
  4. Sends a Slack notification with the download link

No servers to manage. No FFmpeg to install. Just blocks in n8n.

Why automate video conversion?

If you’re running any kind of content operation — marketing, course creation, client deliverables — you’ve probably hit this problem: someone uploads a MOV file, a WebM, or an AVI, and now you need it as MP4 for embedding on your website or sharing with clients.

Doing it manually is fine once. But at scale, it’s a time sink. And every time you forget, it creates blockers.

The solution is a simple automation that handles this the moment a file lands.

Prerequisites

  • An n8n instance (cloud or self-hosted)
  • A ffpipe account (free tier works for this guide)
  • Google Drive connected to n8n
  • Optional: Slack connected to n8n

Step 1: Set up the trigger

Add a Google Drive Trigger node to your workflow. Configure it to watch a specific folder for new files.

{
  "event": "fileCreated",
  "folder": "uploads/incoming-videos"
}

You can filter by file type — set it to only trigger on .mov, .avi, .webm files if you want to skip MP4s that are already in the right format.

Step 2: Add the ffpipe node

Install the ffpipe community node from n8n’s Settings → Community Nodes panel. Search for n8n-nodes-ffpipe and install it.

Once installed, add the ffpipe node to your workflow and configure it:

  • Operation: Convert Format
  • Input URL: {{ $json.webContentLink }} (the Google Drive download URL from the trigger)
  • Output Format: MP4 (H.264)
  • Quality: High (1080p)

That’s it. No FFmpeg command syntax. No encoder settings to figure out.

Step 3: Save the output

Add a Google Drive node after ffpipe. Configure it to upload a file from a URL:

  • Operation: Upload file from URL
  • URL: {{ $json.outputUrl }} (the result from ffpipe)
  • Folder: uploads/converted-videos
  • File name: {{ $json.originalName }}_converted.mp4

Step 4: Notify the team

Add a Slack node to send a notification:

✅ Video converted successfully

File: {{ $json.originalName }}
Output: {{ $json.outputUrl }}
Duration: {{ $json.processingTime }}s

What else can you do?

This same pattern works for dozens of use cases:

Frequently asked questions

Does this work on n8n Cloud or only self-hosted?

This works on both. The ffpipe community node uses HTTP API calls, so no FFmpeg binary is needed on the n8n server. n8n Cloud users can run video processing workflows without any server-side dependencies.

How many processing minutes does a typical video use?

One minute of input video uses approximately one minute of ffpipe processing quota. A 5-minute video conversion uses 5 processing minutes. The free tier includes 100 minutes/month.

What video formats can ffpipe convert from?

Any format FFmpeg supports — MOV, AVI, MKV, WebM, WMV, FLV, MPEG, and dozens more. Output is typically H.264 MP4, the most widely compatible format for web and mobile.

Glossary

  • n8n: An open-source workflow automation platform (similar to Zapier) that connects apps and services via visual node-based workflows.
  • Community node: A third-party n8n extension (like n8n-nodes-ffpipe) installed from Settings → Community Nodes.
  • H.264 MP4: The most common video codec and container format, compatible with virtually all browsers, devices, and platforms.

Ready to automate your video processing? Start free →

Processing minutes: what to expect

The Free tier includes 100 minutes/month. A typical 5-minute video conversion uses 5 minutes of quota. For a team processing 20 videos/week, the Starter plan ($19/month, 2,000 minutes) is more than enough.

Summary

Video processing automation used to require DevOps knowledge and cloud infrastructure. With n8n + ffpipe, it’s a 15-minute setup that runs forever without maintenance.

Get started with ffpipe free →