When a file in Frame.io is marked as Approved, this Zap automatically uploads it to a designated Google Drive folder.
What you'll need
A Frame.io V4 account
A Zapier account
A Google Drive account with edit access to the destination folder
Set up the Zap
Step 1: Open the template
Click the button below
When the template opens, the guided setup wizard will launch automatically. Before exiting, confirm the Zap has been given a name and saved to the desired folder location. Then click Cancel, then Close setup to exit. Your Zap is saved and you can continue in the Zap editor.
Step 2: Connect your accounts
Frame.io: Select the account associated with the workspace you want to monitor.
Google Drive: Select the account where approved files should be uploaded. Make sure it has edit access to your destination folder.
Step 3: Configure the Frame.io trigger and fire a test
Select your Frame.io Account and Workspace. The trigger watches the entire workspace for any metadata value change.
To fire a test trigger:
In Frame.io, open any file in your workspace
Set the status field to Approved
Return to Zapier and confirm the trigger step has received the event
Frame.io V4 sends data to Zapier in real time. Zapier needs to receive a real event from Frame.io before the fields in later steps are available to configure. Confirm the trigger step has received the event before moving to the next step.
Once the payload is received, check the trigger results and confirm the New Value field shows Approved. This is the value the filter in the next step will match against. If the value shown is anything other than Approved, the filter will stop the Zap.
Note: The trigger fires on any metadata change across your workspace. The filter in the next step is what limits the Zap to approved files only.
Step 4: Confirm the filter step
The filter checks that the metadata value that changed is exactly Approved. It is pre-configured and does not need to be changed. Any file marked with a different status will not proceed through the Zap.
Step 5: Configure the Show File step
The Show File step retrieves the file details needed to upload it to Google Drive, including the original download URL.
Each field must use the dynamic value from the trigger payload, not a static value. Static values lock the Zap to a single hardcoded file and it will run on that file every time, regardless of what triggered the Zap.
Confirm the following fields are mapped correctly:
Account: your Frame.io account
Workspace: your Frame.io workspace
Project: update this to your Frame.io project ID
File: mapped dynamically from the trigger
Step 6: Select your Google Drive folder
Select the folder where approved files should be uploaded. This is typically a shared team folder for final deliverables.
Step 7: Test the Zap
Before publishing, click Test on each step in sequence and confirm the data is flowing correctly from Frame.io through to Google Drive. Fix any errors before publishing.
Step 8: Publish the Zap
Click Publish. The Zap is now live. Every time a file is marked as Approved in Frame.io, it will be uploaded to your Google Drive folder automatically.
The Zap is now live. Every time a file is marked as Approved in Frame.io, it will be uploaded to your Google Drive folder automatically.
Troubleshooting
Zap is not triggering
Confirm the correct Frame.io account and workspace are selected in the trigger step. Make sure a file has been marked as Approved in your workspace after the Zap was published.
Zap is triggering for files that are not Approved
Check the filter step and confirm the value is set to exactly Approved with correct spelling and casing.
Show File step is returning the wrong file
Confirm the File field in the Show File step is mapped dynamically from the trigger, not hardcoded. Also confirm the project ID has been updated from the placeholder value to your actual project ID.
File not appearing in the right Google Drive folder
Confirm the connected Google Drive account has edit access to the destination folder.