Make.com FFmpeg Integration

Add FFmpeg video processing to any Make.com scenario using the FFmpeg Micro API. No FFmpeg installation, no infrastructure—just HTTP requests that turn your data into finished videos.

Quick start: FFmpeg Micro works as an HTTP module in Make.com. You send a JSON request with your video parameters, and receive a URL to the rendered video. Free tier includes 100 minutes.

How to Add FFmpeg Micro to Make.com

Step 1: Get Your API Key

Sign up at FFmpeg Micro (free tier includes 100 minutes)
Navigate to your dashboard and copy your API key
Keep this key handy—you'll use it in the Make.com HTTP module

Step 2: Add HTTP Module to Your Scenario

Open your Make.com scenario (or create a new one)
Click the + button to add a new module
Search for "HTTP" and select "Make a request"
Configure the module with the settings below

Step 3: Configure the HTTP Request

URL:https://api.ffmpeg-micro.com/v1/transcodes

Method: POST

Headers:

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Request Body (JSON):

{
  "inputs": [
    { "url": "https://example.com/input-video.mp4" }
  ],
  "outputFormat": "mp4",
  "options": [
    { "option": "-s", "argument": "1280x720" },
    { "option": "-c:v", "argument": "libx264" },
    { "option": "-preset", "argument": "fast" }
  ]
}

Use FFmpeg options directly. Map dynamic values from earlier modules in your scenario (e.g., video URL from a Google Drive module).

Step 4: Map Dynamic Data

Map data from previous modules (Airtable, Google Sheets, webhooks, etc.) into your request:

Video URL: Map the inputs[0].url to a file URL from Dropbox, Google Drive, or any HTTP source
FFmpeg options: Use any FFmpeg flag as an option — resize, trim, add text overlays, change codecs
Output format: Set outputFormat to "mp4", "webm", or "mov"

Step 5: Use the Response

FFmpeg Micro returns a JSON response with the job ID and status:

{
  "id": "abc123-def456",
  "status": "pending",
  "inputUrl": "https://example.com/input-video.mp4",
  "outputFormat": "mp4",
  "downloadToken": "xyz789"
}

Poll GET /v1/transcodes/{id} until status is "completed", then use the output_url in your next step: upload to social media, send in an email, save to cloud storage, or trigger a webhook.

Or use GET /v1/transcodes/{id}/download to get a signed download URL.

Example Make.com Scenarios

Airtable → Video Generator

Trigger: New record in Airtable → FFmpeg Micro HTTP request → Upload to Dropbox

Use case: Team submits product updates in Airtable, Make automatically generates branded video clips

Google Drive File Watcher → Multi-Format Export

Trigger: New file in folder → FFmpeg Micro (resize 3 times) → Save 3 versions back to Drive

Use case: Upload one video, get Shorts (9:16), YouTube (16:9), and Instagram (1:1) versions automatically

Webhook → Caption Burner

Trigger: Webhook receives video URL + transcript → FFmpeg Micro adds captions → Return URL via API

Use case: Integrate video captioning into your own app without running FFmpeg yourself

Common FFmpeg Options

Resize: {"option": "-s", "argument": "1080x1920"}

Video codec: {"option": "-c:v", "argument": "libx264"}

Quality (CRF): {"option": "-crf", "argument": "23"}

Trim video: {"option": "-ss", "argument": "5"}, {"option": "-t", "argument": "25"}

Output format: Set outputFormat to "mp4", "webm", or "mov"

See the full API documentation for all available operations and parameters.

Why Use FFmpeg Micro vs. Self-Hosting?

No FFmpeg installation or server maintenance
Automatic scaling—handles 1 video or 1,000 videos without configuration
Pay only for processing time used (free tier: 100 minutes)
Works in any Make.com scenario as a simple HTTP request
Built-in error handling and retry logic