Zapier Integration
Connect RenderIO to Zapier for no-code video processing automation.
Zapier Integration
RenderIO has a native Zapier app that lets you add cloud video processing to any Zap without writing code. For use cases and examples, see the FFmpeg Zapier integration overview. Submit FFmpeg commands, monitor their status, and react to completed jobs using triggers and actions.
Available triggers
Triggers start a Zap when something happens in RenderIO.
| Trigger | Description |
|---|---|
| Command Completed | Fires when an FFmpeg command finishes processing (either SUCCESS or FAILED). Uses webhooks for real-time delivery. |
The Command Completed trigger delivers the full command payload, including command_id, status, output_files with download URLs, processing times, and any metadata you attached to the command.
Available actions
Actions let you perform operations in RenderIO from any Zap.
| Action | Description |
|---|---|
| Run FFmpeg Command | Submit a single FFmpeg command with input files, output files, and the FFmpeg command string. Returns a command_id. |
| Run Chained Commands | Submit up to 10 sequential FFmpeg commands that share a single sandbox. Outputs from earlier steps are available as inputs to later steps. |
| Get Command Status | Retrieve the current status and results of a command by command_id. Use this to poll for completion in multi-step Zaps. |
| Upload File | Upload a file to RenderIO storage and receive a file_id and storage URL. |
| Store File from URL | Provide a public URL and RenderIO downloads and stores the file. Returns a file_id and storage URL. |
Setup
Step 1: Find the RenderIO app
- Log in to Zapier
- Create a new Zap or edit an existing one
- Search for RenderIO in the app search
Step 2: Connect your account
- Click Sign in to RenderIO
- Enter your API key (the
ffsk_prefixed key from your RenderIO dashboard) - Zapier validates the key and saves the connection
You can manage connected accounts in My Apps on Zapier.
Step 3: Choose a trigger or action
Select the trigger or action you need from the list above and configure its fields. Zapier provides a form-based interface for each -- no JSON or code required.
For the Run FFmpeg Command action, you fill in:
| Field | Description |
|---|---|
| Input Files | A mapping of alias names (e.g. in_video) to source URLs |
| Output Files | A mapping of alias names (e.g. out_video) to output filenames |
| FFmpeg Command | The FFmpeg command string with {{alias}} placeholders |
| Max Run Seconds | Optional. Maximum processing time in seconds (default: 300) |
| Metadata | Optional. Key-value pairs to attach to the command |
Example Zap: Google Drive to Dropbox conversion
Automatically convert new video files uploaded to Google Drive into MP4 format and save them to Dropbox.
Trigger: Google Drive -- New File in Folder
Action 1: RenderIO -- Run FFmpeg Command
| Field | Value |
|---|---|
| Input Files | in_video = (Google Drive file URL from trigger) |
| Output Files | out_video = converted.mp4 |
| FFmpeg Command | ffmpeg -i {{in_video}} -c:v libx264 -preset fast -c:a aac {{out_video}} |
Action 2: RenderIO -- Get Command Status
| Field | Value |
|---|---|
| Command ID | (command_id from Action 1) |
Use a Delay step before this action to give the command time to process, or use a multi-step Zap with a loop.
Action 3: Dropbox -- Upload File
| Field | Value |
|---|---|
| File URL | (storage_url from Action 2 output_files) |
| Folder | /Converted Videos |
| File Name | converted.mp4 |
Example Zap: command completed notification
Send an email whenever a RenderIO command finishes processing.
Trigger: RenderIO -- Command Completed
This trigger fires in real time using RenderIO webhooks. Zapier registers the webhook URL automatically when you enable the Zap.
Action: Gmail -- Send Email
| Field | Value |
|---|---|
| To | team@yourcompany.com |
| Subject | RenderIO: Command {{ command_id }} {{ status }} |
| Body | Your FFmpeg command has completed with status {{ status }}. Download your file: {{ output_files.out_video.storage_url }} |
You can replace Gmail with Slack, Microsoft Teams, or any other notification service available on Zapier.
Tips
Use the Command Completed trigger for real-time workflows. The trigger uses webhooks behind the scenes, so your Zap runs immediately when a command finishes. This is faster and more efficient than polling with Get Command Status.
Use multi-step Zaps for submit-wait-download flows. If you need to submit a command and use the output in the same Zap, add a Delay step (1--5 minutes depending on your typical processing time) between the Run FFmpeg Command action and the Get Command Status action.
Attach metadata to track jobs. Include a metadata field with identifiers from your system (e.g. order_id, project_name). The metadata comes back in the Command Completed trigger and poll responses, making it easy to route results in downstream Zap steps.
Use Store File from URL for external sources. If your input files are behind authentication or need preprocessing, use the Store File from URL action first to get a RenderIO storage URL, then pass that URL into the Run FFmpeg Command action.
Combine with Zapier Paths for error handling. After a Get Command Status action, add a Paths step to branch on status. Route SUCCESS results to your delivery step and FAILED results to an error notification or retry step.
Other integration platforms
RenderIO also works with n8n, Pipedream, and Make.
Further reading
- Zapier Video Processing Guide -- complete Zap setup for video processing
- Zapier FFmpeg Integration -- using FFmpeg commands through Zapier
- Extract Audio from Video in Zapier -- simple audio extraction Zap