Skip to main content

Action: Upload Frame.io Files to Google Drive

Trigger a Action on a Frame.io file to upload it directly to Google Drive.

A
Written by Aaron Burns

Trigger a Action on a Frame.io file to upload it directly to Google Drive.

What you'll need

  1. A Frame.io V4 account with Account Owner or Content Admin permissions

  2. A Zapier account (Free plan or above)

  3. A Google Drive account with edit access to the destination folder

Important: Actions are only visible to users who are members of the workspace where the action is configured. Users with access only at the project or folder level will not see the Actions menu.

Before you set up this Zap

Create an Action in Frame.io.

This Zap is triggered by a Action in Frame.io. If you have not set one up yet, follow Set Up Actions in Frame.io for Zapier before continuing. You will need the webhook URL from your Catch Hook trigger step before you can complete the setup below.

Set up the Zap

Step 1: Open the template and set up the Catch Hook

Click the button below

The setup wizard will create a skeleton for the zap. Once your zap has been named and saved to the desired location exit the setup wizard. Copy the webhook URL from the Catch Hook trigger step and paste it into the URL field of your Action in Frame.io. For full instructions see Set Up Actions in Frame.io for Zapier.

Step 2: Fire a test trigger

In Frame.io, right-click any file in the workspace, select Actions, and choose your Action. Return to Zapier and confirm the Catch Hook step has received the payload.

Step 3: Connect your accounts and map the Show File fields

Frame.io: Select the account associated with the workspace where your Action is configured.

Google Drive: Select the account where files should be uploaded. Make sure it has edit access to your destination folder.

Then open the Show File step and confirm the following fields are mapped to dynamic values from the webhook payload:

  • Account: Account Id from the webhook payload

  • Workspace: Workspace Id from the webhook payload

  • Project: Project Id from the webhook payload

  • File: Resource Id from the webhook payload

Note: The download url comes from Include Additional Data media_links.original

Each field must use the dynamic value from the payload, not a static value. Dynamic values update with every trigger and ensure the Zap always acts on the asset that was clicked. Static values lock the Zap to a single hardcoded asset and it will run on that asset every time, regardless of what triggered the action.

Step 4: Set the project filter (recommended)

The filter scopes the Zap to one Frame.io project. Without it, the Zap runs for every file across your entire workspace.

The project ID field should now be populated from the test payload. Confirm it matches the project you want to scope this automation to, or enter a different project ID manually.

To find a project ID:

  1. Open the project in Frame.io

  2. Copy the ID from the browser URL bar. It is the string of characters after /project/

Note: To scope the filter to a specific folder, navigate into the folder in Frame.io. The folder ID will appear in the URL after the project ID. Use that value in the filter field instead.

To skip the filter, delete the filter step. The Zap will run for all files in your workspace.

Step 5: Select your Google Drive folder

Select the folder where uploaded files should be saved.

Step 6: Publish the Zap

Click Publish. The Zap is now live.

Use the Action

  1. Right-click any file in Frame.io and select Actions

  2. Select Upload to Google Drive (or whatever you named your action)

The file uploads to your Drive folder automatically.

Troubleshooting

Zapier is not receiving the test payload

Make sure the webhook URL in your Action matches the URL from the Catch Hook trigger step exactly. Confirm the Action is active at next.frame.io/settings/actions.

Frame.io fields are empty in the Show File step

The Catch Hook has not received a payload yet. Complete Step 2 before configuring the Show File step.

Filter step stopping the Zap

Make sure the project ID is copied exactly from the URL, with no extra spaces or characters.

File not in the right Drive folder

Confirm the connected Google Drive account has edit access to the destination folder.

Actions menu not showing in Frame.io

See Set Up Actions in Frame.io for Zapier for troubleshooting steps.

Did this answer your question?