In this guide we will help you configure Actions to work with Zapier. You will need to configure your Action on Frame.io and then set up a workflow on Zapier using one of our templates. Let's get started.
If you want to learn more about Actions and how they work, check out our Actions documentation.
Actions add a button to the Frame.io context menu. When a user triggers one on a file, folder, or version stack, Frame.io sends a payload to a URL you configure and the automation on the other end runs.
What you'll need
A Frame.io V4 account with Account Admin permissions
A Zapier account (Free plan or above)
A webhook URL from your Zap
Before you start
Who can create Actions: Account Admins only. Any member of the workspace can execute them.
Who can see Actions: Only 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.
Create an Action
Click Create Action
Fill in the fields:
Name: Label shown in the Frame.io context menu
Description: Internal reference only. Not visible in the Frame.io web app
Event: Internal key to identify this action, for example: *upload.asset*
URL: Webhook URL from your automation tool
Workspace: The workspace where the action will appear
Click Save
Get your webhook URL from Zapier
Zapier uses a Catch Hook step to receive data from Frame.io. When you set up a Zap with a Catch Hook trigger, Zapier generates a unique URL and starts listening at that address for incoming data. When a user triggers the Action in Frame.io, Frame.io sends a payload to that URL. Zapier catches it and uses the data inside to run the rest of the Zap.
This means the webhook URL needs to exist in Zapier before you create the Action in Frame.io. The URL is what connects the two.
To get your webhook URL:
Open your Zap in Zapier
Click the Catch Hook trigger step
Go to the Test tab
Copy the Webhook URL
Paste it into the URL field of your Action in Frame.io
Note: The webhook URL is available as soon as the trigger step is configured, even before the Zap is published.
Firing a test trigger is essential
The steps that follow the Catch Hook depend on data from Frame.io. Account ID, workspace ID, project ID, and file ID are only available after the webhook receives its first payload. Without it, those fields will be empty and the later steps cannot be configured.
To fire a test trigger:
In Frame.io, right-click any file in the workspace
Select Actions and choose your Action
Return to Zapier. The trigger step should now show a payload has been received.
Once the payload is received, the downstream steps in your Zap will show the payload data as selectable options. Select the dynamic values from the payload for each field. 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.
Trigger an Action
Right-click any file, folder, or version stack in Frame.io (or open the three-dot menu)
Select Actions
Choose your Action from the list
Frame.io sends the payload to your URL and the automation runs.
Note: If no Actions are active in your workspace, the Actions item will not appear in the context menu.
What the payload contains
When an Action is triggered, Frame.io sends the following data to your URL:
Field | Description |
Account | The Frame.io account the action belongs to |
Workspace | The workspace where the action was triggered |
Project | The project containing the file |
Resource ID | The ID of the file, folder, or version stack |
Resource type | File, folder, or version stack |
User | The user who triggered the action |
Action ID | The unique ID of the Action |
Interaction ID | A unique ID for this specific execution |
Event | The event key set when configuring the action |
These fields populate automatically in your Zap steps as soon as the webhook receives its first payload.
Manage Actions
Go to next.frame.io/settings/actions to view, edit, enable, or disable actions. Actions belong to a workspace, not to any individual user. Any Account Admin can create, modify, or delete them, and changes take effect immediately for all users.
Migrated from a legacy account? All Actions are automatically disabled on migration to V4. Re-enable them from the Actions settings page after confirming the URL and configuration are compatible with V4.
Troubleshooting
Actions menu not showing up
At least one Action must be active in the workspace for the Actions item to appear in the context menu.
Action not triggering the Zap
Confirm the webhook URL in your Action matches the URL in the Zapier trigger step exactly.
No access to the Actions settings page
Creating and managing Actions requires Account Admin permissions. Contact your Account Admin.
Action stopped working after migration
Go to next.frame.io/settings/actions, check the Status column, and re-enable any actions that were disabled during migration.