In this guide, you will configure an Action to work with Make. You will create a scenario in Make that gives you a webhook URL, then create the Action in Frame.io with that URL. Let's get started.
If you want to learn more about Actions and how they work, check out the Frame.io developer 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 scenario on the other end runs.
What you'll need
A Frame.io account with Account Owner or Content Admin permissions
A Make account
A webhook URL from your scenario
Before you start
Who can create Actions: Account Owners and Content Admins only. Any member of the Workspace can run 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
Select Create Action.
Fill in the fields:
Name: The label shown in the Frame.io context menu
Description: For internal reference only.
Event: An identifier for events the Action generates. Frame.io sends it as type in the payload.
URL: The webhook URL from your Make scenario
Workspace: The Workspace where the Action was triggered
Selection Behavior: Select Allow this action to run on more than one selected item. The scenarios in this collection need this turned on, because the payload then arrives as a resources list.
Select Save.
Get your webhook URL from Make
Make uses a Custom webhook module to receive data from Frame.io. When you add one to a scenario, Make generates a unique URL and starts listening at that URL for incoming data. When a user triggers the Action in Frame.io, Frame.io sends a payload to that URL. Make receives it and uses the data inside to run the rest of the scenario.
This means the webhook URL needs to exist in Make before you create the Action in Frame.io. The URL is what connects the two.
To get your webhook URL:
In Make, create a new scenario or open an existing one.
Select the + button, search for Webhooks, and select Custom webhook.
Next to Webhook, select Add. Enter a name that describes the workflow, and select Save.
Select Copy address to clipboard.
Paste the webhook URL into the URL field of your Action in Frame.io.
Note: The webhook URL is available as soon as you save the webhook, even before the scenario is turned on.
Run a test trigger first
The modules that follow the Custom webhook 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 modules cannot be configured.
To run a test trigger:
In Make, select Run Once. Make now waits for data.
In Frame.io, right-click any file, folder, or version stack in the Workspace.
Select Actions and choose your Action.
Return to Make. The Custom webhook module should no longer show No data detected. The data it received now appears under output.
Once Make receives the payload, the modules after the Custom webhook show its data as values you can select. Map these values into each field instead of typing them in. A typed value locks the scenario to one item, so it runs on that item every time, whatever triggered the Action.
The payload contains IDs only, so add a module to get the details. Use Get a file for a file or a version stack, and Get a folder for a folder. If the Action runs on a folder and the next module is Get a file, the scenario fails.
When you're ready, turn on the Active toggle. The Custom webhook is an instant trigger, so the scenario runs each time someone triggers the Action.
Trigger an Action
Right-click any file, folder, or version stack in Frame.io, or open its three-dot menu.
Select Actions.
Choose your Action from the list.
Frame.io sends the payload to your URL, and the scenario runs.
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 |
Make shows these fields under Output as soon as the webhook receives its first payload.
Run an Action on more than one file
Frame.io sends the files you select in a resources list, so a scenario that starts from an Action needs an Iterator in Make to handle each file. An Action can send up to 100 files in one request.
To set it up:
In Frame.io, go to next.frame.io/settings/actions. Edit your Action, select Allow this action to run on more than one selected item, and select Update. This changes the payload from a single resource to a list of resources right away, so update any scenario you built before the change.
In Make, add an Iterator module after the Custom webhook module. Set Array to the resources list from the webhook.
Map the modules that follow from the Iterator output. Run the scenario once with real data first, so Make learns the fields.
What to know:
Credits: Each module after the Iterator runs once per file, so 10 files use about 10 times the operations. A trigger counts as one operation per run.
Rate limits: Frame.io limits requests per user. A 429 error means requests came in too fast. Other apps can also have rate limits.
Errors: A scenario that starts with an instant trigger is deactivated on the first error. Turn on Store incomplete executions so you can fix the issue and retry. See Make's Scenario settings page.
Order: Make runs webhooks in parallel by default. Turn on Process data in order if the sequence matters.
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 Owner or Content Admin can create, modify, or delete them, and changes take effect immediately for all users.
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 scenario
Confirm the webhook URL in your Action matches the Webhook URL in the Custom webhook module exactly. Then check that the scenario is turned on.
Make shows no data after I trigger the Action
The Custom webhook only receives data while the scenario is waiting. Select Detect new values, then trigger the Action in Frame.io again.
The scenario runs on only one file when multiple assets are selected
The scenario needs an Iterator after the Custom webhook, and the Action must allow more than one selected item. See Run an Action on more than one file. Run a new test trigger afterward so Make picks up the updated payload.
The webhook stopped receiving data
Make deactivates a webhook that has not been connected to a scenario for five days. Reconnect the webhook to a scenario and turn the scenario on.
No access to the Actions settings page
Creating and managing Actions requires Account Owner or Content Admin permissions.